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
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
Radius Scale
Radius Scale
Fix the app's corner radii to a few steps that agree with one another.
What it does
A small radius scale mapped to component roles — controls, cards, overlays, pills, media — and applied throughout.
How it works
- 1 Collect every corner radius in the codebase and reduce it to three or four steps, then assign each step a role: controls and inputs, cards and panels, overlays and sheets, fully rounded pills.
- 2 Set nested radii so the inner corner is smaller than the outer one by roughly the padding between them. An inner element with the same radius as its container leaves a visible sliver of gap at each corner.
- 3 Scale the radius with the component: the step that reads as softly rounded on a small button reads as barely rounded on a large panel, and as a lozenge on a short chip.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/radius-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.