ui-refactor
Skill1 starsChanged 5 months agoMITView on GitHub
Tactical user interface design guide for fixing layouts, selecting colors/fonts, and creating professional UIs. Use when the user asks to "make this look better," needs help with CSS/styling decisions, wants to create a design system, or needs to fix a cluttered interface.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LovroPodobnik/refactoring-ui-skillword for word, first seen Jan 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- LovroPodobnik/refactoring-ui-skill★ 49100% same
Edited · 0
None found.
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 repository20 other files it gives its agents.
- system/CLAUDE.mdCLAUDE.md
- design-sub-agentSkill
- design-taste-frontendSkill
- emil-design-engSkill
- full-output-enforcementSkill
- generate-daily-scheduleSkill
- gpt-tasteSkill
- grill-with-docsSkill
- high-end-visual-designSkill
- improve-codebase-architectureSkill
- market-researchSkill
- minimalist-uiSkill
- motion-animationsSkill
- nodejs-expertSkill
- playwright-cliSkill
- redesign-existing-projectsSkill
- scroll-videoSkill
- skill-builderSkill
- ui-ux-pro-maxSkill
- ux-heuristicsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Feature First: Do not start by designing a "shell" (nav bars, sidebars).
- Distinctive: line 14
Define Systems: Do not use arbitrary values.
- Distinctive: line 29
Limit Choices: If you can't decide between two options, you have too many choices.
- Distinctive: line 33
Complexity: Do not design for edge cases first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
UI Refactoring and Design
This skill applies tactical, logical rules to user interface design. It prioritizes clarity, hierarchy, and systems over "artistic talent."
Core Workflow
- Feature First: Do not start by designing a "shell" (nav bars, sidebars). Start with the specific functionality (e.g., the search form, the contact card).
- Low Fidelity: Ignore color, shadows, and fonts initially. Design in grayscale using a thick marker or basic wireframes to solve layout and spacing first.
- Define Systems: Do not use arbitrary values. establishing restrictive systems for spacing, type, and color immediately.
- Refine: Apply specific tactics for hierarchy, depth, and polish.
Domain-Specific Tactics
Consult these references for specific implementation rules:
- Making elements stand out/fit in: See hierarchy.md (Size, weight, contrast, semantics).
- Whitespace and alignment: See layout-spacing.md (Grids, spacing scales, density).
- Text and fonts: See typography.md (Type scales, line-height, fonts).
- Colors and palettes: See color.md (HSL, saturation, accessible contrast).
- Images, shadows, and polish: See depth-and-polish.md (Light sources, assets, finishing touches).
Quick Heuristics
- Limit Choices: If you can't decide between two options, you have too many choices. constrain your inputs (colors, font sizes, spacing) to a pre-defined scale.
- Personality:
- Serious/Elegant: Serif fonts, sharp corners, gold/blue colors, formal language.
- Playful/Friendly: Rounded sans-serifs, large border-radius, pink/orange, casual language.
- Complexity: Do not design for edge cases first. Design the "happy path" (simple version), then iterate for complexity.
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.