What problem does it solve? Product managers often struggle to judge interaction models, information hierarchy, and task paths from abstract discussion alone. This Skill turns a clarified product problem into concrete, viewable interaction directions so the PM can compare real alternatives before committing to a specification. ## Core Features & Use Cases - Interaction Direction Exploration: Generates 2-3 genuinely different directions when real interaction forks exist, or a single recommended draft when they do not, avoiding fake visual-only variants. - Design Basis Compilation: Reads DESIGN.md, the project design system, and existing product pages, then compiles must-inherit, must-reuse, may-change, and guardrail constraints bound to real repository paths. - Visual Quality Gate: Opens each candidate in a real browser or Playwright, runs screenshot-check-fix cycles on desktop and narrow viewports, and blocks unverified drafts from the review board. - Use Case: During module design, the PM needs to decide between a card-based list and a table layout for a task page. The Skill generates both directions covering the full task path and edge states, audits them visually, and presents them on a review board for selection. ## Quick Start Ask the design workflow to explore interaction directions for the current module and present the verified mockups on the review board.