Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

Skip to main content
uSpec now runs on the uSpec Extract plugin. Every spec starts from a Component Markdown file the plugin produces — it saves thousands of tokens per run and captures more component detail than live extraction. See the Component Markdown guide →
uSpec: design system documentation for Figma components
uSpec turns your Figma components into structured documentation from your AI agent. The uSpec Extract plugin captures your component, create-component-md turns that capture into a single .md spec you can take anywhere, and the create-* skills render that spec into Figma as annotation frames. Works with Cursor, Claude Code, and Codex.

Start here: Component Markdown

Your component. One .md file. Anywhere.

New in v2.0. Your design system source of truth, in one markdown file per component. Covers API, structure, color, and screen-reader behavior. An artifact that LLM tools can build from and humans can query.

Render into Figma

Once you have a component .md, the create-* skills render annotation frames directly into your Figma file, next to the component. They read from the .md you generated — they no longer re-extract from a Figma link.

Component Anatomy

Numbered markers and attribute tables for every element

Component API

Properties, values, defaults, and configuration examples

Component Properties

Variant axes, boolean toggles, and variable mode exhibits

Component Color

Design token mapping for every element and state

Component Structure

Dimensions, spacing, and padding across density and size variants

Screen Reader

VoiceOver, TalkBack, and ARIA accessibility specs

Motion

Animation timeline bars and easing details from After Effects

How it works

Every spec flows through one pipeline, with the Component Markdown file at its center:
1

Extract

Run the uSpec Extract Figma plugin on your component to produce a _base.json capture of every variant, token binding, and sub-component.
2

Generate the .md

Run create-component-md against the _base.json. It runs four parallel interpretation agents (API, structure, color, voice) and writes a single .md specification to disk — your source of truth.
3

Render into Figma (optional)

Point any create-* skill at the .md to render that section as annotation frames next to the component. These skills read from the .md; they do not re-extract from Figma.
create-motion is the one exception: it renders a timeline from an After Effects export and does not use the Component Markdown pipeline.

Get started

Setup

Set up your AI agent, Figma MCP, and your template library.

Create your first spec

Prompt format, available skills, and tips for better output.
Morty Proxy This is a proxified and sanitized view of the page, visit original site.