design-analyst

Extract Figma component specifications and generate a Markdown brief.

7|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/kaelig/react-craft --skill design-analyst-kaelig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-analyst
Source: https://github.com/kaelig/react-craft/tree/main/react-craft/skills/design-analyst
Command: npx skills add https://github.com/kaelig/react-craft --skill design-analyst-kaelig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the tedious and error-prone process of translating complex Figma designs into structured, actionable component specifications for development.

Core Features & Use Cases

  • Automated Spec Extraction: Extracts detailed component specifications, including variants, states, design tokens, and responsive behavior, directly from Figma.
  • Completeness Auditing: Validates that all necessary design details are present and flags any gaps for human review.
  • Component Brief Generation: Produces a standardized brief.md file that serves as a single source of truth for developers.
  • Use Case: When a new UI component is designed in Figma, this Skill can be used to automatically generate its technical specification, ensuring consistency and reducing the time spent on documentation.

Quick Start

Use the design analyst skill to process the Figma link https://www.figma.com/design/abc123?node-id=1:42.

Frequently Asked Questions about design-analyst

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

FAQPage Schema
How do I generate component specifications from Figma for developer handoff?

To generate component specifications from Figma, provide a Figma link or Anova YAML export to extract design tokens, variants, states, and responsive behavior into a structured Markdown brief. It validates design details against a checklist and outputs a `brief.md` file for developers.

What is the best way to automate design system documentation from Figma links?

Automating design system documentation from Figma links involves extracting structured component specifications and design tokens directly from the file. This process validates completeness against a checklist and generates a standardized Markdown component brief.

Can I extract design tokens and component variants directly from a Figma file?

Yes, you can extract design tokens and component variants directly from a Figma file by processing the Figma link through an automated extraction tool. It sanitizes the data to capture variants, states, and responsive behavior for technical documentation.

How do I check if my Figma component design is ready for development?

To check if your Figma component design is ready for development, run it through a completeness audit that validates the presence of necessary design details. This process flags any missing specifications, tokens, or states before generating the final component brief.

Does the component brief generation process support Anova YAML exports?

Yes, the component brief generation process supports Anova YAML exports as an alternative to providing a direct Figma link. The tool ingests the YAML file to extract variants, states, and content rules to produce the final Markdown specification.

Why is my Figma to Markdown handoff missing responsive behavior and states?

Your Figma to Markdown handoff may be missing responsive behavior and states if the design lacks these definitions or the extraction tool failed to capture them. A completeness audit flags these specific gaps in the component specifications for human review.