Icon System
Draw every icon from one set, at one set of sizes, with one rule for accessible naming.
What it adds
A single icon interface with a fixed size ladder, stable names, predictable alignment, and defined accessible behaviour.
What your agent is told to do
5
What your agent is told to do
5-
1
Inventory every icon currently rendered in the app — inline vector markup, sprites, image files, icon fonts, glyphs pasted into labels — and route all of them through one interface so a size or colour change is made in one place.
-
2
Fix a small size ladder, three or four steps, tied to the type scale, and make every icon align to the text it sits beside rather than to the box that contains it.
-
3
Decide per usage whether an icon is decorative or meaningful. Decorative icons must be hidden from assistive technology; meaningful ones need an accessible name that says what the control does, not what the picture is.
-
4
Make icons inherit colour from their context so a single icon works in a button, a menu, a warning, and a disabled control without a per-instance override.
-
5
Do not leave a second icon library in place while migrating. Two sets of the same concept drift apart, and the day someone reaches for the wrong chevron is the day the app has two visual languages. Icon Stroke Normalization owns the drawing weight of the icons themselves; this entry owns the interface, sizing, naming, and accessibility around them.
Edge cases it handles
7
Edge cases it handles
7- More than one icon library in the same codebase produces two versions of the same concept at different weights and different optical sizes. Pick one source, migrate the rest, and remove the abandoned dependency rather than leaving it available.
- An icon that carries meaning on its own — a status dot, an error mark, a delete control with no text — needs a name announced to assistive technology. An icon beside a visible label is decoration and must be hidden, or screen reader users hear the same word twice.
- Icons drawn on different canvases occupy different proportions of their box, so a set nominally at one size will look mismatched. Normalize the optical size so a square and a circle read as equally weighted at the same step.
- Fill and stroke behaviour has to survive a theme change. An icon that relies on a light background will disappear or invert badly in dark mode unless its colour comes from the theme rather than being baked in.
- Directional icons — arrows, chevrons, undo, next and previous — must mirror in right-to-left locales, while icons for time, media playback, and brand marks must not.
- A name that does not exist in the set must fail visibly during development rather than rendering an empty box in production.
- Icons used as the only content of a control still need a minimum touch target, which is larger than the icon itself.
Definition of done
9
Definition of done
9- Every icon in the app is rendered through one interface, and no second icon library remains installed.
- Icon sizes come from a fixed ladder and align optically with adjacent text.
- Decorative icons are hidden from assistive technology and meaningful ones carry an accessible name describing the action.
- Icons inherit colour from their surroundings and remain legible in every theme.
- Directional icons mirror in right-to-left locales and non-directional ones do not.
- An unknown icon name produces a clear failure during development.
- Icon-only controls meet the minimum touch target regardless of the icon's size.
- 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.