figma-generate-design

Builds Figma screens and views from code using design system components, variables, and styles.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/xzedm/clipplic-landing --skill figma-generate-design-xzedm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-generate-design
Source: https://github.com/xzedm/clipplic-landing/tree/main/.agents/skills/figma-generate-design
Command: npx skills add https://github.com/xzedm/clipplic-landing --skill figma-generate-design-xzedm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating an application page, modal, or multi-section view into Figma by hand produces disconnected frames with hardcoded colors and placeholder text. This Skill assembles composed Figma views from the published design system so screens stay linked to real components, variables, and styles. ## Core Features & Use Cases - Design system discovery: Resolves component keys from Code Connect files, existing screens, or library search, plus variables and text/effect styles, before building anything. - Section-by-section assembly: Creates a wrapper frame and builds each section in its own use_figma call, binding variables and importing component instances instead of hardcoding values. - Parallel pixel reference: Runs generate_figma_design alongside the build for web apps to capture exact layout and transfer image fills via imageHash. - Use Case: Convert a React settings modal into Figma by resolving the Button and Input component sets from Code Connect, binding spacing and color variables, then validating each section with screenshots. ## Quick Start Take this settings page from my React app and build it in Figma using our design system components.

Frequently Asked Questions about figma-generate-design

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

FAQPage Schema
How do I convert a React page into a Figma screen?▼

Read the source to identify sections and components, resolve component keys from Code Connect files or existing screens, then build each section inside a wrapper frame using imported component instances and bound variables. Validate each section with get_screenshot before continuing.

How do I find Figma design system components from code?▼

Check Code Connect files (*.figma.ts, *.figma.tsx) next to each component and parse the Figma URL for fileKey and nodeId, then resolve the component key via use_figma. If unresolved, inspect existing screens' instances or use search_design_system as a last resort.

Why are my Figma variables not showing up with getLocalVariableCollectionsAsync?▼

That API only returns local variables defined in the current file; remote published library variables are invisible to it. Run search_design_system with includeVariables: true to discover library variables, then import them by key.

Can this skill handle images when building Figma screens?▼

The use_figma Plugin API cannot fetch external image URLs, so run generate_figma_design in parallel to rasterize images into Figma. Then copy the imageHash values from the capture's image fills onto the corresponding frames in your output.

When should I use figma-use instead of figma-generate-design?▼

Use figma-use directly when creating new reusable components or variants rather than composed views. Use figma-code-connect when writing Code Connect mappings. This skill is for building or updating full pages, modals, drawers, and multi-section containers.