Overview
The UI standards: components and styling.
- Communicate State - every state is visible, never let error look like empty
- Never Obscure Information The User Needs - never collapse distinct states or offer ambiguous choices
- Pixel-Perfect Design Check - compare app and design side by side at the widths that matter
- UI Component Design - shared ui is pure: inputs, slots, strict BEM
- UI Components First - use existing design-system and shared UI components, and add one rather than roll custom
- UI Layout Via Slot Composition - layout through generic slots, not config props
- UI Library Is Domain-Agnostic - ui stays domain-agnostic, and domain maps live in the app layer
- UI Refactor: Preserve, Don't Redesign - a ui extraction looks exactly as before, and differences become variants
- UI Styleguide - every workspace with a ui layer gets a styleguide with variants and a testbox
- UI Variants By Function, Not By Color - variant inputs are named by function, not color
- Validation Errors Fire On Submit - submit reveals validation errors from any gesture
- Walk The User's Journey - design and check every screen as the user's journey: who, experiencing what, wanting what, the next question at each step. Show what means something to the user