Census the drifted colors, spacing, and duplicate components; propose the token set and migration order to unify them.
Free & open · no signup · read-only — it ends by asking · nothing leaves your machine
You are working inside this repo. Mission: census the visual drift — every near-duplicate color, arbitrary spacing value, and re-implemented component — and propose the token system and migration order that unifies them.
This is for a codebase with no system yet: census the drift, propose the tokens. If tokens already exist, 105 audits their adoption; for color and contrast alone, 56 computes the ratios.
Read-only pass. Your only write is the report file.
Phase 2 sweeps the codebase through every one of these, citing file and line for each finding.
cluster near-duplicates; name the intended color each cluster wants to be
arbitrary values vs an implied scale; propose the scale the code is already reaching for
sizes/weights outside any scale; heading styles re-declared per page
for each cluster: which implementation wins and why
inline styles and one-off overrides defeating existing tokens/components
hover, focus, disabled, error styled differently across components
One structured report at the repo root — or in reports/, if you keep one — the same shape every time, ready for a teammate — or the optional Studio — to act on.
Every Goal Prompt follows the same four steps, so results are consistent and repeatable — no matter which one you run.
Count, don't estimate.
Color sprawl — cluster near-duplicates.
Every consolidation names keep / merge / kill per variant, with usage counts.
Create DESIGN-SYSTEM.md at repo root.
Copy it and paste it into your agent inside the repo you want checked.
Install the goal plugin once — two commands — then just type /goal:design-system-consolidation.
/plugin marketplace add GhostlyGawd/goal-prompts/plugin install goal@goal-promptsOr install only this Goal Prompt as /goal-design-system-consolidation:
curl -fsSL https://goal-prompts.vercel.app/install | BRIEF=15 shLet an agent fetch it mid-conversation, or pull the raw Goal Prompt by URL.
https://goal-prompts.vercel.app/raw/15.mdNothing hidden — this is the whole Goal Prompt, verbatim. Read it in a minute, edit it, or copy it as-is.
# Goal: Design System Consolidation You are working inside this repo. Mission: census the visual drift — every near-duplicate color, arbitrary spacing value, and re-implemented component — and propose the token system and migration order that unifies them. This is for a codebase with no system yet: census the drift, propose the tokens. If tokens already exist, 105 audits their adoption; for color and contrast alone, 56 computes the ratios. Read-only pass. Your only write is the report file. ## Phase 1 — Take the census Count, don't estimate. Grep the styles and components: - Distinct color values (how many near-identical grays and brand shades?) - Distinct font sizes, weights, and line heights - Distinct spacing values, radii, shadows, z-indexes - Component duplicates: how many button/input/modal/card implementations exist? ## Phase 2 — Audit through 6 lenses 1. **Color sprawl** — cluster near-duplicates; name the intended color each cluster wants to be 2. **Spacing drift** — arbitrary values vs an implied scale; propose the scale the code is already reaching for 3. **Type chaos** — sizes/weights outside any scale; heading styles re-declared per page 4. **Component duplicates** — for each cluster: which implementation wins and why 5. **System bypasses** — inline styles and one-off overrides defeating existing tokens/components 6. **State inconsistency** — hover, focus, disabled, error styled differently across components ## Phase 3 — Curate - Every consolidation names keep / merge / kill per variant, with usage counts - Order migration by risk: tokens first (mechanical), shared components second, page cleanups last ## Phase 4 — Report Create `DESIGN-SYSTEM.md` at repo root: 1. **Census numbers** — the before: counts per category 2. **Proposed tokens** — colors, spacing scale, type scale, radii/shadows — derived from what the code already wants 3. **Component consolidation list** — keep/merge/kill with usage counts and winning implementation 4. **Migration order** — sequenced lowest-risk first, each step shippable 5. **Projected after-numbers** — the census once complete Start the report with today's date. If `DESIGN-SYSTEM.md` already exists from a previous run, read it first and lead with what changed since. ## Rules - Derive the system from the code's existing center of gravity — don't import a foreign aesthetic - Mechanical, reviewable migrations beat big-bang rewrites - No design system or shared UI components in this repo? Say so in a one-paragraph null report and stop — a null result is a valid finding. - If a `reports/` directory exists at the repo root, write the report there instead of the root. - Before asking, present the top findings as a ranked list in plain words - Report only — end by asking which migration step to take
reports/ directory exists at the repo root, write the report there instead of the root.Curated neighbors — briefs that answer the adjacent question, worth running in the same session.
Whether the design system's tokens are actually used — or whether hardcoded colors, spacing, and type have crept back in and drifted the UI out of sync.
The palette as it actually ships — every hex in the codebase, contrast ratios computed, semantic drift named, and whether dark mode is a theme or an apology.
Duplication, tangles, and dead patterns — mapped as interest paid vs principal owed, with a refactor sequence that pays for itself.
Walk clone → install → run → change → PR like a brand-new developer and log every stumble on the way to a first contribution.
Can a coding agent work here? Entry files, one-command checks, discoverable conventions, and a mechanical definition of done — audited by attempting the work.
Read git history for the human risks — files only one person understands, critical paths with a truck factor of one, and the knowledge that leaves when they do.