ui-spec

# UI Specification ## Overview Turn a selected visual source and verified product facts into an implementation-ready UI contract, then hand it to `dev-frontend`. This Skill specifies an accepted direction; it does not explore visual directions, generate images, build prototypes, or edit product source. ## Workflow 1. Read effective repository guidance and run `git status --short` before planning an authorized artifact write. 2. Fix the selected visual source: a user-selected Product Design result, supplied screenshot/mockup/frame, accepted current surface, or accepted shared visual baseline. Record identity, revision, approval, rights status, `use`, and `ignore` boundaries. 3. Require the repository-root `DESIGN.md` as the single source of truth for shared visual semantics. If it does not exist, copy [assets/DESIGN.md](assets/DESIGN.md) as the structural starter, replace every placeholder from verified sources, omit unverified token groups, obtain named human approval, and validate it before authoring Feature Specs or shared-system changes. 4. Define implementation slices: one Feature Spec per confirmed page/flow/domain; for multiple independent domains, create one shared index plus one independently loadable contract per slice and load [references/multi-surface.md](references/multi-surface.md). 5. Select one profile: - **Feature Spec (default):** reuse current shared systems unless shared semantics truly change. - **Design System Spec (conditional):** only when sha...