figma-generate-library

Builds Figma design systems with variables, components, and theming from a codebase.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill figma-generate-library-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-generate-library
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/plugins/cache/openai-curated/figma/314574a046f21938025ae443f9c6dbbd0c2c9b7a/skills/figma-generate-library
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill figma-generate-library-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Translating a codebase's design tokens and components into a structured Figma design system is slow and error-prone when done manually, and one-shot automated attempts produce broken or inconsistent results. This Skill orchestrates a phased, checkpoint-driven workflow that creates variables, component libraries, theming modes, and documentation in Figma that match the code. ## Core Features & Use Cases - Token and Variable Creation: Builds primitive and semantic variable collections with Light/Dark modes, scopes, aliases, and code syntax matching the codebase's CSS variables. - Component Library Construction: Creates components one at a time with auto-layout, variant matrices, component properties (TEXT, BOOLEAN, INSTANCE_SWAP), and full variable bindings. - Theming and Documentation: Sets up file structure with cover pages, foundations documentation, color swatches, and type specimens, plus Code Connect mappings to code components. - Use Case: A team wants their React component library mirrored in Figma with matching tokens and dark mode. The Skill analyzes the codebase, locks scope with the user, then builds tokens, pages, and components across validated phases. ## Quick Start Ask the AI to build a Figma design system from your codebase using the figma-generate-library skill, starting with a discovery phase and plan approval.

Frequently Asked Questions about figma-generate-library

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

FAQPage Schema
How do I create a design system in Figma from my codebase?▼

Start with a discovery phase that extracts tokens and components from CSS variables, Tailwind config, or theme objects, then lock scope with the user. Build foundations (variables and modes) before components, with user checkpoints between each phase.

How to create Figma variables with light and dark modes?▼

Create a variable collection with Light and Dark modes, add primitive variables with raw values in a single mode, then create semantic variables aliased to primitives with mode-specific values. Set scopes and code syntax on every variable.

Can I build Figma components with variants programmatically?▼

Yes, create one component per variant combination, then call figma.combineAsVariants to form a component set. Variants stack at (0,0) after combining, so you must manually position them in a grid and resize the set.

Why do my Figma variant components all overlap at the top left?▼

combineAsVariants places all children at coordinates (0,0) by default. After combining, manually assign x and y positions to each variant in a grid layout, then call resizeWithoutConstraints so the component set frame fits its contents.

What are the limitations of automated Figma design system creation?▼

It is never a one-shot task; builds require 20-100+ sequential Plugin API calls with user checkpoints. use_figma calls cannot be parallelized, getPluginData is unsupported (use shared plugin data), and variant matrices should stay under 30 combinations.