What problem does it solve? Designing product screens without a consistent design system leads to mismatched tokens, ad-hoc mockups, and poor handoff to engineering. This Skill provides a structured workflow that combines design-system research with Google Stitch screen generation so every screen is grounded in a documented Design Decision Record. ## Core Features & Use Cases - Design system research: Runs ui-ux-pro-max searches to produce a Design Decision Record covering patterns, colors, typography, and UX guardrails before any screen is generated. - Stitch screen generation: Uses Google Stitch MCP tools (list_projects, generate_screen_from_text, fetch_design_md, fetch_screen_code) to create and iterate screens from persona-driven prompts. - Token reconciliation and handoff: Compares Stitch theme tokens against the execution repo (e.g. tailwind.config.js) and delivers screen IDs, export paths, and implementation notes to developers. - Use Case: A product team needs a new checkout flow for a mobile app. The Skill scopes the persona and journey, runs ui-ux-pro-max for the design system, generates Stitch screens, and hands off labeled screen IDs with Tailwind token mappings. ## Quick Start Ask the assistant to design a specific screen for your named product, providing the persona, journey step, and any existing Stitch project ID so it can run the design workflow.