refactoring-uilisted
Install: claude install-skill whoiscarlo/agent-skills
# Refactoring UI
Practical rules for making interfaces look designed, distilled from the book
*Refactoring UI* by Adam Wathan and Steve Schoger. Rules below are paraphrased.
Pixel values for the spacing and type scales are reconstructed from the book's
example figures; they match Tailwind's default scales.
How to use this skill: pick the chapter that matches the problem, apply the
rules in order, then run the checklist at the end before calling the work done.
---
## 1. Starting from scratch
**Start with a feature, not a layout.**
Why: the nav, sidebar and shell depend on features you have not designed yet.
Design the actual thing first (a search form, a pricing card, an archive grid).
**Design in grayscale first. Add color last.**
Why: it forces spacing, contrast and size to carry the hierarchy. A design that
works in grey gets better with color; one that needs color to work is fragile.
**Ignore detail early.** Skip fonts, shadows and icons until the layout works.
Why: low-level choices slow you down and are cheap to change later.
**Design the smallest useful version.** Do not draw features you cannot ship yet.
Why: a half-built "nice to have" blocks the whole feature from shipping.
**Work in short cycles.** Design a simple version, build it, fix what breaks, repeat.
Why: real edge cases show up in a working UI, not in a mockup.
**Choose a personality on purpose.** It is set by a few concrete levers:
- Font: serif reads elegant or classic, rounded sans reads playful