figma-generate-library

You can map code-defined design tokens to Figma by running the phase-driven workflow, which handles discovery, token creation, foundations, and component scaffolding to maintain design system alignment.

Building Figma components from code tokens involves a phase-driven workflow spanning discovery, token creation, foundations, components, and QA, utilizing strict phase gates and a shared state ledger for consistency.

Yes, you can safely resume Figma design system generation after interruptions because the workflow uses a shared state ledger and enforces idempotent operations to track progress across phase gates.

Yes, automated token binding and code-syntax integration prevent naming drift by reflecting codebase changes directly in Figma, ensuring consistent naming, variants, and documentation across design and code.

Load this skill in your project root to bootstrap a new Figma design system, generating initial tokens, pages, and component scaffolding directly from your code-defined design tokens.

A key limitation is the strict adherence to sequential phase gates and sequential use_figma calls; skipping phases or concurrent operations disrupts the shared state ledger and breaks the idempotent workflow.