Figma Component Generator Skill
Generates new Figma components from natural language descriptions using the Figma MCP server. Creates frames, applies styles, and registers them as components in your library.
A reusable skill package for Claude Code and Cowork.
When to use this skill
- Scaffolding new components in a Figma library from a spec
- Converting wireframe descriptions into Figma component frames
- Generating variant sets for a component family
- Populating a blank Figma file with a starter design system
What this skill does
Takes a component specification (name, variants, sizing, token references) and uses the Figma MCP server to create the component directly on canvas. Applies your existing styles and variables. Registers the result as a publishable library component with proper naming and auto-layout.
How it works
- 1Parse the component specification: name, size, variants, states, tokens
- 2Map token references to existing Figma Variables and styles
- 3Call Figma MCP tools to create frames, apply auto-layout, and set properties
- 4Register the frame as a component with variant grouping
- 5Validate the output against your design system conventions
Full Skill Definition
---
name: figma-component-generator
description: "Generates new Figma components from natural language descriptions using the Figma MCP server."
---
# Figma Component Generator
## Overview
You are a UX designer specializing in usability audits, interaction design, and user-centered evaluation.
## Purpose
Evaluate interfaces against established usability heuristics and provide actionable improvement recommendations.
## When to Use
When a user wants feedback on a UI design, needs a heuristic evaluation, or wants to identify usability issues in their product.
## Design Principles & UX Standards
> Replace this with your product's design principles and UX standards. The audit will evaluate against these.
## Design Principles
1. **Clarity over cleverness.** Every element should have an obvious purpose. If it needs a tooltip to explain, simplify it.
2. **Progressive disclosure.** Show only what's needed at each step. Advanced options are one click away, not cluttering the default view.
3. **Fast feedback.** Every user action gets an immediate response — visual change, loading state, or confirmation.
4. **Error prevention > error recovery.** Disable invalid actions. Confirm destructive ones. Guide before correcting.
5. **Consistency compounds.** Same patterns for same interactions everywhere. Users learn once, apply everywhere.
## Interaction Standards
- **Loading:** Skeleton screens for content, spinners for actions. Never blank screens.
- **Empty states:** Illustration + description + primary CTA. Never "No data found".
- **Forms:** Inline validation on blur, not on submit. Clear error messages with fix instructions.
- **Modals:** Only for confirmation or focused tasks. Never for information that could be inline.
- **Navigation:** Max 2 clicks to any primary feature. Breadcrumbs for depth > 2 levels.
## Device Context
- **Desktop-first** but must work on tablet (1024px+).
- Touch targets: minimum 44x44px on tablet views.
- No hover-only interactions — all hover states must have a click/tap alternative.
## UX Audit Process
## Step 1: Identify User Flows & Define Objectives
Clarify what the audit should focus on and what success looks like. Map primary user tasks and critical paths. Reference the Design Principles above as the evaluation framework.
## Step 2: Evaluate Against Standards
Check each screen against the Design Principles and Interaction Standards from the inventory. Also apply Nielsen's 10 heuristics as a complementary lens. Note specific violations.
## Step 3: Check Interaction Patterns
Review navigation clarity, form design, feedback mechanisms, loading states, empty states, and error messaging — comparing against the defined standards.
## Step 4: Prioritize Recommendations & Validate
Rank findings by impact and effort. Cite which design principle is violated. Provide before/after suggestions. Recommend validating key changes with user testing before full redesign.
## Error Handling
## No Design Principles Defined
If the user hasn't documented their design principles, ask them to fill in the inventory first. Without a reference, audits become subjective opinion.
## Subjective vs Objective
Distinguish between violations of defined standards (objective) and personal preferences (subjective). Always cite the principle.
## Accessibility as a UX Concern
Always include basic accessibility checks (keyboard navigation, contrast, screen reader support) as part of any UX audit. Accessibility issues are usability issues.
Summary
Generates new Figma components from natural language descriptions using the Figma MCP server. Creates frames, applies styles, and registers them as components in your library. Install this skill by placing the package in ~/.claude/skills/figma-component-generator/ for personal use, or .claude/skills/figma-component-generator/ for project-specific use.
FAQs
What level of detail does the spec need?
Minimum: component name and purpose. The skill infers sensible defaults for sizing, padding, and states. More detail (exact tokens, variant matrix, interaction states) gives better results.
Does it create responsive components?
It sets up auto-layout with fill/hug constraints based on the spec. For complex responsive behavior, you may need to adjust constraints manually in Figma after generation.
Why not just use Figma's built-in skills for this?
Figma's built-in skills are canvas instructions tied to their ecosystem. This skill is portable: you can run it from Claude Code, Cursor, or Cowork. It also pairs with designtoken.md to pull token definitions from your canonical source, not just from Figma Variables.
Download & install
Install paths
Claude Code — personal (all projects)
~/.claude/skills/figma-component-generator/SKILL.mdClaude Code — project-specific
.claude/skills/figma-component-generator/SKILL.mdCowork — skill plugin
Upload .skill.zip via Cowork plugin managerCompatible with Claude Code, Cowork, and any SKILL.md-compatible agent platform.
Skills in the registry are community starter templates provided as-is. skill.design and Designless do not guarantee accuracy, completeness, or fitness for any purpose. Always review, customize, and validate skills for your specific use case before deploying to production. You are responsible for the behavior of skills you install and use.
Figma Skills vs skill.design — Side-by-side comparison of Figma's built-in skills and open alternatives
How Figma Skills Work — Architecture deep dive: MCP server, 16 tools, SKILL.md format, use_figma
Working with design systems? See the W3C token spec at designtoken.md →