Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/rebrand
Apply a downstream brand to a PlatformPlatform fork. Edits one config file, drops in eight supplied logo assets, renames the solution and CLI to the new brand, and rotates UserSecretsId across every csproj. Skips all other source files. Use once per downstream fork after cloning, or to re-flip a brand later.
Passed 18 of 23 test cases with the skill, and 3 of 23 without it.
and 18 more in the full report
16 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When editing platform-settings.jsonc during rebranding, can I add inline comments at the end of key-value JSON lines, like `"productName": "Acme" // primary brand`?
| Checked | Without skill | With skill |
|---|---|---|
| Advises keeping comments on their own separate lines because the build system only strips whole-line comments. | Missed | Passed |
The instructions your model reads when the skill loads.
Apply a downstream brand to a PlatformPlatform fork. The rebrand is intentionally narrow: brand values live in one JSONC file, logo assets live at canonical paths, and a handful of names (solution file, CLI alias, UserSecretsId, Docker prefix) flip in lockstep. Source code is not touched.
This skill expects the upstream canonical layout — primary logos named logo-{light,dark}-88.png and square marks named logo-mark-{light,dark}-192.png. If you are on an older PlatformPlatform that still uses logo-wrap-* or -512 mark names, the upstream needs the one-time rename first.
git status --porcelain
Stop if there is anything staged or unstaged. Rebrand touches many files at once and a mid-rebrand merge with unrelated changes is hard to untangle.
Use AskUserQuestion to collect all values up front. Do not write anything until every value is in hand — otherwise a partial rebrand leaves the fork in a broken state.
Required inputs:
Acme.pp. Example: acme. No spaces, no dashes inside the binary name.PlatformPlatform.slnx. Example: Acme (yielding Acme.slnx).@example.com (leading @ required). Classifies users as internal for telemetry segmentation. BackOffice access is controlled by Entra ID, not by this setting.tagline.web.<locale> — shown in the landing page footer (consumer reads the active Lingui locale).tagline.mail.<locale> — shown in the email footer (renderer reads the template's locale).
The two maps must list the SAME locales (backend fails loud at startup if they diverge); the en-US value is REQUIRED. Collect en-US and da-DK for both channels — for downstream brands the web and mail copy will often differ (e.g. the email leans toward the recipient context). For PlatformPlatform itself, web == mail.branding.primaryColor: light, lightForeground, dark, darkForeground. Drives the "button color" and its on-color text in both light and dark modes. The value flows through theme.css via an inline <style> block injected per HTML template (--brand-primary / --brand-primary-foreground CSS variables); --primary and --sidebar-primary read those. Pick foregrounds with enough contrast against the primary — that is a deliberate brand-owner decision, not auto-derived.branding.themeColor.light / branding.themeColor.dark tint the mobile browser/PWA toolbar (iOS Dynamic Island "tint band"); the frontend swaps the <meta name="theme-color"> value at runtime to match the resolved theme. branding.themeColor.light is the install-time fallback baked into manifest.json (PWA spec is single-valued). branding.backgroundColor is the PWA splash-screen background while the SPA boots.branding.emailHeaderBackground.branding.showAddToHomescreen boolean. When true the user-facing app renders the iOS "Add to Home Screen" install prompt (it self-limits to iOS Safari outside an installed PWA); false suppresses it entirely. BackOffice never shows the prompt regardless.Required logo assets (user provides absolute paths to eight files):
| Spec | Canonical path written to |
|---|
test cases passed, vs 3 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.