design-webapp

## Design Webapp — Dashboards, Density, States ### When After `design-system` tokens exist and `design-method`'s Gate 0 has locked register `product` (dense, predictable, motion stays discreet). Read `design-method`'s routing table first — if the surface is a marketing/landing page instead, use `design-web`. ### Input - `design-system.md` — OKLCH palette, typography, spacing density, the 3 dials. - `design-method/references/register/product.md` — the Domain-Specificity Floor and the Product Furniture table (generic KPI ribbon, marketing triad reused in-app, cookie-cutter empty state, undifferentiated settings list, generic nav vocabulary). - The specific page/pattern being built (dashboard, auth, settings, data table, etc.). ### Steps 1. **Register `product` ≠ marketing register.** No hero, no scroll-reveal, no CTA-tricks — this register optimizes for glance-speed, not first impression. Density is a feature: Enterprise Dense / Standard spacing profile (`design-system/references/spacing-density.md`), `MOTION_INTENSITY ≤ 4` by default (`design-motion/references/motion-performance.md`). The Focal-Block Floor and Signature Dominance from `design-web` do not apply here (`register/product.md` §4) — several equal-weight blocks in one viewport is correct, not a defect. 2. **Pick the page pattern** from `references/layouts/pages/` — dashboard, auth-login, auth-register, onboarding, profile, settings, error-pages. Each is a starting structure, not a tem...