figma-generate-library

Coordinate token creation, component assembly, theming, and documentation across Figma design-system phases.

12|7|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/allofmeng/streamline_project --skill figma-generate-library-allofmeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-library
Source: https://github.com/allofmeng/streamline_project/tree/main/.agents/skills/figma-generate-library
Command: npx skills add https://github.com/allofmeng/streamline_project --skill figma-generate-library-allofmeng

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides an end-to-end orchestration framework for design systems inside Figma, coordinating token creation, component libraries, theming, and documentation across multiple phases to reduce drift between code and design and to enable replayable builds.

Core Features & Use Cases

  • Phase-driven workflow that covers discovery, foundations, file structure, component creation, and QA with mandatory user checkpoints.
  • Robust state management and idempotency across 20–100 use_figma calls, including run tagging, recovery, and safe cleanup.
  • Reuse and integration: search_design_system, code-connect tooling, and token architecture guidance for consistent designer-to-developer handoffs.
  • Real-world scenario: scale a design system across teams, publish components, and align tokens with code tokens while maintaining parity with the codebase.

Quick Start

To begin, analyze the codebase and Figma, then follow the phased plan to create tokens, components, and documentation.

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 workflows end-to-end?

Automating Figma design system workflows end-to-end involves coordinating token creation, component assembly, theming, and documentation across multiple phases. This process uses a phase-driven workflow with mandatory user checkpoints for discovery, foundations, file structure, component creation, and QA.

How do I maintain code and design parity when creating Figma component libraries?

Maintaining code and design parity when creating Figma component libraries requires aligning design tokens with codebase tokens and using Code Connect tooling. This integration ensures consistent designer-to-developer handoffs and reduces drift between the implemented code and the Figma components.

What is the best way to manage state and rollback during Figma token creation?

Managing state and rollback during Figma token creation relies on state ledger management and reusable scripts to enforce idempotency and safety checks. This ensures reproducible builds by satisfying strict sequencing rules and allowing safe recovery across up to 100 use_figma calls.

Can I use Code Connect to align Figma components with my existing codebase?

Yes, you can use Code Connect to align Figma components with your existing codebase by integrating search_design_system tooling and token architecture guidance. This ensures consistent designer-to-developer handoffs and maintains parity between your Figma design system and codebase.