Rebrand

STEP 7: Rotate UserSecretsId across every csproj

Every .csproj carrying a <UserSecretsId>platformplatform-<old-guid></UserSecretsId> element needs a fresh GUID and the new alias prefix.

Find them:

grep -rln "<UserSecretsId>platformplatform-" application developer-cli

Generate ONE new GUID and use the SAME <UserSecretsId><cli-alias>-<new-guid></UserSecretsId> value in every match. All projects must share the identical UserSecretsId — secrets live at ~/.microsoft/usersecrets/<id>/secrets.json and every project reads from that single store. Different GUIDs would split the store per project and nothing would resolve secrets.

Existing user secret stores on disk (~/.microsoft/usersecrets/) are not migrated — developers may need to re-run any local secret setup after the rotation.

STEP 8: Set the Docker volume prefix

Set development.dockerVolumePrefix in platform-settings.jsonc to the product name lowercased, with spaces replaced by hyphens (e.g. productName "Acme Foo Bar" -> "acme-foo-bar"). The Aspire AppHost (which names the volumes) and the developer CLI's stop command (which removes them) both read this single value through DockerVolumeNaming.ResolveVolumePrefix, so it keeps each fork's volumes isolated on a shared machine. Use the product name, not the CLI alias — the volume identity tracks the brand.

STEP 9: Update GitHub Actions

Replace solution-file references in every workflow:

grep -rln "PlatformPlatform\.slnx" .github/workflows

Files known to reference it: code-style.yml, app-gateway.yml. Replace PlatformPlatform.slnx with <SolutionName>.slnx. Also update the human-readable label in code-style.yml (e.g. full backend (PlatformPlatform.slnx) -> full backend (<SolutionName>.slnx)).

STEP 10: Leave the bootstrap quickstart image alone

cloud-infrastructure/cluster/deploy-cluster.sh and cloud-infrastructure/modules/container-app.bicep reference ghcr.io/platformplatform/quickstart:latest as a default image. This is an upstream-provided empty hello-world container used during initial Bicep deployment, before the downstream's own container registry exists. Chicken-and-egg: Bicep creates the registry, but the first deployment needs a placeholder image. Downstream forks keep using the upstream image. Do not touch these files.

Illustrative comments in cloud-infrastructure/ and .github/workflows/ use example.com (RFC 2606 reserved domain) as placeholder sender domains. Nothing to change.

STEP 11: Audit for hardcoded references

The skill assumes the codebase reaches every brand-coupled value through configuration (platform-settings.jsonc, Configuration.AliasName, the dockerVolumePrefix constant, the new UserSecretsId). If something hardcodes the old brand, that is a centralization gap upstream — surface it, do not silently patch.

Run these greps across the whole repo (excluding build artifacts):

grep -rln "PlatformPlatform" . \
  --exclude-dir=node_modules --exclude-dir=bin --exclude-dir=obj --exclude-dir=artifacts \
  --exclude-dir=dist --exclude-dir=.turbo --exclude-dir=.git
grep -rln "platformplatform" . \
  --exclude-dir=node_modules --exclude-dir=bin --exclude-dir=obj --exclude-dir=artifacts \
  --exclude-dir=dist --exclude-dir=.turbo --exclude-dir=.git
grep -rln "\\bpp\\b" . \
  --include="*.cs" --include="*.csproj" --include="*.yml" --include="*.sh" --include="*.ts" --include="*.tsx"

Expected remaining hits after the rebrand:

• README.md, LICENSE, CODEOWNERS, CONTRIBUTING.md — out of scope for this skill (the rewrite is project-specific); not a brand-leak.
• cloud-infrastructure/cluster/deploy-cluster.sh and cloud-infrastructure/modules/container-app.bicep — the bootstrap quickstart image, left intentionally (see step 10).

Anything else is a finding. For each hit:

1. Read the file to understand whether the reference is brand-coupled (must change) or a stable identifier (e.g. an upstream package name in pull-platformplatform-changes).
2. If brand-coupled and the value should come from configuration but doesn't, fix the upstream code so future rebrands stop hitting this — do not just patch the literal here. Report the fix as a centralization improvement that should land in PlatformPlatform.
3. If brand-coupled but trivially local (e.g. a comment), update inline.

STEP 12: Verify

Run in order:

1. build --quiet — full backend + frontend build. Any failure here means the rebrand broke something the rebrand itself was supposed to leave untouched. Investigate before continuing.
2. aspire-restart — restart the AppHost. Should print the new product name in startup logs.
3. e2e --smoke --quiet — confirms the SPA renders, login works, and the new product name appears where the tests assert it.
4. Visual smoke in the browser: open the SPA, confirm the footer logo, the favicon, the page title, and the email-template preview all show the new brand.

Final check:

git diff --stat

The diff should only touch:

• application/platform-settings.jsonc
• application/shared-webapp/ui/images/logo-*.png
• application/main/WebApp/public/favicon.ico
• application/main/WebApp/public/apple-touch-icon.png
• application/main/WebApp/public/apple-touch-icon-dark.png
• application/account/BackOffice/public/favicon.ico
• application/account/BackOffice/public/apple-touch-icon.png
• application/account/BackOffice/public/apple-touch-icon-dark.png
• application/main/WebApp/public/email/logo-1200x184.png
• application/<SolutionName>.slnx (renamed from PlatformPlatform.slnx)
• application/<SolutionName>.slnx.DotSettings (renamed)
• application/main/Main.slnf
• application/account/Account.slnf
• developer-cli/DeveloperCli.csproj
• Every *.csproj with a rotated UserSecretsId
• A small number of .cs files that read the UserSecretsId prefix
• .github/workflows/*.yml

Source code outside this list should be untouched. If anything else shows up in the diff, stop and investigate before committing.

Out of scope

The skill does not touch:

• README.md, LICENSE, CODEOWNERS, CONTRIBUTING.md — these are not required for the fork to run, and the correct rewrite is project-specific (license terms, README narrative, code-owner team names). Out of scope because the skill does not know how, not because they should stay.
• package.json workspace scopes — already brand-neutral (@repo/*), nothing to do.
• C# root namespaces — every csproj has its own assembly-scoped namespace; nothing reads PlatformPlatform.*. Nothing to do.

A downstream that wants to rewrite README/LICENSE/CODEOWNERS does that in a separate pass.