Icon Stroke Normalization
Make icons gathered from different sources look as though one hand drew them.
What it adds
A normalization pass over the app's icon artwork unifying stroke weight, terminals, corner treatment, and visual density.
What your agent is told to do
5
What your agent is told to do
5-
1
Lay the whole icon set out at one size on one background and identify the outliers: strokes that are heavier or lighter than the rest, corners that are sharp among rounded ones, glyphs that carry twice as much detail as their neighbours.
-
2
Agree one stroke weight, one terminal shape, and one corner radius for the set, and rework the outliers to match rather than adjusting the majority to accommodate them.
-
3
Make stroke weight hold its apparent thickness across the size ladder. An icon scaled down without adjustment reads thin and faint at the smallest step, which is where most icons in an interface actually live.
-
4
Do not normalize the silhouette along with the stroke. An icon that has lost its distinguishing shape is consistent and useless, and users navigate by outline before they see detail.
-
5
The size ladder, naming, alignment, and accessibility rules belong to Icon System; this entry changes only the artwork. Apply it after the set has been consolidated, or the work is done twice.
Edge cases it handles
7
Edge cases it handles
7- Brand marks, third-party logos, and deliberately filled icons must be left alone. Redrawing a logo to match an internal stroke weight is a trademark problem as well as a recognition problem.
- An icon that reads clearly at the largest step can collapse into a smudge at the smallest, where detail merges and gaps close. Test every icon at the smallest size it is actually used at, not at the size it was designed at.
- Active and inactive variants — a filled and an outlined bookmark, a solid and hollow star — must stay recognisably the same icon. Different silhouettes for the two states make the toggle read as two different controls.
- Some icons genuinely need to break the rule to stay legible. Record each exception and the reason, so the next person does not normalize it back and undo the fix.
- Icons sourced later will drift from the set again. Define what a new icon has to satisfy before it is added, and check it at review time rather than discovering the mismatch in production.
- Pixel alignment matters at small sizes: a half-pixel stroke offset renders blurry on standard-density displays even when the geometry is correct.
- Normalization must not change an icon's optical weight relative to adjacent text, or the icon will either dominate or disappear beside its label.
Definition of done
9
Definition of done
9- The icon set renders at a single stroke weight with consistent terminals and corner treatment.
- Apparent stroke thickness holds across every step of the size ladder.
- Every icon remains identifiable by silhouette after normalization.
- Brand marks and intentionally filled icons are excluded and documented as such.
- Paired active and inactive variants read as the same icon in two states.
- Documented exceptions exist for every icon that deviates, with the reason recorded.
- Each icon has been checked at the smallest size it is used at in the app.
- 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.