What problem does it solve? Teams need to validate user flows and visual design before writing backend logic, but building throwaway mockups wastes effort. This Skill produces clickable static views (landing, auth, app screens, legal pages, error pages) built directly on the project's design system, so the prototype later gets connected rather than discarded. ## Core Features & Use Cases - Screen inventory from a standard catalog: Covers public pages (landing, pricing, 404/500), legal pages, auth flows, and the critical-path app views, checked against the screen map in docs/architecture/screens.md. - Token-based construction: Builds views with design/tokens.css and native HTML primitives (<dialog>, <details>, popover), including loading/empty/error states, light/dark mode, and es/en text support. - Real navigation and validation: Links work across views so the prototype can be walked end-to-end against the critical journey, with a final review listing design decisions and which view to connect first. - Use Case: During the definition sprint, ask for the prototype and receive a complete clickable set of static views — landing, login, dashboard, and legal pages — styled with the design system and ready for stakeholder review. ## Quick Start Ask the assistant to build the clickable static prototype of the product views using the design system tokens.
