create-ds-component-page

Automate end-to-end Design System component page creation in Figma from prompts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ThanapatJutha/th_gene2-figma-mcp --skill create-ds-component-page
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ds-component-page
Source: https://github.com/ThanapatJutha/th_gene2-figma-mcp/tree/main/packages/gene2-figma-mcp/skills/create-ds-component-page
Command: npx skills add https://github.com/ThanapatJutha/th_gene2-figma-mcp --skill create-ds-component-page

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end process of creating a Design System component page in Figma, turning prompts into a ready-to-ship page that coordinates parsing, exploration of libraries, suggested properties, a showcase, Figma capture, post-processing, and artifact saving.

Core Features & Use Cases

  • CAPTURE-driven workflow (Steps 0–8): always use the capture path unless explicitly overridden.
  • Dual layout strategies: per-property items for display sections and cross-product masters for variant generation.
  • Token-aware styling and asset handling: map colors and spacing to design tokens and ensure local assets for dependable captures.
  • Page management and save artifacts: create or reuse a Figma page, promote and combine masters, swap property instances, and save .figma.tsx wrappers and connections.
  • End-to-end design-system component creation for UI libraries (e.g., shadcn/ui, MUI, Chakra) or components like Button, Card, Badge.

Quick Start

Instruct Copilot to follow the CAPTURE workflow to create a DS component page in Figma.

Frequently Asked Questions about create-ds-component-page

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

FAQPage Schema
How do I automate design system component page creation in Figma?

Automate design system component page creation in Figma by parsing user prompts to explore UI libraries, generate showcases, apply token-aware styling, and save artifacts. It follows a CAPTURE-driven workflow to deliver ready-to-ship component pages.

How does token binding work when generating Figma component pages?

Token binding maps colors and spacing to design tokens during component page generation. It ensures local asset handling for dependable captures and saves .figma.tsx wrappers to maintain connections between Figma visuals and code contexts.

Can I generate UI library component pages for shadcn/ui or MUI?

You can generate UI library component pages for shadcn/ui, MUI, and Chakra. The workflow parses your intent, explores the specified library, suggests properties, and creates showcases for components like Button, Card, and Badge.

What is the best way to map component properties for a Figma design system?

The best way to map component properties uses dual layout strategies: per-property items for display sections and cross-product masters for variant generation. This approach coordinates property instance swapping and master promotion on the Figma page.

Do I need an existing Figma page to create design system component showcases?

You do not need an existing Figma page because the workflow manages page creation and reuse automatically. It parses your prompt, generates the showcase, captures it to Figma, post-processes the layout, and saves the resulting artifacts.

Why are my automated Figma component captures missing local assets?

Automated Figma component captures require local assets to ensure dependable rendering during the capture path. The workflow explicitly handles token-aware styling and asset localization to prevent missing visual elements in the final page.