figma-design-screenslisted

# Figma Design Screens ## Overview The process is universal. Everything product-specific is discovered in the project, never assumed. First action, every time: check `<project>/.claude/design.md`. No file → follow `references/setup.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. | Project state | Where style comes from | Skipped | |---|---|---| | Design system exists | the design system is law | direction, typography, palette phases | | No design system, screens exist | existing screens in Figma | same | | Neither | external references, curated by the user | nothing | ## Improving a product that already ships When the task is to fix a live product rather than add screens to it, the current interface is captured and audited **before** anything is redrawn — `references/audit-existing.md`. That audit is what every later claim of "this is better" gets measured against, so a wrong note there becomes a wrong screen two phases on: on a 64-note audit one note in four was wrong on the first pass, and the errors were in the retelling, not in the observation. Skipping the audit doesn't remove the phase, it relocates it — without a recorded defect you end up arguing whether th