making-ui-changes
Skill1.2k starsChanged 21 days agoApache-2.0View on GitHub
Read before changing any component, page, or styles. Five moves to change UI without silently breaking another screen - reuse before you create, cover every state, check the blast radius, prove it with a visual test, kill flake at the source.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run these five moves on any UI change.
- Very specific: line 12
Search for an existing component and extend it (variant="danger", a new prop) instead of adding a near-copy.
- Very specific: line 16
Every component or state you add or change owes a story/capture in the _same_ change, never a follow-up.
- Very specific: line 24
Not done until you've looked at what moved: check-visual-changes mid-edit, or the PR check + triage-visual-changes.
- Very specific: line 32
Add to AGENTS.md and CLAUDE.md so this runs on every UI change (setup-visual-testing does this for you):
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Making UI changes
Run these five moves on any UI change.
1. Reuse before you create
Search for an existing component and extend it (variant="danger", a new prop) instead of adding a near-copy. Two components that look the same drift apart. Build net-new only when nothing fits - then it goes through move 2.
2. Cover every state, in the same change
Every component or state you add or change owes a story/capture in the same change, never a follow-up. Don't hand-write one per combination - generate them densely (economical-visual-tests). No visual testing wired yet? setup-visual-testing first.
3. Check the blast radius
Editing a shared component changes every screen that imports it. Grep the importers, decide which ones this touches, and make sure each has a story/capture so the diff will catch it.
4. Prove it with a visual test
Not done until you've looked at what moved: check-visual-changes mid-edit, or the PR check + triage-visual-changes. A story that changed which your diff shouldn't touch is a stop-and-look (usually move 3), not an accept.
5. Kill flake at the source
A story that comes back changed with no real change (clock, live data, animation, randomness) is flake. Fix it at capture time (storybook-/playwright-/vitest-visual-testing) - don't accept it, don't disable the check.
Wire it in
Add to AGENTS.md and CLAUDE.md so this runs on every UI change (setup-visual-testing does this for you):
Before changing any component, page, or styles, read making-ui-changes: reuse before you create, add or update the story/capture in the same change, check the blast radius, and prove it with a visual test.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about FranciscoMoretti/sparka
- FranciscoMoretti/chat-js“Implement Global MCP connectors”GitHub · Dec 9, 2025
- FranciscoMoretti/chat-js“📝 Add docstrings to `better-auth`”GitHub · Oct 17, 2025
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions3 projects use a version of this.
Word for word · 2
- FranciscoMoretti/chat-js★ 1.2k100% same
- FranciscoMoretti/chatjs★ 1.2k100% same
Edited · 1
- uiverify/uiverify★ 26100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-visual-changesSkill
- create-vercel-ai-issueSkill
- dev-auth-bypassSkill
- economical-visual-testsSkill
- generate-code-snippetSkill
- lazy-prefetch-patternSkill
- next-cache-components-adoptionSkill
- next-dev-loopSkill
- next-partial-prefetching-adoptionSkill
- review-docsSkill
- strategic-testingSkill
- triage-visual-changesSkill
- trpc-patternsSkill
- vitest-visual-testingSkill
- worktree-portsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.