ui-refactor

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.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

The UI Refactor skill is a comprehensive tactical guide for user interface design, focusing on logical rules rather than subjective art. It helps developers and designers transform cluttered interfaces into professional products by optimizing layouts, establishing consistent design systems, and refining visual hierarchy through typography, color theory, and spacing systems.

Use Cases

  • Refactoring Cluttered Interfaces: Apply 'Feature First' workflows and logical spacing scales to clean up complex dashboards and improve user clarity.
  • Establishing Design Systems: Create restrictive, scalable systems for typography, HSL-based color palettes, and spacing to ensure UI consistency across applications.
  • Enhancing Visual Hierarchy: Utilize specific tactics for size, weight, and contrast to guide user attention toward primary actions and key information.
  • Professional CSS Styling: Provide technical guidance on line-height, border-radius, and depth (shadows) to add a high-end polish to web components.
  • Low-Fidelity Wireframing: Solve layout and functionality issues in grayscale before committing to high-fidelity visual details.
nameui-refactor
descriptionTactical 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.

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

  1. 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).
  2. Low Fidelity: Ignore color, shadows, and fonts initially. Design in grayscale using a thick marker or basic wireframes to solve layout and spacing first.
  3. Define Systems: Do not use arbitrary values. establishing restrictive systems for spacing, type, and color immediately.
  4. 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.