State Color Matrix
Define how every control looks in each interaction state, once, instead of screen by screen.
What it adds
A matrix pairing each interactive component with its default, hover, active, focus, selected, disabled, and loading treatment.
What your agent is told to do
5
What your agent is told to do
5-
1
Enumerate the interactive components — buttons, links, rows, cards, tabs, menu items, form controls — and fill in every state for each, so that the combinations nobody thought about are visibly blank rather than silently absent.
-
2
Check contrast in every state, not only the default one. Hover and disabled treatments are where text most often drops below threshold, and disabled is where teams most often assume the rules no longer apply.
-
3
Treat hover as an enhancement that touch users will never see. Any meaning carried only by a hover treatment — that a row is actionable, that an item can be removed — must also be carried by something permanent.
-
4
Make selected, active, and disabled distinguishable from one another by more than colour: a selected row and a disabled row rendered as two shades of the same grey are indistinguishable to a large number of users and identical in a forced-colours mode.
-
5
Do not change an element's box dimensions on state change. Adding a border on hover or thickening one on selection reflows the row underneath; keep the border present and change only its colour, or draw it inside the element's own box.
Edge cases it handles
7
Edge cases it handles
7- Contrast must hold in every state, including hover, selected, and disabled — a disabled label is still read, and a low-contrast hover makes text briefly unreadable at the exact moment someone is aiming at it.
- Hover cannot carry meaning on touch devices, where it either never fires or sticks after a tap, so anything discoverable only on hover is undiscoverable to most mobile users.
- Selected, active, and disabled must be distinguishable from each other and from focus without relying on hue alone, since colour-vision differences and forced-colours modes collapse them together.
- State changes must not alter the element's dimensions, or the layout shifts under the pointer and the row moves out from under the click.
- States combine: a selected row that is also hovered and also focused needs one defined result, not three treatments layered until nothing is legible.
- Focus ring geometry, offset, and clipping belong to the Focus Ring System; this matrix owns only the colours the focus state uses, and must not specify a second ring.
- A loading state on a control must remain visibly the same control at the same size, so the button does not shrink to a spinner and take the layout with it.
Definition of done
9
Definition of done
9- Every interactive component has a defined treatment for default, hover, active, focus, selected, disabled, and loading.
- Contrast requirements are met in every state, including disabled.
- No affordance or meaning is conveyed by hover alone.
- Selected, active, focus, and disabled are distinguishable without relying on colour alone.
- No state change alters an element's dimensions or shifts surrounding layout.
- Combined states have a single defined result.
- Focus ring geometry is delegated to the Focus Ring System rather than redefined.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Semantic Color Tokens
Semantic Color Tokens
Name colours by the job they do, so changing a theme is one edit rather than a sweep.
What it does
A vocabulary of role-named colour tokens — surface, text, border, accent, danger, success — that components reference instead of literal values.
How it works
- 1 Inventory every literal colour value in the codebase and group them by the job they are doing rather than by the shade they happen to be. Two different greys used as card backgrounds are one role; the same grey used as a background and as a border is two.
- 2 Define the role names once and map each role to a value per theme. A role may resolve to a light grey in one theme and a near-black in another; what must not change is which components reference it.
- 3 Stop shared components accepting raw colour values. A primitive that takes a hex string as a prop guarantees that some product screen will hardcode a colour the themes never learn about.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/semantic-color-tokens
Motion Token System
Motion Token System
Give the app one shared vocabulary of durations and easing curves instead of ad hoc numbers.
What it does
A named set of durations and easing curves, each tied to a category of motion, replacing the timing values scattered through the app's components.
How it works
- 1 Inventory every duration and easing value currently written into the app and group them by what they do: something entering, something leaving, something being emphasised, and something changing size or position.
- 2 Name a small set of durations — roughly instant, quick, standard, and deliberate — and a small set of curves, then map each motion category to a pairing. Four or five of each is enough for an entire product.
- 3 Give entrances and exits different treatment. Something arriving should decelerate into place; something leaving should accelerate away and take less time, because nobody wants to wait for a dismissal.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/motion-token-system
Responsive Grid Tokens
Responsive Grid Tokens
Express columns, gaps, and spans as shared tokens rather than per-component guesses.
What it does
A token set describing column counts, gutters, and span behaviour at each breakpoint, used by every grid in the app.
How it works
- 1 Find the grids already in the app — card lists, dashboards, form layouts, media galleries — and record how many columns each uses at each size. The reconciled set is normally three or four column counts, not one per screen.
- 2 Define gutters from the spacing scale rather than inventing grid-specific values, so the gap between cards matches the rhythm of everything around them.
- 3 Express spans in tokens tied to the column count, so a component asking for half a row keeps working when the row drops from four columns to two instead of overflowing.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/responsive-grid-tokens
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.