figma-generate-library

Automate phased Figma design system creation from code tokens and guidelines.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/calvingit/skills --skill figma-generate-library-calvingit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-library
Source: https://github.com/calvingit/skills/tree/main/external-skills/Design/figma-generate-library
Command: npx skills add https://github.com/calvingit/skills --skill figma-generate-library-calvingit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates a comprehensive, multi-phase workflow to build and maintain a Figma-based design system from code tokens and design guidelines, enabling consistent token binding, component creation, and documentation within a single, reusable unit.

Core Features & Use Cases

  • End-to-end design system construction: Phase 0 discovery, Phase 1 token architecture, Phase 2 foundations, Phase 3 component creation, and Phase 4 QA, all orchestrated with strict sequencing.
  • Idempotent state management: Robust tagging and state ledger to resume work after interruptions without duplicating assets.
  • Code Connect integration and naming discipline: Establishes code bindings, token aliases, and 1:1 mappings to code components for seamless handoff.
  • Foundations-first documentation: Auto-generation of tokens, color swatches, typography, spacing, shadows, and radii for designers and engineers.
  • Flexible, extensible workflow: Supports adding or adjusting phases, integrating external design libraries, and expanding with new token models.

Quick Start

Start the 4-phase workflow from Phase 0 (discovery) to scaffold tokens, pages, and components in your Figma file, then proceed through Phases 1–4 with human checkpoints as needed.

Frequently Asked Questions about figma-generate-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Figma design system creation from code tokens?

Figma design system automation runs a phased workflow from discovery and tokenization to component creation and QA. It uses code tokens and design guidelines to enforce consistent naming, token binding, and component architecture.

What is the best way to bind Figma components to code using Code Connect?

Binding Figma components to code with Code Connect involves establishing 1:1 mappings between design components and code syntax. This integration enables seamless live code handoff and ensures token aliases match their code counterparts exactly.

How do I manage design tokens in Figma without duplicating assets?

Managing design tokens without duplicating assets requires idempotent state management. This approach uses robust tagging and a state ledger to safely resume workflows after interruptions, preventing redundant token or component generation.

Can I resume a Figma design system workflow after an interruption?

Yes, you can resume a Figma design system workflow after an interruption using idempotent state management. A robust state ledger tracks progress across phases, allowing the workflow to continue without duplicating existing foundations or components.

Does this design system workflow support adding external Figma libraries?

Yes, the workflow supports adding external Figma libraries. The phased architecture is flexible and extensible, allowing you to integrate external design libraries and expand the system with new token models as needed.

What phases are involved in automating Figma foundations and componentry?

Automating Figma foundations and componentry involves five phases: discovery, token architecture, foundations, component creation, and QA. Each phase runs sequentially to scaffold tokens, pages, and components with human checkpoints.