analyze-design

Generate design graph nodes linking functional scenarios to UI components.

2|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill analyze-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-design
Source: https://github.com/accionlabs/breezeai-claude-plugin/tree/main/skills/analyze-design
Command: npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill analyze-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often have functional requirements in Jira, Figma, or plain text but lack a corresponding design graph that ties UI elements to functional scenarios, leading to fragmented documentation and redundant effort.

Core Features & Use Cases

  • Multi‑source input: Accepts Jira tickets, Figma URLs, scenario references, or free‑form descriptions.
  • Automated UI mapping: Generates UserJourney, Flow, Page, and Component nodes, reusing existing design artifacts when possible.
  • Optional repository enrichment: When a UI codebase is provided, it discovers routes to split scenarios into multiple flows and pages.

Quick Start

Ask the AI to analyze a design by providing a Jira ticket, a Figma link, or a brief description of the requirement.

Frequently Asked Questions about analyze-design

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

FAQPage Schema
How do I generate a design graph from Jira tickets or Figma wireframes?

Generating a design graph from Jira tickets or Figma wireframes requires providing the source link to automatically produce UserJourney, Flow, Page, and Component nodes linking functional scenarios to UI elements.

What is design graph mapping for functional requirements?

Design graph mapping for functional requirements links scenarios to UI components by generating structured nodes like UserJourney, Flow, Page, and Component, preventing fragmented documentation and redundant effort across teams.

Do I need a Breeze MCP project UUID to create UI components from requirements?

Yes, a Breeze MCP project UUID is required to resolve routes and create reusable design artifacts. Providing an optional UI repository path can further enrich the generated design graph flows.

Can I use plain text descriptions to build a Figma design flow?

Yes, plain text descriptions are accepted alongside Figma URLs and Jira tickets to build design graph nodes, allowing you to map functional scenarios to UI components without requiring formal documentation.

How does providing a UI codebase repository improve design graph generation?

Providing a UI codebase repository enriches design graph generation by discovering routes, which allows the system to automatically split functional scenarios into multiple distinct flows and pages for accurate mapping.