Responsive Grid Tokens
Express columns, gaps, and spans as shared tokens rather than per-component guesses.
What it adds
A token set describing column counts, gutters, and span behaviour at each breakpoint, used by every grid in the app.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Let grids collapse on the content's minimum width rather than on a fixed column count, so a card that needs a certain width to be legible triggers the reflow itself.
-
5
Breakpoint names and values are owned by Breakpoint Token System and outer page widths by Container Width System. Consume both here and do not define a second set of thresholds inside the grid.
Edge cases it handles
7
Edge cases it handles
7- A grid nested inside another grid inherits gutters it should not, producing a visibly wider gap in the inner layout. Nested grids need their own gutter step or an explicit reset.
- Collapsing purely on breakpoints ignores the container, so a four-column grid placed inside a narrow sidebar will squeeze its cards below legibility on a wide screen. The minimum content width, not the viewport, should drive the reflow.
- Reordering items visually with the grid leaves the source order untouched, so keyboard and screen reader users receive a sequence that contradicts what is on screen. Keep visual order and source order aligned.
- A grid must not assume how many children it will receive. Three cards in a four-column layout, or a single card, must both look deliberate rather than leaving a ragged hole.
- Items of unequal height will either stretch to the tallest in the row or leave gaps, and which of those is correct depends on the content, so it has to be a stated choice per grid.
- A grid rendered inside a resizable or split layout changes width without the viewport changing at all, so anything keyed to viewport width alone will be wrong there.
- Long unbroken strings and wide media inside a cell will push the column past its share unless the cell is allowed to shrink below its content.
Definition of done
9
Definition of done
9- Every grid in the app draws its column count, gutters, and spans from shared tokens.
- Gutter values come from the app's spacing scale, not from grid-specific numbers.
- Nested grids do not inherit the outer gutter.
- Grids reflow on content minimum width, so they behave correctly inside narrow containers as well as narrow viewports.
- Visual order matches source order in every grid.
- Grids render sensibly with one item, with a partial final row, and with items of unequal height.
- No grid defines its own breakpoint values.
- 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
Container Width System
Container Width System
Give pages a few defined widths instead of a different max-width on every screen.
What it does
A small set of named page widths — narrow, standard, wide, and full-bleed — applied consistently across the app.
How it works
- 1 Measure the max-width used on every top-level page and group them. Settings forms, prose, dashboards, and data tables usually want three or four distinct widths between them, not the eleven the codebase currently has.
- 2 Pick each width from the content it holds. A reading column is bounded by comfortable line length, a settings form by field width, and a table by the number of columns that must stay visible.
- 3 Make horizontal page padding part of the container rather than something each page adds, so content never touches the viewport edge on a narrow screen even at the widest setting.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/container-width-system
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.