uikitlisted

# uikit AI-generated UI has a signature. Three equal feature cards, a violet gradient, Inter on slate-900, a div-built fake dashboard in the hero, `01 / 02 / 03` eyebrows over content that isn't a sequence. None of these are bugs and no test catches them. They are **defaults, reached for because the model had no reason to reach anywhere else.** uikit is the reason. It supplies the constraint that makes a UI decision *this project's* decision, and it names the tells so they can be avoided deliberately rather than reproduced accidentally. The whole skill hangs off one idea: **taste is spent only where nothing else constrains the choice.** A project with a recorded design system gets consistency. A project with shipped components gets conformity. A greenfield project gets a point of view drawn from its own subject matter. None of them get a default. That is [the precedence ladder](#the-precedence-ladder), and every other section defers to it. ## What uikit is not - **Not a design-system recorder.** `DESIGN.md` has one owner, and it isn't this skill. uikit reads it and never writes it, because a skill that both invents the taste and records it can't be held to either job honestly. - **Not a taste library.** No bundled palettes, no font pairings, no style catalog. A lookup table of 161 palettes is exactly how every project styled from it ends up looking like every other one. - **Not the code reviewer.** Convention-fit, correctness, and completeness are a general review's job.