figma-design-expert

Generate Figma design-system metadata packages with YAML frontmatter and Markdown instructions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/aiguy611/cc-tools --skill figma-design-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-design-expert
Source: https://github.com/aiguy611/cc-tools/tree/main/.github/skills/figma-design-expert
Command: npx skills add https://github.com/aiguy611/cc-tools --skill figma-design-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardize and accelerate Figma-driven design workflows and documentation.

Core Features & Use Cases

  • Auto-invocation when using Figma MCP tools or discussing design systems, color palettes, typography, component design, visual design, accessibility, and framework styling (React/Vue/Tailwind/Flutter).
  • Provides a structured frontmatter (name, description, version) and a rich Markdown body with operational instructions loaded into context.
  • Includes references to MCP tooling docs and framework mappings to guide outputs.

Quick Start

Generate a complete Figma design-system metadata package from the current document.

Frequently Asked Questions about figma-design-expert

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

FAQPage Schema
How do I standardize Figma design tokens for UI components?

Standardizing Figma design tokens involves applying structured YAML frontmatter and Markdown instructions to enforce consistent color, typography, and component styling across your design system. This ensures cross-framework alignment for React, Vue, Tailwind, and Flutter.

What is the best way to document Figma design systems for cross-framework styling?

Documenting Figma design systems is best achieved by generating a metadata package with structured frontmatter and a rich Markdown body. This operationalizes design reviews, tokenization, and framework mappings to guide styling outputs.

How do I check accessibility compliance in a Figma design system?

Checking accessibility compliance in a Figma design system requires applying operational instructions loaded into context during design reviews. This enforces accessibility standards alongside color and typography system standardization.

Does this approach work with Figma MCP tools for UI/UX tokenization?

Yes, it integrates with Figma MCP tools by auto-invoking when discussing design systems, color palettes, and UI/UX tokenization. It links directly to MCP tooling docs and framework mappings to guide standardized outputs.

Can I use Figma design system metadata for React and Flutter framework styling?

Yes, you can apply generated Figma design system metadata for React and Flutter framework styling. The skill includes framework mappings that translate design tokens and visual design rules into cross-framework styling outputs.

Why do I need YAML frontmatter for Figma design system documentation?

YAML frontmatter is needed for Figma design system documentation to provide a structured name, description, and version for design rules. This standardizes the metadata package and accelerates Figma-driven design workflows.