figma-spec

Transform screen-inventory and component-inventory into a six-section Figma handoff specification in Markdown.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/bflandev/threadline-ai --skill figma-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-spec
Source: https://github.com/bflandev/threadline-ai/tree/main/skills/figma-spec
Command: npx skills add https://github.com/bflandev/threadline-ai --skill figma-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps design teams translate inventories of screens and components into a structured Figma handoff specification in Markdown, ensuring clear organization and traceability for handoff.

Core Features & Use Cases

  • Generates a six-section Figma spec including File structure, Component page layout, Use case page layout, Annotation conventions, Handoff checklist, and Handoff package.
  • Enforces traceability by aligning screen frames to use case steps and extensions and providing a consistent annotation scheme.
  • Produces a designer-ready Markdown document that can be executed in Figma workflows without creating a Figma file itself.

Quick Start

Invoke the figma-spec skill after supplying a screen-inventory and a component-inventory to generate the Markdown specification.

Frequently Asked Questions about figma-spec

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

FAQPage Schema
How do I generate a Figma handoff spec from a screen and component inventory?

To generate a Figma handoff spec, supply your screen-inventory and component-inventory to produce a structured Markdown specification covering file structure, component pages, use case pages, annotations, and a handoff checklist.

What is a Figma handoff specification and what sections should it include?

A Figma handoff specification organizes design files for developer handoff. A complete spec includes six sections: File structure, Component pages, Use case pages, Annotations, Handoff checklist, and Handoff package.

Do I need a screen-inventory and component-inventory before creating design handoff documentation?

Yes, both a screen-inventory and a component-inventory must exist before generating handoff documentation. These inventories provide the foundational screen frames and component data required to enforce traceability and structure.

Can I generate a complete Figma file directly from a design inventory?

No, this process produces a designer-ready Markdown specification document rather than a direct Figma file. The structured Markdown output can then be executed in Figma workflows to guide file organization and annotations.

What's the best way to structure Figma component pages for complex use cases across multiple screens?

The best way to structure component pages is by aligning screen frames to use case steps and extensions within the Markdown spec. This enforces consistent annotation schemes and traceability across complex multi-screen workflows.

Why does my design handoff lack traceability between screen frames and use case steps?

Handoff lacks traceability when screen frames are not aligned to use case steps and extensions. Generating a structured handoff spec enforces this alignment and provides a consistent annotation scheme for complex use cases.