figma-generate-design

Create or update Figma screens using published design system components, tokens, and styles.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/HellKaiser45/Podlet --skill figma-generate-design-hellkaiser45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-generate-design
Source: https://github.com/HellKaiser45/Podlet/tree/main/.podlet/skills/figma-generate-design
Command: npx skills add https://github.com/HellKaiser45/Podlet --skill figma-generate-design-hellkaiser45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to create or update Figma screens by reusing a published design system's components, tokens, and styles, avoiding drift between code and design.

Core Features & Use Cases

  • Reuse published design system components, variables, and text/effect styles to assemble screens without rebuilding UI primitives.
  • Import and bind design tokens (colors, spacing, typography) and apply them to frames, components, and text.
  • Use case: rapidly build a new product page by translating code structure into a Figma layout that mirrors the design system.

Quick Start

Provide a Figma file URL or context about the target file and let the skill generate or update screens from the published design system.

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 a published design system?

To generate Figma screens from a design system, provide a Figma file URL or context. The skill loads published components, variables, and text styles via use_figma to assemble full-page layouts or update sections without rebuilding UI primitives.

Can I update individual sections of a Figma page using existing design tokens?

Yes, you can update individual sections within a Figma page. The skill applies bound design tokens, including colors, spacing, and typography, to specific frames or components inside a page wrapper without rebuilding the entire layout.

How do I translate code structure into a Figma layout that matches my design system?

Translating code structure into a Figma layout requires loading your design system components and variables. The skill follows a step-by-step workflow to map code descriptions into Figma frames that mirror centralized design tokens.

Do I need a centralized design system to create Figma screens with tokens?

Yes, a centralized design system is required. The skill relies on loading published design system components, variables, and text or effect styles to assemble screens and avoid drift between code and design.

What is the best way to avoid design drift when updating Figma UI components?

To avoid design drift when updating Figma UI components, reuse published design system tokens and styles. The skill imports and binds these centralized variables directly to frames and text, ensuring code and design stay synchronized.

Why are my Figma screens not reflecting the latest design system variables?

Figma screens may not reflect updated variables if the published design system is not properly loaded. The skill requires explicitly fetching design system components, variables, and styles via use_figma before applying them to page wrappers.