refactoring-ui
Refactoring UI
Good UI design isn't about talent or artistic ability — it's about making deliberate, systematic choices. Every visual decision (spacing, color, typography, depth) has a small set of correct answers that you can learn and apply consistently. This skill gives you those answers.
Core Philosophy
- Start with content, not chrome. Begin with the actual feature and data. Don't start with a navbar and sidebar — start with the content that matters and build outward.
- Work in cycles. Get the structure right first with plain text and basic layout. Then layer in hierarchy, typography, color, depth, and polish — in that order.
- Constrain your choices. Pre-define scales for spacing, font sizes, colors, and shadows. Choosing from a system is faster and more consistent than picking arbitrary values.
- Design every detail deliberately. If you haven't consciously decided on a value, it's probably wrong. Every pixel of spacing, every shade of grey, every font weight should be intentional.
Building New UI
When creating an interface from scratch, follow this sequence:
- Start with the feature, not the layout. Build a single component with real content. Don't think about navigation, sidebars, or page structure yet.
- Establish hierarchy. Decide what information is primary (large, dark, bold), secondary (smaller, medium grey), and tertiary (small, light). Not everything can be important.
- Apply your design system. Use the scales below for spacing, typography, and color. Pick values from the system — never invent new ones mid-design.
- Add depth and polish. Apply shadows for elevation, accent borders for flair, and finishing touches that elevate the design from functional to professional.
More from muco-rolle/skills
write-prd
Collaboratively write a Product Requirements Document through structured interview and codebase exploration. Use when user wants to create a PRD, define requirements, plan a new capability, or write a spec.
11goos-adonis
Use when building, testing, or refactoring AdonisJS v7 applications with test-driven development. Covers outside-in TDD workflow, writing acceptance tests (api-client and browser-client), designing testable services with dependency injection, creating test doubles with container.swap, fixing fragile or slow tests, and restructuring fat controllers into clean service layers
11grill-me
Interview the user relentlessly about a plan or design until reaching a shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
9frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
9write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
5dont-make-me-think
>
4