figma-generate-library

Plan and execute end-to-end Figma design-system generation with MCP workflows.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill figma-generate-library-charitablebusinessronin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-library
Source: https://github.com/Charitablebusinessronin/Allura_Memory/tree/main/.opencode/skills/figma-generate-library
Command: npx skills add https://github.com/Charitablebusinessronin/Allura_Memory --skill figma-generate-library-charitablebusinessronin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coordinates end-to-end design-system generation inside Figma MCP workflows, enabling governance, traceability, and reproducible results across discovery, token creation, documentation, component generation, and QA phases.

Core Features & Use Cases

  • Orchestrates multi-phase workflows across 20–100+ tasks with deterministic sequencing and mandatory checkpoints.
  • Maintains a run-scoped state ledger with phase keys to support resumable builds and safe cleanup.
  • Integrates with Code Connect MCP tools to align design tokens and code bindings for Dev Mode handoff.
  • Automatically generates foundations/docs, variable collections, components, and component sets in a cohesive run.
  • Enforces governance gates and human review points to reduce drift between design and implementation.

Quick Start

Begin Phase 0 with discovery, lock scope, then execute Phases 1–4 in order, following the mandatory checkpoints at each stage.

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 end-to-end Figma design system generation across multiple phases?

Automate Figma design system generation by orchestrating multi-phase MCP workflows that sequence discovery, token creation, documentation, component generation, and QA with deterministic checkpoints and run-scoped state tracking.

What is the best way to maintain governance and traceability when creating Figma component libraries at scale?

Maintain Figma component library governance by using a shared state ledger with run IDs, enforcing mandatory review gates across 20–100+ tasks to ensure reproducible results and reduce drift between design and implementation.

Can I resume a Figma design system build if a workflow task fails midway?

Resume interrupted Figma design system builds using a run-scoped state ledger with phase keys that support idempotent retries, allowing safe cleanup and deterministic continuation from the last mandatory checkpoint.

Does this Figma design system workflow integrate with Code Connect for design-to-code handoff?

Integrate with Code Connect MCP tools to align design tokens and code bindings for Dev Mode handoff, ensuring generated Figma variable collections and component sets map directly to implementation.

How do I start a deterministic Figma design system workflow from scratch?

Start by executing Phase 0 discovery to lock scope, then proceed sequentially through Phases 1–4, following mandatory checkpoints at each stage to generate foundations, variables, and components cohesively.

What limitations exist when orchestrating large-scale Figma design system generation via MCP workflows?

Large-scale Figma design system orchestration requires strict adherence to mandatory checkpoints and phase sequencing; skipping governance gates or human review points risks drift and breaks reproducible build state.