Branding — Changing the Identity

The identity is chosen at design time: high-fidelity derives it, writes it into design/tokens.json, and bootstrap translates it into each app. This skill is the rebrand — a later change of mind, once code exists.

One rule makes it cheap: design/tokens.json is still the single source of style. Change it there, re-translate into every app directory, and every screen follows. Iteration happens on a static brand board first, so the user refines before anything touches code.

If no design/tokens.json exists, the product predates it — stop and say so, then work from the app's own theme file and write the JSON as part of this run, so the next rebrand is one edit.

Identity, not structure. Branding never moves, adds, or removes UI. If the user asks for layout changes while iterating, that is a spec change — point them back to the high-fidelity skill.