ui-design-craftlisted

# UI Design Craft AI-generated UI fails in a recognizable direction: it optimizes for the safe average. The counter is not taste words - it is bans with exact signatures, budgets with numbers, and a mechanical gate. One meta-rule governs the whole file, learned from production tests upstream: **"use sparingly" does not transfer to a generating model; binary phrasing and countable caps do.** ## 0. Classify the surface before generating anything First action, before any code or mockup: - **MARKETING** (landing, portfolio, about, pricing): all sections below apply, §2 layout budgets included. - **APP UI** (dashboard, admin, dense product screens - including the chrome AROUND embedded tables and editors): route the visual system to an established design system (Material, Fluent, Carbon, Polaris, or the project's own); from this file everything EXCEPT §2 applies - the §1 bans, §3 discipline, §4 states, §5 floors, §6 preservation on restyles, and §7's gate minus its MARKETING group. The §2 marketing budgets do NOT apply - a dashboard is allowed to be dense and repetitive. - **HYBRID** (product site with embedded app screens): classify each section. - Out of scope entirely - say so and route: the INTERNALS of data-grid and code-editor widgets (TanStack/AG Grid, Monaco/CodeMirror - theme them through their official APIs; the app chrome around them stays in scope above), native mobile idiom (HIG/Material), realtime collaboration surfaces. - If the project has