get-contextlisted

# Get Context Run this skill at the start of Product Design requests that ask to design, build, prototype, clone, redesign, extend, or generate product UI directions. Use question mode when any of the following are unclear: - what product, site, feature, workflow, component, or screen is being designed, redesigned, or extended - what the feature, change, app, or website should help the user do - whether the target is a website, desktop/web application, or mobile app when that is not apparent from the visual source or brief Do not re-ask answered questions. When both are clear, play back the brief and defaults in one pithy note, name the next workflow, and continue in the same turn. Playback is not a request for approval. The user can course-correct style, scope, or interactivity at any point. Hard boundary: do not implement UI, scaffold a prototype, start a server, or create files while the design target or intended user outcome is still missing. ## Critical Overrides - Refer to the Plugin router [$index](../index/SKILL.md) before proceeding. - Follow [$critical-overrides](../../references/critical-overrides.md). ## User Context Before starting, load [$user-context](../user-context/SKILL.md) and run its preflight script when local shell access is available. Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material w