design-intel

Extract structured design intent from Figma frames into Markdown documents.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/razorpay/ai-playbook --skill design-intel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-intel
Source: https://github.com/razorpay/ai-playbook/tree/main/skills/design-intel
Command: npx skills add https://github.com/razorpay/ai-playbook --skill design-intel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the uncertainty in translating a Figma design into production code by producing structured, build-ready design intent instead of leaving the downstream compiler to guess the designer’s intent.

Core Features & Use Cases

  • Figma-to-intent extraction: Reads a Figma frame via the Figma MCP and outputs a structured design-intel Markdown document.
  • Blade-aligned mapping: Identifies UI components and records the closest Blade primitive (or flags gaps when no exact match exists).
  • Workflow-critical structure: Captures layout shape, interaction states (and missing states), visible variants, accessibility considerations, and open questions for blockers.
  • Multi-frame flow mode: Generates a single combined intent document for a sequence of frames representing a component/flow across states (empty/loading/success/error).

Quick Start

Use the design-intel skill to extract intent from a Figma frame by asking for “Give me design intel for <Figma frame URL or ID>”.

Frequently Asked Questions about design-intel

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

FAQPage Schema
How do I extract structured design intent from a Figma frame?

You can extract design intent from a Figma frame by reading its structure and outputting a Markdown document. This process captures layout primitives, interaction states, and accessibility considerations to generate build-ready UI code.

What is the best way to map Figma components to Blade primitives?

Mapping Figma components to Blade primitives involves analyzing the frame structure and identifying the closest matching primitive. If no exact match exists, the system flags gaps to ensure the design intent is accurately captured for production code generation.

Can I capture interaction states and accessibility considerations from Figma to code?

Yes, you can capture interaction states and accessibility considerations during design intent extraction. The process records visible variants, flags missing states, and documents accessibility requirements to ensure the UI code is shippable.

Does the design intent extraction process support multi-frame flows?

Yes, design intent extraction supports multi-frame flows. It can generate a single combined intent document for a sequence of Figma frames representing a component or flow across various states like empty, loading, success, and error.

Why do I need a Markdown document for design-to-code workflows?

You need a Markdown document for design-to-code workflows to provide a stable, structured representation of design intent. This prevents downstream production compilers from guessing the designer's intent regarding layout and component variants.

What are the limitations when extracting design intent from Figma?

A limitation when extracting design intent is that the system flags gaps when no exact Blade primitive match exists. Additionally, the extraction relies on reading the frame structure via Figma MCP, which may require clear frame organization to capture all open questions and blockers.