Skip to main content
This guide walks you through creating your first specification for a UI component.
This guide assumes you’ve completed the Setup guide. If you haven’t configured Cursor, the Figma Console MCP, and the template library yet, do that first.

Step 1: Write your prompt

Every prompt follows the same format:
@skill-name [Figma link] + additional context
Reference a skill, paste a Figma link, and describe anything the agent can’t infer from the design: states, variants, behavior, or interaction details.

Example prompt

@create-voice https://www.figma.com/design/abc123/Components?node-id=100:200

This is a primary action button with enabled, hover, pressed, and disabled states.
The button has a text label and an optional leading icon.

Available skills

SkillWhat it generates
@create-anatomyNumbered markers on a component with an attribute table
@create-propertyVariant axis and boolean toggle exhibits with instance previews
@create-voiceScreen reader specs for VoiceOver, TalkBack, and ARIA
@create-colorColor token annotations for all elements and states
@create-apiProperty tables with values, defaults, and examples
@create-structureDimensional specs for spacing, padding, and sizing
@create-changelogNew changelog with initial entries
@update-changelogAppend entries to an existing changelog
@convert-changelogExtract an existing Figma changelog to JSON

Step 2: Watch it render

The agent renders the documentation directly in your Figma file:
1

Template import

The agent imports the documentation template into your current Figma page.
2

Content population

Component name, guidelines, properties, and tables are filled in automatically.
3

Section cloning

Sections are cloned for each variant, state, or property in your component.
4

Validation

A screenshot is captured and verified. Issues are fixed automatically.
If a documentation frame appears in your Figma file, your setup is working correctly.

Result

The agent creates a documentation frame with:
  • Component name and guidelines
  • Formatted tables and properties
  • Placeholder areas for component previews

Tips for better output

Be specific about states

Mention all states (selected, disabled, expanded) in your prompt. The agent cannot infer states that aren’t visible in the current Figma frame.

Describe the parts

For complex components, describe the interactive elements:
  • “This is a tooltip. The bell icon triggers it, and the bubble appears on hover and focus.”
  • “This is a tab bar with 3 tabs. Only one can be selected at a time.”

Next steps