figma-generate-design

Build or update Figma screens using published design system tokens.

2|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Sacred-G/oh-my-claw --skill figma-generate-design-sacred-g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-design
Source: https://github.com/Sacred-G/oh-my-claw/tree/main/secure-openclaw/skills-main/skills/.curated/figma-generate-design
Command: npx skills add https://github.com/Sacred-G/oh-my-claw --skill figma-generate-design-sacred-g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates human descriptions or code-based page requirements into fully structured Figma screens by reusing a published design system, avoiding manual recreation and ensuring visual parity with system components.

Core Features & Use Cases

  • Reuse published design system components, variables, and styles to assemble screens rather than drawing primitives.
  • Update existing screens by swapping components and adjusting text properties without breaking layout.
  • Use case: convert a page description into a ready-to-ship Figma frame aligned to tokens and variants from the design system.

Quick Start

Build a new screen in Figma from the provided code description and design system tokens.

Frequently Asked Questions about figma-generate-design

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

FAQPage Schema
How do I generate Figma screens from code or text descriptions?

To generate Figma screens from descriptions, the Skill translates human text or code-based page requirements into fully structured frames by reusing a published design system. This avoids manual recreation and ensures visual parity with system components.

How do I update existing Figma pages without breaking the layout?

To update existing Figma pages without breaking layout, the Skill swaps components and adjusts text properties using design system tokens. This maintains the original layout structure while ensuring the updated elements align with system variants.

Do I need a published design system to build screens in Figma?

Yes, you need a Figma file with a published design system and an MCP workflow to fetch and apply components, variables, and text or effect styles. The Skill leverages these design system tokens instead of hardcoded values to assemble screens.

Can I reuse design system variables and styles instead of drawing primitives?

Yes, you can reuse published design system components, variables, and styles to assemble screens rather than drawing primitives. The Skill fetches these tokens and component instances via an MCP workflow to apply them directly to the canvas.

What is the best way to convert a page description into a ready-to-ship Figma frame?

The best way to convert a page description into a ready-to-ship Figma frame is by applying design system tokens and component variants. The Skill processes the description and fetches the matching published components to assemble the frame automatically.

Why should I use design tokens instead of hardcoded values when building Figma screens?

Using design tokens instead of hardcoded values when building Figma screens ensures visual parity with system components and prevents manual recreation errors. It maintains consistency by applying published variables and text or effect styles directly.