Run the full design-to-code roundtrip — analyze a Figma design, surface gotchas, write designer answers back into the file via the Figma Plugin API (use_figma), re-analyze to confirm the gotchas were captured, hand off to figma-implement-design, then optionally register a Code Connect mapping pointing the Figma component at the just-generated code so future roundtrips reuse the implementation. Mutates the Figma file: requires Figma full seat + edit access. TRIGGER when: the user shares a figma.com/design/... URL and wants production-quality code, or asks for "design-to-code roundtrip", "fix the gotchas", or "annotate the Figma file" with implementation context; the user wants a single command for analyze → survey → apply → implement; the user wants Figma annotations or property fixes written before code generation. SKIP when: the user only wants a one-shot readiness report (route to canicode); the user only wants Q&A captured locally without touching the Figma file (route to canicode-gotchas); the user has
Run a gotcha survey on a Figma design — Q&A workflow that captures designer/developer answers locally in .claude/skills/canicode-gotchas/SKILL.md so figma-implement-design can read them at code-gen time. Memo-only: this skill never writes to the Figma canvas. TRIGGER when: the user shares a figma.com/design/... URL and asks to capture implementation context, run a gotcha survey, collect design Q&A, or prepare context for figma-implement-design without mutating the Figma file; the user wants to answer implementation questions for a design before code generation; the user mentions "gotcha survey" or "design Q&A". SKIP when: the user wants the answers written back into the Figma file as annotations or property fixes (route to canicode-roundtrip); the user only wants a one-shot readiness report with no Q&A loop (route to canicode); the user wants to generate code directly with no survey step (route to figma-implement-design).
Analyze a Figma design for development-friendliness and AI-friendliness — produces a graded readiness report listing rule-based issues with severity, affected nodes, and fix suggestions. Read-only: this skill never modifies the Figma file. TRIGGER when: the user shares a figma.com/design/... URL and asks to analyze, score, lint, audit, or check readiness of a Figma design; the user asks "how AI-friendly is this design" or "is this Figma file ready for code generation"; the user wants a one-shot readiness report without a survey or write-back. SKIP when: the user wants to capture designer/developer answers about implementation context (route to canicode-gotchas); the user wants to fix or annotate the Figma file itself (route to canicode-roundtrip); the user wants to generate code directly from the design with no readiness analysis (route to figma-implement-design).