What problem does it solve? Teams often start building UI features before agreeing on the look and feel, leading to rework and inconsistent styling. This Skill locks the visual direction first by producing throwaway HTML/CSS mockups and a single durable theme.css file of CSS variables that later ports into the real app's stylesheet. ## Core Features & Use Cases - Plan-first workflow: Reads the project overview for stated look and feel, asks targeted questions about vibe, color, type, and pages, then proposes a plan and waits for approval before writing any files. - Shared theme variables: Writes a single prototypes/theme.css defining surfaces, text, accent, fonts, and scale as CSS variables, so every mockup stays consistent and the theme ports directly into the app's @theme block. - Realistic screen mockups: Generates self-contained plain HTML pages per approved screen with believable content and real UI states, no frameworks or build steps. - Use Case: Before building the first UI feature of a dashboard app, run /prototype to mock the dashboard, settings, and detail pages, iterate on the dark theme in a browser, then hand the approved theme.css to the first /feature build. ## Quick Start Ask the AI to run /prototype and mock up the key screens of your project with a dark minimal theme before building the first UI feature.