design-screenslisted

# Figma Design Screens ## Overview The process is universal. Everything product-specific is discovered in the project, never assumed. First action, every time: read `<project>/.claude/design.md`. No file → follow `references/setup.md`. If its first line is `# Design — index`, the repository holds several products: match the task to one row of the index — by the Figma file key in the request first, then by the row's task markers. Exactly one match → the product file it names (`design/<slug>.md`) is `design.md` for the rest of this run. Zero or more than one → ask which product in a single line and wait. Format of the index: `references/state.md`. Second action, before any read or write in Figma: make sure you have a link to the frame or page the task is about. No link in the request and none recorded in `design.md` → ask for one in a single line and wait. Guessing which file and page the user means is the most expensive mistake available here: everything after it is built in the wrong place. A from-scratch product has no file yet, and that is not an exemption from the rule — it is the case where the answer is "a new file". Say where it will be created (which plan, drafts or a named project) in the same message as the first phase, before any typography or palette is proposed; the user should never have to ask "where are you going to draw this?" after the direction is agreed. | Project state | Where style comes from | Skipped | |---|---|---| | Design system exists | the de