ui-speclisted

# 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/image ID, approval, rights status, `use` and `ignore` boundaries, target viewport/state, and source limitations. When a current runtime exists, load [references/frontend-visual-evidence.md](references/frontend-visual-evidence.md) and request same-round, same-viewport/state source and runtime captures from `ops-browser` without operating the browser here. For implicit routing, do not trigger this Skill when no selected visual source or accepted existing UI surface is available; route to `product-spec` for unresolved behavior or host Product Design for visual exploration. If this Skill is already explicitly invoked without that source, stop as `evidence-incomplete` instead of fabricating one. 3. Resolve the approved `<design-root>` from effective guidance, build ownership, and shared consumers. Require `<design-root>/DESIGN.md` as that boundary's single s