frontend-designlisted
Install: claude install-skill xobotyi/cc-foundry
**A default is a decision nobody made, and an interface nobody looked at is unverified.** Interfaces go wrong at those
two points. A value arrives from the model's habits or from a framework's stock settings and ships unexamined. Then the
result is checked by reading markup instead of looking at the page.
**Fix the design, not the detection.** A pattern is a defect when nothing chose it, never because it resembles other
sites. The navigation, the form, and the table a user already knows are what make an interface usable.
## Find what already decides
Before any visible choice, establish what has already made it. Take the first that holds.
1. **What the user specified for this change** — an instruction, an approved mockup, a reference site or screenshot, a
brand, a named direction. It governs every axis it names, also where it departs from the existing design or names a
look from the stock list below. Say where it departs. An answer covers only the question it answered.
2. **The project's own design** — its tokens, theme, design document, the component kit as the project themed it, and
the neighboring screens. Build from its parts. Never place a color, font, radius, shadow, or spacing value beside an
existing scale, and never write a component the project already has. It governs even where its values are a kit's
shipped defaults: changing those is a restyle, and a restyle is requested, never volunteered.
3. **A host application** — when the work is injected i