Brand Palette Generator
Turn one brand colour into a full ramp the app can use without breaking contrast.
What it adds
A generator that expands a single seed colour into light and dark ramps with contrast held at every step.
What your agent is told to do
5
What your agent is told to do
5-
1
Take a single seed colour and produce a ramp of named steps, each with a defined contrast target against the surfaces it is meant to sit on, rather than an evenly spaced set of tints that happens to look plausible.
-
2
Generate the light and dark ramps independently. Inverting the light ramp gives dark mode a palette that is too saturated at the top and indistinguishable at the bottom — dark surfaces need less chroma and different spacing.
-
3
Keep the status colours out of the brand ramp. Danger, warning, and success must remain legible as danger, warning, and success even when the brand colour is itself red or green, so derive them separately and only borrow the brand's chroma character.
-
4
Let a person lock individual steps — usually the exact brand colour itself — and regenerate everything else around the locked values rather than overwriting them.
-
5
Write the output into the existing semantic token map defined by Semantic Color Tokens. Do not emit a parallel palette file that components can reference directly; two sources of colour truth diverge within a release.
Edge cases it handles
7
Edge cases it handles
7- Light and dark ramps must be generated separately rather than by inversion, because a ramp that reads correctly on white becomes either glaring or muddy when placed on a dark surface.
- Every step needs its contrast checked against the surfaces it will actually be used on, not just against pure white and pure black, or the mid-range steps pass in theory and fail on cards.
- The brand colour must not become the colour of every status. A brand-coloured success state and a brand-coloured error state leave users unable to tell an outcome apart from decoration.
- Locked values must survive regeneration exactly. A brand colour that shifts by a fraction on each regeneration will eventually no longer match the printed guidelines it came from.
- A very light or very dark seed leaves no room to extend the ramp in one direction — detect that case and say so rather than producing a ramp with five identical steps at one end.
- A near-grey seed with almost no chroma produces a ramp indistinguishable from the neutral scale; require a minimum chroma or warn explicitly.
- Regeneration must be previewable before it is applied, since it changes every screen at once.
Definition of done
9
Definition of done
9- One seed colour produces a complete named ramp for both light and dark.
- The dark ramp is generated independently rather than derived by inverting the light ramp.
- Every step meets its contrast target against the surfaces it is used on.
- Status colours are derived separately and remain distinguishable from the brand colour.
- Locked steps are preserved byte for byte through a regeneration.
- Output populates the existing semantic token map, with no parallel palette file.
- Degenerate seeds produce an explicit warning rather than a silently unusable ramp.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Z-Index Registry
Z-Index Registry
Keep every stacking value in one file so nobody has to guess a bigger number.
What it does
A single source of named z-index tokens, with reserved ranges per layer and a check that blocks raw values.
How it works
- 1 Find every z-index in the codebase, including inline styles and values buried in third-party overrides, and list them with the component that owns each. The count is usually higher than anyone expects and several will be arbitrary large numbers.
- 2 Reserve a range for each layer rather than assigning single values, so a new dropdown can slot between existing ones without renumbering everything above it. Leave real gaps between ranges.
- 3 Name each token after the layer it belongs to and derive the ordering from Elevation Layer Map. That feature decides what covers what; this one holds the numbers and stops them being invented locally.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/z-index-registry
Spacing Scale
Spacing Scale
Reduce the app's spacing to a small set of steps that repeat across every surface.
What it does
A named spacing scale covering gaps, padding, and section rhythm, with every existing value in the app mapped onto it.
How it works
- 1 Collect every spacing value currently in the codebase and count how often each appears. The result is usually a handful of genuine intentions surrounded by dozens of near-misses that were nudged once and never revisited.
- 2 Define a scale that is fine at the small end, where control padding lives, and coarse at the large end, where section separation lives. A linear scale gives too many indistinguishable large steps and too few small ones.
- 3 Separate the tokens used inside a component from the ones used between components and between page sections, and name them so the difference is obvious. The same number serving both purposes means a change to button padding also changes the gap between sections.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/spacing-scale
Shadow Scale
Shadow Scale
Replace ad hoc shadows with a small set tied to what each surface actually is.
What it does
A fixed ladder of shadow tokens, each named for an elevation role rather than a blur radius.
How it works
- 1 Collect every shadow currently declared anywhere in the app and group them by what they sit on — a resting card, a hovered card, a dropdown, a dialog, a toast. Most apps have a dozen near-identical values that collapse into four or five roles.
- 2 Name each step for its role, not its appearance. A token called menu tells the next person which surfaces may use it; a token called shadow-md-2 does not.
- 3 Use a single light source for the whole scale, so offset, blur, and spread grow together as elevation rises. Two shadows lit from different directions on the same screen read as a rendering bug.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/shadow-scale
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.