refactoring-ui
Skill16 starsChanged 7 months agoMITView on GitHub
Tactical rules for making interfaces look intentional and polished. Specific, actionable fixes for the most common visual problems. Triggers on "my UI looks off", "fix the design", "visual hierarchy", "polish the UI", "refactoring ui".
19 other projects use a version of this.
Adopted by
Most recently taken up by
- BuilderIO/builder-agent-skillstheir own version, first seen Nov 8, 2026
- LongJohnSilver1504/claude-skillstheir own version, first seen Nov 8, 2026
- skygenesisenterprise/notploytheir own version, first seen Nov 1, 2026
- Design-of-Man/claude-skillstheir own version, first seen Oct 30, 2026
- nurmdrafi/pi-nativetheir own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use prototype and grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 4 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 4 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- wondelai/skills★ 2.6ksame name
- s0xDk/refactoring-ui-skill★ 500same name
- jaywilburn/refactoring-ui-skill★ 28same name
- BuilderIO/builder-agent-skills★ 16same name
- czyt/tinyskills★ 7same name
- itsyasirkhandev/skills★ 4same name
- nurmdrafi/pi-native★ 4same name
- anis-dr/skills★ 3same name
- eXodes/skills-workspace★ 3same name
- Adhamxon/claude-code-skills★ 2same name
9 more not listed
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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- actSkill
- security-checkSkill
- environment-checkSkill
- run-verificationSkill
- refactorSkill
- debug-session-archivedSkill
- generate-guardsSkill
- check-anthropicSkill
- code-reviewerSkill
- code-reviewSkill
- debug-sessionSkill
- end-sessionSkill
- evolve-checkSkill
- evolveSkill
- fix-bugSkill
- forgetSkill
- frontend-designSkill
- guardSkill
- kit-healthSkill
- learnSkill
- map-codebaseSkill
- modeSkill
- parallel-prototypesSkill
- planSkill
- powershell-safeSkill
- product-riskSkill
- progress-reportSkill
- prototype-hypothesisSkill
- recallSkill
- scan-codebaseSkill
- scan-conventionsSkill
- search-firstSkill
- search-memorySkill
- shadow-codeSkill
- skill-creatorSkill
- smart-resumeSkill
- start-sessionSkill
- strategic-compactSkill
- tourSkill
- ux-heuristicsSkill
- verification-loopSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
Space between sections > space within sections: Use 2-3x more space between unrelated sections.
- Distinctive: line 51
Never use black for shadow color: Use a darkened version of the background color.
- Distinctive: line 71
Never use grey on a colored background: Use a lighter tint of the background color instead.
- Very specific: line 87
Letter spacing for all-caps: Always add letter-spacing: 0.05-0.1em to all-caps text.
- Distinctive: line 93
When something looks wrong, work through this order:
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Refactoring UI
Tactical rules for making interfaces look intentional, professional, and polished. Specific, actionable fixes for the most common visual design problems.
Trigger: "my UI looks off" / "fix the design" / "visual hierarchy" / "polish the UI" / "refactoring ui"
Core Approach
Work in grayscale first. Solve layout, spacing, and hierarchy before introducing color.
Design systems beat one-off decisions. Define spacing scale, type scale, color palette — apply consistently.
Hierarchy
Use all four sources:
- Size — larger = more important
- Weight — bold = more important
- Color — darker = more important; secondary content uses muted color
- Spacing — related elements sit closer
De-emphasize to create contrast. Making less-important things lighter is often more effective than making important things bolder.
Labels vs. values. Labels (name, date, status) are secondary — make them smaller/lighter. Values are primary.
Whitespace
Start with too much, then remove. Most designs are too dense.
Dense != information-rich. Dense layouts feel cheap. Whitespace signals quality.
Space between sections > space within sections. Use 2-3x more space between unrelated sections.
Shadows
Two-part shadows are more realistic:
- Small, sharp, close shadow (1-2px offset, no blur, 0.1 opacity)
- Larger, blurred ambient shadow (4-8px offset, 8-16px blur, 0.05 opacity)
Never use black for shadow color. Use a darkened version of the background color.
Don't apply shadows everywhere. Reserve for: floating cards, dropdowns, modals, hover states.
Borders
Use less of them. Most of the time you need better spacing or a background color change.
Four alternatives to borders:
- Background color — slightly different surface color
- Box shadow — subtle shadow instead of border
- Spacing — more whitespace creates separation
- Bold heading — section title creates separation implicitly
Color
Never use grey on a colored background. Use a lighter tint of the background color instead.
One accent color. Everything interactive uses it. Everything else does not.
Define a full 9-step scale (100-900) for each color in your palette.
Typography
Don't use more than two typefaces.
Line height scales inversely with font size. Large headings: 1.1-1.2. Body text: 1.5-1.6.
Limit your type scale. Pick 6-8 sizes: 12, 14, 16, 18, 24, 30, 36, 48.
Letter spacing for all-caps. Always add letter-spacing: 0.05-0.1em to all-caps text.
Refactoring Diagnostic Order
When something looks wrong, work through this order:
- Hierarchy problem? Is there a clear dominant element?
- Spacing problem? Too dense? Inconsistent padding?
- Color problem? Low contrast? Too many competing colors?
- Typography problem? Too many sizes? Inconsistent weights?
- Shadow/border problem? Too many borders? Shadows too dark?
- Component problem? Missing interaction states? Inconsistent radius?
Fix in this order. Hierarchy first — it usually solves the other problems.
Quick Wins
| Problem | Fix |
| Everything same visual weight | Pick one primary element per section, de-emphasize rest |
| Looks like a form, not a product | Add generous padding, remove borders, increase section spacing |
| Colors feel muddy | Saturate more aggressively; add colorized greys |
| Shadows look fake | Use two-part shadows; never pure black |
| Typography unfinished | Tighten heading line height; add letter-spacing to all-caps |
| Terrible on mobile | Check at 375px; ensure touch targets >= 44pt |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

