What problem does it solve? AI-generated UI has recognizable tells: violet gradients, three equal feature cards, Inter on slate-900, fake dashboards built from divs. No test catches these because they are defaults, not bugs. This Skill supplies the design constraints that make UI decisions deliberate for a specific project, and audits shipped UI for the signatures that give generated work away. ## Core Features & Use Cases - Build mode: Generates UI grounded in a four-rung precedence ladder (DESIGN.md tokens, shipped components, the product's subject matter, or declared stack defaults), with a five-word design read stated before any code is written. - Audit mode: Read-only sweep of named paths or branch diffs against a capped anti-slop catalog and an accessibility floor, reporting findings as blocker, should-fix, or nit with file and line references. - Stack correctness layer: Enforces Tailwind v4 and shadcn/ui rules that prevent silent rendering errors, such as renamed utility classes and semantic token usage. - Use Case: Ask it to build a settings page in a repo with existing components, and it matches the shipped component conventions, declares one signature element, runs a written pre-flight critique, and hands off with the design read repeated for the PR body. ## Quick Start Ask the agent to build the settings page for this project using uikit, or to audit the current UI for AI-generated design tells.