1
Setup & Connection Verification
8 prompts
1
Verify MCP Connection
Run this first after setting up MCP to confirm Claude can communicate with Figma's API.
Chat
CLI
Automation
Prompt #1 — Chat
List all Figma MCP tools you have access to. For each tool, show: 1. Tool name 2. What it does (one sentence) 3. Parameters it accepts 4. Required vs optional parameters Confirm whether the Figma MCP server is connected and responding.
VARIATIONS
SHORTERWhat Figma tools do you have? List them all.
DIAGNOSTICCheck if Figma MCP is connected. If yes, list every available tool with parameters.
VERBOSEI just set up the Figma MCP server. Before I start working, can you verify the connection is active and show me every tool available, including their full parameter schemas?
Expected Output
A numbered list of all available MCP tools with parameter details and a connection status confirmation.
Example Output
Figma MCP Server — Connected Available Tools (6): 1. get_file Retrieves the full node tree of a Figma file. Parameters: fileKey (required), depth (optional) 2. get_design_context Returns design properties and screenshots. Parameters: nodeId (required), fileKey (required) Connection status: Active ✓
2
Test File Access
Verify you can read from a specific Figma file using the MCP connection.
Chat
CLI
Automation
Prompt #2 — Chat
I want to test file access to confirm the MCP setup works. Please: 1. Attempt to read a Figma file using the file key [FILE_KEY] 2. Show me the basic metadata (name, pages, component count) 3. Report any permissions issues 4. Confirm successful read access If access fails, provide the exact error message.
VARIATIONS
QUICKCan you access this Figma file? [FILE_KEY] Just confirm yes/no and show the file name.
DETAILEDTest read access to [FILE_KEY]. Show: file name, number of pages, total nodes, any errors encountered.
DEBUGTry to read [FILE_KEY]. If it succeeds, show metadata. If it fails, give me the full error trace and tell me what permission is missing.
Expected Output
File metadata (name, pages, node count) confirming successful access, or specific error message identifying the issue.
Example Output
File Access Test Results: File Key: abc123xyz File Name: Design System v2.4 Pages: 5 (Components, Colors, Typography, Patterns, Archive) Total Nodes: 2847 Access Level: Editor Status: ✓ Successfully read Response Time: 287ms
3
Diagnose Connection Failure
When MCP connection fails, debug systematically to identify the root cause.
Chat
CLI
Automation
Prompt #3 — Chat
The Figma MCP connection is failing. Please help me diagnose: 1. Is the MCP server running? 2. Can the server reach Figma's API? 3. Are credentials/tokens valid? 4. Are there firewall/proxy issues? 5. Check server logs for errors 6. Suggest fixes in order of likelihood Provide a step-by-step troubleshooting guide.
VARIATIONS
QUICKMCP not working. What's wrong? Give me the top 3 things to check.
TECHNICALDiagnose Figma MCP connection failure. Check: server status, API connectivity, auth tokens, network issues. Provide specific commands to test each.
DETAILEDMCP setup failed. Walk me through every diagnostic step, what each means, and how to fix it. Include commands, log locations, and expected outputs.
Expected Output
Numbered troubleshooting steps with diagnostic commands and expected outcomes, prioritized by likelihood.
Example Output
Figma MCP Diagnostic Guide: 1. Check Server Status Command: npm status / systemctl status figma-mcp Expected: Running 2. Verify Auth Token Command: echo $FIGMA_TOKEN | head -c 10 Expected: Token starts with 'fv' or similar 3. Test API Connection Command: curl https://api.figma.com/v1/me -H "X-Figma-Token: $FIGMA_TOKEN" Expected: 200 OK + user data Most likely issue: Invalid/expired token (fix: refresh in .env)
4
Validate Token Permissions
Ensure your Figma token has necessary scopes for all planned operations.
Chat
CLI
Automation
Prompt #4 — Chat
Check what permissions my Figma token has: 1. List all token scopes 2. Identify which files/teams Claude can access 3. Check what operations are permitted (read/write/admin) 4. Flag any scope limitations that might block workflows 5. Recommend minimum required scopes for design systems work Clearly show which operations Claude can and cannot perform.
VARIATIONS
MINIMALWhat can my Figma token do? What files can I access?
DETAILEDAudit my Figma token permissions. Show scopes, accessible files, allowed operations, and any limitations.
SECURITYValidate my token for security. Show: current scopes, over-privileged scopes, recommended minimum scopes, any security concerns.
Expected Output
List of token scopes, accessible files/teams, permitted operations, and any permission gaps affecting workflow.
Example Output
Token Permissions Audit: Token Scopes: ✓ files:read ✓ file_exports:read ✗ files:write (NOT GRANTED) ✗ comments:write (NOT GRANTED) Accessible Files: 23 Accessible Teams: 2 (Design, Product) Permitted Operations: ✓ Read design files ✓ Export assets ✓ Extract metadata ✗ Create/edit components ✗ Manage styles ✗ Add comments Recommendation: Add 'files:write' scope for token sync
5
Check Server Version
Verify MCP server version and check for available updates.
Chat
CLI
Automation
Prompt #5 — Chat
What version of the Figma MCP server am I running? 1. Report current version 2. Check for latest available version 3. Show changelog for new versions 4. Recommend if update is needed 5. Provide update instructions if applicable Include compatibility notes with Claude versions.
VARIATIONS
QUICKWhat version of Figma MCP do I have? Is there a newer one?
DETAILEDCheck MCP version, latest version, changelog, and whether I should update. Include any breaking changes.
FULLFull version audit: current version, latest version, detailed changelog, compatibility with Claude, update risk assessment, and instructions.
Expected Output
Current version, latest version, brief changelog, and update recommendation with compatibility notes.
Example Output
Figma MCP Version Check: Current Version: 2.1.3 Latest Available: 2.3.1 Update Available: YES Changelog (2.1.3 → 2.3.1): - 2.2.0: Added component variant queries - 2.3.0: Improved performance, new design tokens API - 2.3.1: Bug fixes for token export Compatibility: Claude 3.5+ required (you have 3.8 ✓) Risk: Low (minor version bump) Update Command: npm update figma-mcp@latest
6
List Available Figma Files
Get a quick overview of all Figma files you have access to.
Chat
CLI
Automation
Prompt #6 — Chat
Show me all Figma files Claude has access to: 1. List file name, key, and owner 2. Show last modified date 3. Indicate access level (view/edit/owner) 4. Count total files per team 5. Highlight recently updated files 6. Show file type if identifiable (design system, prototype, etc.) Format as a sortable table or organized list.
VARIATIONS
QUICKList all my Figma files with their keys.
ORGANIZEDShow all Figma files by team, with name, key, owner, and last modified date.
DETAILEDComplete inventory of Figma files Claude can access. Show: file name, key, team, owner, access level, last modified, file size if available.
Expected Output
Organized list or table of all accessible files with key metadata (name, key, owner, access level, last modified).
Example Output
Available Figma Files (8 total): DESIGN TEAM (6 files): 1. Design System v2.4 | abc123xyz | Owner | Updated: 2h ago 2. Mobile Components | def456uv | Edit | Updated: 1d ago 3. Marketing Site | ghi789wxy | View | Updated: 3d ago PRODUCT TEAM (2 files): 4. App Prototype | jkl012zab | Edit | Updated: 30min ago 5. Archived Designs 2024 | mno345cde | View | Updated: 2w ago
7
Test Write Permissions
Verify you can push changes back to Figma (create/edit components, tokens, styles).
Chat
CLI
Automation
Prompt #7 — Chat
Test my write permissions to Figma: 1. Attempt a safe test write (e.g., create temporary test component) 2. Verify the write succeeded 3. Report permission level (edit/owner/none) 4. Test token push capability 5. Test style creation capability 6. Clean up test data Provide clear pass/fail status for each operation type.
VARIATIONS
MINIMALCan I write to Figma? Do a quick test.
DETAILEDTest write access. Try: creating a test component, updating a style, pushing tokens. Report success/failure for each.
COMPREHENSIVEFull write permission audit. Test: component creation, style updates, token pushes, layer modifications. Report each capability and clean up test artifacts.
Expected Output
Pass/fail status for each write operation type (component creation, style updates, token pushes) with clear indicators of what operations are allowed.
Example Output
Write Permission Test Results: Test Component Creation: ✓ PASS Created: Test_Widget_Temporary Status: Verified in file Cleanup: Deleted Test Style Update: ✓ PASS Updated color style: Colors/Primary Status: Verified Test Token Push: ✓ PASS Pushed 5 token variables Status: Verified in Variables panel Overall Write Access: ✓ ENABLED Permission Level: Editor Authorized Operations: Create, Edit, Delete
8
Health Check Dashboard
Get a comprehensive system status report of the entire Figma MCP setup.
Chat
CLI
Automation
Prompt #8 — Chat
Generate a complete health check report of my Figma MCP setup: 1. MCP server status (running/stopped) 2. API connectivity (latency, errors) 3. Token validity and scope coverage 4. File access status across all accessible files 5. Read/write capability verification 6. Performance metrics (response times) 7. Any warnings or issues 8. Overall system health score Format as a clear status dashboard.
VARIATIONS
QUICKIs everything working with my Figma MCP setup? Give me a quick status.
DETAILEDFull health check: server status, API latency, token validity, file access, read/write capability. Flag any issues.
EXECUTIVEGenerate a professional health dashboard for my Figma MCP setup. Include status, metrics, warnings, and recommendations in dashboard format.
Expected Output
Structured health report with status of each component (server, API, token, files, permissions), metrics, and overall health score.
Example Output
Figma MCP Health Dashboard [████████████████████] 92% Overall Server Status: ✓ RUNNING Uptime: 7d 3h 21min Memory: 342MB / 512MB (67%) API Connectivity: ✓ HEALTHY Latency: 234ms avg Errors (24h): 0 Authentication: ✓ VALID Token Expires: 89 days Scopes: 4/6 optimal File Access: ✓ OPERATIONAL Files Accessible: 8/8 Avg Read Time: 287ms Write Capability: ✓ ENABLED Test Write: PASS Warnings: None Recommendations: Consider updating to v2.3.1 (minor improvement) Last Check: 2min ago
2
Reading & Exploring Figma Files
10 prompts
9
Full File Overview
Get a bird's-eye view of everything in a Figma file's structure.
Chat
CLI
Automation
Prompt #9 — Chat
Give me a complete overview of the Figma file [FILE_KEY]: 1. File name and description 2. List all pages with page counts 3. Count total components, styles, and variants 4. List all teams/projects 5. Show document permissions 6. Identify design tokens (if any) 7. Summary of asset types (icons, illustrations, etc.) 8. Nested structure: how many levels deep Organize as a hierarchical summary.
VARIATIONS
QUICKOverview of [FILE_KEY]: name, pages, components, styles. Just the basics.
STRUCTUREDComplete file structure breakdown: pages, components, styles, tokens, permissions, asset types.
DETAILEDFull architectural overview of [FILE_KEY]. Show: all pages with details, all components with variant counts, all styles, tokens, permissions, nesting depth, asset inventory.
Expected Output
Hierarchical summary showing file name, pages, component/style/token counts, and overall file structure with nesting levels.
Example Output
File Overview: Design System v2.4 Pages (5 total): ├─ Components (892 nodes) │ ├─ Buttons (28) │ ├─ Forms (45) │ └─ Navigation (18) ├─ Colors (156 nodes) ├─ Typography (89 nodes) ├─ Patterns (234 nodes) └─ Archive (archived) Components: 347 Variants: 892 Styles: 156 (Colors) Tokens: 84 Nesting Depth: 5 levels Permissions: Editor (Design Team) Size: ~2.3MB Last Modified: 2h ago
10
Deep Dive into a Specific Frame
Extract complete details about a single frame's internal structure and all child elements.
Chat
CLI
Automation
Prompt #10 — Chat
Show me everything inside the frame '[FRAME_NAME]' in [FILE_KEY]: 1. Frame dimensions and position 2. All direct children (list by name and type) 3. Fill colors and strokes 4. Layout properties (flex, auto-layout settings) 5. Text content in all text nodes 6. Image fills (with descriptions) 7. Component instances (with overrides) 8. Constraints and sizing behavior Show the complete DOM-like tree.
VARIATIONS
QUICKWhat's in '[FRAME_NAME]'? List all the elements inside it.
DETAILEDComplete breakdown of '[FRAME_NAME]': dimensions, children, colors, layout, text, images, components, constraints.
TECHNICALFull technical audit of '[FRAME_NAME]' frame. Show: exact dimensions, all child nodes as tree, colors/strokes, auto-layout rules, all text content, image sources, component instances with overrides, all constraints.
Expected Output
Tree-like listing of all frame contents with properties (dimensions, colors, text, components, constraints).
Example Output
Frame: 'Button - Primary' Details Dimensions: 160 × 48 px Position: X=0, Y=0 Auto Layout: Flex, horizontal, gap=8 Fill: Color/Primary (value: #2563EB) Children (3): ├─ Icon [Component] │ └─ Instance: icons/check-solid │ Override: Size=16×16 ├─ Text: "Click Me" │ └─ Font: Inter, 14px, weight 600 │ └─ Color: Color/White (#FFFFFF) └─ Hover State [Component] └─ Instance: Overlay/Hover Constraints: Horizontal center, fixed height Export: button-primary.svg
11
List All Text Content
Extract all text from a Figma file for review, translation, or content audit.
Chat
CLI
Automation
Prompt #11 — Chat
Extract all text content from [FILE_KEY]: 1. Find every text node in the file 2. Show page and frame location for each 3. Group by content type (labels, headings, body copy, etc.) 4. Include font size and weight 5. Highlight any placeholder or dummy text 6. Count total text nodes 7. Flag any formatting issues (very long text, special characters) 8. Provide in both list and CSV formats Useful for content audits and translation prep.
VARIATIONS
QUICKList all text in [FILE_KEY].
ORGANIZEDAll text content from [FILE_KEY], grouped by page/frame with font info.
DETAILEDComplete text inventory from [FILE_KEY]. Show: all text nodes, locations (page/frame), grouping by content type, font properties, flags for issues (dummy text, special chars, length). Provide CSV export.
Expected Output
Comprehensive list of all text nodes organized by location and type, with font properties and counts.
Example Output
Text Content Inventory: [FILE_KEY] Total Text Nodes: 247 HEADINGS (28): ✓ Page: Components > Buttons "Primary Button" | Inter 18px bold | Color: Primary "Secondary Button" | Inter 18px bold BODY COPY (89): ✓ Page: Patterns > Card "Lorem ipsum dolor sit amet..." | Inter 14px regular "Click here to learn more" | Inter 14px, underline LABELS (56): ✓ "First Name" | 12px, color: Secondary ✓ "Email Address" | 12px PLACEHOLDER TEXT (18) ⚠️: ✓ "[NEEDS COPY]" in 3 locations ✓ "TODO" in 2 locations DATA: CSV Export Available
12
Find All Images & Assets
Locate all images, icons, and asset exports in a Figma file.
Chat
CLI
Automation
Prompt #12 — Chat
Find all images and assets in [FILE_KEY]: 1. List every image fill (with dimensions) 2. Show image source URL or embedded data 3. Find all icon components 4. List all export settings 5. Identify unused/orphaned images 6. Calculate total asset footprint 7. Group by asset type (icons, illustrations, photos) 8. Flag any broken image references Provide organized inventory with download recommendations.
VARIATIONS
QUICKWhat images and icons are in [FILE_KEY]?
DETAILEDAll images and assets in [FILE_KEY]: image fills, icons, exports, sources, dimensions, asset footprint.
COMPLETEComprehensive asset audit of [FILE_KEY]. Show: all image fills with sources/dimensions, all icon components, all export settings, unused assets, total footprint, asset types organized, broken references flagged. Include download recommendations.
Expected Output
Organized inventory of images/icons with dimensions, sources, locations, and export settings.
Example Output
Asset Inventory: [FILE_KEY] IMAGE FILLS (12): ✓ Page: Patterns > Hero Source: unsplash.com/photos/abc123 Dimensions: 1200×600 Embedded: Yes Size: ~340KB ICON COMPONENTS (34): ✓ Icons/Check (16×16, 24×24, 32×32 variants) ✓ Icons/Arrow (12 directions) ✓ Icons/Social (8 variants) EXPORT SETTINGS (23): ✓ Button Primary → button-primary.svg ✓ Icons/Check → icons/check.svg ✓ Hero Image → hero.png UNUSED ASSETS (2) ⚠️: ✓ Old_Brand_Logo (safe to delete) ✓ Placeholder_Image_v1 Total Asset Footprint: ~4.2MB Recommendation: Export unused assets, optimize images
13
Page-by-Page Breakdown
Get a summary of each page in a Figma file to understand file organization.
Chat
CLI
Automation
Prompt #13 — Chat
Break down each page in [FILE_KEY]: 1. For each page, show name and node count 2. List major frames/sections on each page 3. Identify page purpose (components, docs, specs, archive, etc.) 4. Show recent changes on each page 5. Flag pages that are empty or archived 6. Suggest organizational improvements 7. Show page permissions if different Provide summary of file organization health.
VARIATIONS
QUICKList all pages in [FILE_KEY] with their purposes.
DETAILEDFor each page in [FILE_KEY]: name, node count, major frames, purpose, recent changes, status.
ANALYSISComplete page-by-page analysis of [FILE_KEY]. Show: page name/purpose, node counts, major sections, recent changes, status (active/archived/empty), permissions, and organizational recommendations.
Expected Output
Summary of each page showing name, purpose, node count, major sections, and organizational status.
Example Output
Page Breakdown: [FILE_KEY] Page 1: COMPONENTS (892 nodes) ✓ ACTIVE ├─ Purpose: Published component library ├─ Sections: Buttons, Forms, Navigation, Cards ├─ Last Updated: 2h ago └─ Status: Well-organized Page 2: COLORS (156 nodes) ✓ ACTIVE ├─ Purpose: Color palette & tokens ├─ Sections: Brand Colors, Semantic Colors, Gradients ├─ Last Updated: 1w ago └─ Status: Good Page 3: TYPOGRAPHY (89 nodes) ✓ ACTIVE ├─ Purpose: Type scale & styles ├─ Last Updated: 3w ago Page 4: PATTERNS (234 nodes) ⚠️ NEEDS REVIEW ├─ Purpose: Common UI patterns ├─ Status: Last updated 2 months ago Page 5: ARCHIVE (289 nodes) 🗂️ ARCHIVED ├─ Purpose: Old designs (safe to delete) ├─ Recommendation: Move to separate file Overall Health: Good organization, consider archiving page 5
14
Inspect a Specific Component
Get detailed technical specs of a single component for code generation or documentation.
Chat
CLI
Automation
Prompt #14 — Chat
Inspect the component '[COMPONENT_NAME]' in [FILE_KEY]: 1. Show component metadata (name, size, location) 2. List all properties and variants 3. Show variant matrix (all combinations) 4. Document all component props 5. Extract all colors and typography 6. List nested components (children) 7. Show constraints and layout behavior 8. Provide component code-gen suggestions Format as technical component spec.
VARIATIONS
QUICKWhat's in the '[COMPONENT_NAME]' component? Show variants and props.
TECHNICALFull technical spec of '[COMPONENT_NAME]': metadata, variants, props, colors, typography, nesting, constraints.
DEV-READYComplete technical component specification for '[COMPONENT_NAME]'. Show: metadata, variant matrix, all props with types, colors/typography, nested components, constraints, and ready-to-code documentation.
Expected Output
Detailed component specification including metadata, variant matrix, prop definitions, and styling information.
Example Output
Component Spec: Button Metadata: - Name: Buttons/Primary - Dimensions: 160×48 (variable) - Location: Components page, frame "Buttons" - Published: Yes Variants (12 total): - Size: Small (32h), Medium (48h), Large (56h) - State: Default, Hover, Active, Disabled - Icon: With Icon, Without Icon Variant Matrix: [Small, Default, No Icon] ✓ Exists [Small, Hover, No Icon] ✓ Exists [Medium, Default, With Icon] ✓ Exists ... (12 total) Component Props: 1. label: string = "Click me" 2. size: enum(small, medium, large) = medium 3. state: enum(default, hover, active, disabled) = default 4. icon: boolean = false Colors: - Background: Color/Primary (#2563EB) - Text: Color/White (#FFFFFF) - Border: None Typography: - Font: Inter - Size: 14px (medium) - Weight: 600 (semibold) Nested Components: - Icons/Check (optional) Constraints: - Horizontal: Center - Vertical: Top Suggestion: Ready for React component generation
15
List All Colors Used
Extract every unique color value from a Figma file for a color palette audit.
Chat
CLI
Automation
Prompt #15 — Chat
Extract all colors from [FILE_KEY]: 1. Find every unique color value (HEX, RGB, HSL) 2. Show where each color is used (element names, counts) 3. Group by color similarity/family 4. Identify and flag color issues: - Duplicates (same color, different hex values) - Unused colors - Accessibility issues (low contrast) - Off-brand colors 5. Match colors to named styles if they exist 6. Provide color palette export (Figma JSON, CSS variables, Tailwind) Provide comprehensive color audit.
VARIATIONS
QUICKWhat colors are in [FILE_KEY]? List them all.
DETAILEDAll colors in [FILE_KEY]: hex values, usage, grouping, duplicates, unused colors. Export as CSS variables.
AUDITComplete color audit of [FILE_KEY]. Show: all unique colors with usage counts, grouping by family, duplicates flagged, unused colors, contrast issues, off-brand colors, match to named styles, export in multiple formats (CSS, JSON, Tailwind).
Expected Output
Organized color inventory with grouping, usage counts, duplicates flagged, and export options.
Example Output
Color Audit: [FILE_KEY] Unique Colors: 34 total PRIMARY COLORS: ✓ #2563EB (Brand Primary) Used in: 28 elements Style: Colors/Primary ✓ #DC2626 (Brand Error) Used in: 12 elements Style: Colors/Error DUPLICATES FOUND (2) ⚠️: ✗ #1E40AF (used 3x) ≈ #2563EB (should consolidate) ✗ #F87171 (used 2x) ≈ #DC2626 (should consolidate) UNUSED COLORS (3) 🗑️: - #9CA3AF (gray, no usage) - #A78BFA (purple, old brand) - #FEF3C7 (yellow, deprecated) NEUTRAL PALETTE: #000000 (black, headings, 45x) #FFFFFF (white, backgrounds, 89x) #6B7280 (gray-500, body text, 23x) #F3F4F6 (gray-100, backgrounds, 34x) CONTRAST ISSUES (1) ⚠️: - #A0AEC0 on #FFFFFF = 3.2:1 (below WCAG AA) Export Formats: ✓ CSS Variables ✓ Tailwind Config ✓ JSON Tokens
16
Find Hidden or Locked Layers
Audit the visibility and lock status of all layers to identify buried or protected content.
Chat
CLI
Automation
Prompt #16 — Chat
Audit hidden and locked layers in [FILE_KEY]: 1. Find all hidden layers (visibility off) 2. Find all locked layers 3. Show what's hidden/locked and why (maintenance layer? old version?) 4. Identify stranded/orphaned hidden content 5. Count hidden/locked elements 6. Recommend which can be safely deleted 7. Suggest organization improvements 8. Provide remediation checklist Show complete visibility and lock status report.
VARIATIONS
QUICKAre there hidden or locked layers in [FILE_KEY]? Show me.
DETAILEDAll hidden/locked layers in [FILE_KEY]: what's hidden, what's locked, where, deletion recommendations.
AUDITComplete visibility and lock audit of [FILE_KEY]. Show: all hidden layers with reasons, all locked layers, orphaned content, deletion safety assessment, organization recommendations, cleanup checklist.
Expected Output
Inventory of hidden and locked layers with recommendations for cleanup and organization.
Example Output
Layer Visibility & Lock Audit: [FILE_KEY] HIDDEN LAYERS (8 total): ✓ Page: Components > Buttons "OLD Button Styles (v1)" | 5 child layers Recommendation: Safe to delete (superseded) ✓ Page: Components > Forms "Unused input variants" | 3 child layers Recommendation: Safe to delete ✓ Page: Archive "2023 designs" | 43 child layers Recommendation: Move to separate archive file LOCKED LAYERS (12 total): ✓ Page: Components "Master Components" | 45 items Reason: Prevent accidental edits Status: Appropriate ✓ Page: Colors "Color Grid (reference)" | locked Reason: Documentation reference Status: Appropriate STRANDED CONTENT (2) ⚠️: ✓ "Hidden old logo" | No reference | Recommend: Delete ✓ "temp sketch" | Hidden for 3 months | Recommend: Delete RECOMMENDATIONS: 1. Delete 7 truly unused hidden layers (safe) 2. Archive old 2023 designs to separate file 3. Audit locked layers quarterly 4. Consider new organization system for versions Cleanup Checklist: ☐ Review ☐ Backup ☐ Execute
17
Get File Version History
Review version history to understand design evolution and find specific changes.
Chat
CLI
Automation
Prompt #17 — Chat
Show version history for [FILE_KEY]: 1. List all versions with dates 2. Show who made each change and when 3. Provide brief descriptions of what changed 4. Identify major updates vs. minor tweaks 5. Show current vs. previous versions 6. Highlight breaking changes 7. Suggest rollback points if needed Format as a timeline view.
VARIATIONS
QUICKShow recent version history for [FILE_KEY].
DETAILEDComplete version history for [FILE_KEY]: versions, dates, authors, change descriptions, major vs. minor updates.
ANALYSISFull version history and timeline for [FILE_KEY]. Show: all versions with dates/authors, change descriptions, impact assessment (breaking changes, major updates), rollback options, historical analysis.
Expected Output
Timeline of file versions showing dates, authors, change descriptions, and impact.
Example Output
Version History: [FILE_KEY] Version 2.4.0 | TODAY at 2:15 PM | Sarah Chen (Designer) - Added 3 new button variants - Updated color tokens for better contrast - Status: Current Version 2.3.2 | MARCH 13 | Mike Johnson (Designer) - Bug fixes: corrected font sizes in typography page - Minor UI polish - Rollback available Version 2.3.1 | MARCH 10 | Sarah Chen (Designer) - Major: Redesigned form components - Breaking change: Old form variants deprecated - ⚠️ Note: Affects implementations Version 2.3.0 | MARCH 5 | Design Team - Added 8 new color tokens - Updated spacing system - Added documentation page Version 2.2.0 | FEBRUARY 28 | Sarah Chen - Major refactor: Reorganized component structure - Added variant system - ⚠️ Breaking change for developers Version 2.1.0 | FEBRUARY 14 | Initial DS v2 launch Suggested Rollback Points: - To fix form issues: v2.3.0 (pre-redesign) - To restore old colors: v2.2.0
18
Search by Node Name
Find specific elements in a large file by searching for node names or patterns.
Chat
CLI
Automation
Prompt #18 — Chat
Search for nodes in [FILE_KEY] matching the pattern '[SEARCH_PATTERN]': 1. Find all nodes whose names match the pattern 2. Support regex patterns if needed 3. Show full path to each match (page > frame > component) 4. Display node type (component, frame, group, text, shape) 5. Show node dimensions and position 6. List all matches with relevance ranking 7. Provide quick navigation links Use case: Find all 'Button' components or all nodes starting with 'Icon_'.
VARIATIONS
QUICKFind all nodes named '[SEARCH_PATTERN]' in [FILE_KEY].
DETAILEDSearch [FILE_KEY] for '[SEARCH_PATTERN]'. Show: all matches, full paths, types, dimensions, count.
ADVANCEDSearch [FILE_KEY] for nodes matching '[SEARCH_PATTERN]' (support regex, wildcards). Show: all matches with full paths, node types, properties, dimensions, position, match count, navigation.
Expected Output
List of all nodes matching search pattern with full paths and basic properties.
Example Output
Search Results: [SEARCH_PATTERN] in [FILE_KEY] Matches Found: 14 1. ✓ Button - Primary (Component) Path: Components > Buttons > Button - Primary Type: Component Instances: 28 2. ✓ Button - Secondary (Component) Path: Components > Buttons > Button - Secondary Type: Component Instances: 15 3. ✓ Button (Group) Path: Patterns > Card > Button Type: Group Dimensions: 160×48 Position: X=100, Y=200 4. ✓ Button Hover State (Component) Path: Components > Buttons > States > Button Hover State Type: Component ... (10 more matches) Navigation: [Go to Button - Primary] [Go to Button - Secondary] [Go to all Buttons]
3
Design Tokens Extraction
12 prompts
19
Extract Full Color Palette
Export all colors from Figma as design tokens for use in code.
Chat
CLI
Automation
Prompt #19 — Chat
Extract complete color palette from [FILE_KEY] as design tokens:
1. Find all unique colors in the file
2. Group colors by semantic meaning (primary, secondary, neutral, etc.)
3. Create token names following naming convention (color-{purpose}-{state})
4. Include color values in multiple formats (HEX, RGB, HSL)
5. Add WCAG contrast ratings for readability
6. Generate export in: JSON, CSS, JavaScript, SCSS
7. Include color documentation
8. Flag deprecated colors
Provide production-ready token definitions.
VARIATIONS
QUICKExport colors from [FILE_KEY] as tokens in JSON format.
DETAILEDColor palette as tokens: semantic grouping, multiple formats, contrast ratings, exports (JSON/CSS/JS/SCSS).
FULLComplete color token extraction from [FILE_KEY]. Include: semantic grouping, token naming (following conventions), multiple formats (HEX/RGB/HSL), contrast ratings, exports, documentation, deprecated flags, production-ready.
Expected Output
Color tokens organized by category with multiple format exports and contrast ratings.
Example Output
Color Token Palette: [FILE_KEY]
PRIMARY COLORS:
{
"color-primary-50": {"value": "#EFF6FF", "rgb": "rgb(239, 246, 255)", "contrast": "N/A"},
"color-primary-500": {"value": "#2563EB", "rgb": "rgb(37, 99, 235)", "contrast": "4.8:1 ✓"},
"color-primary-900": {"value": "#1E3A8A", "rgb": "rgb(30, 58, 138)", "contrast": "7.2:1 ✓"}
}
NEUTRAL COLORS:
{
"color-neutral-0": {"value": "#FFFFFF"},
"color-neutral-50": {"value": "#F9FAFB"},
"color-neutral-900": {"value": "#111827"}
}
EXPORTS:
✓ colors.json (JSON)
✓ colors.css (CSS variables)
✓ colors.js (ES6)
✓ colors.scss (SCSS maps)
Contrast Summary:
✓ All semantic colors meet WCAG AA
✓ Primary on white: 4.8:1
✓ Neutral-900 on white: 21:1
Deprecated Colors (3):
⚠️ old-brand-blue (#3B5998) — Replace with primary-500
⚠️ old-brand-red (#E64646) — Replace with error-50020
Generate Color Token JSON
Create a JSON file of color tokens for direct use in design systems.
Chat
CLI
Automation
Prompt #20 — Chat
Generate color tokens JSON from [FILE_KEY]: 1. Extract all colors as token definitions 2. Use semantic naming (primary, secondary, success, warning, error, neutral) 3. Include color states (default, hover, active, disabled) 4. Create color scales (50-900 with 50-step increments) 5. Add metadata: usage, description, WCAG rating 6. Format as W3C Design Tokens Community Group standard 7. Include comments with usage examples 8. Generate companion CSS custom properties 9. Ready for: Figma, Storybook, CSS, Tailwind, design tools Include both JSON and CSS variable versions.
VARIATIONS
QUICKGenerate color tokens JSON from [FILE_KEY]. Just the basic structure.
DETAILEDColor tokens JSON with semantic naming, color scales, metadata, WCAG ratings, CSS variables.
PRODUCTIONProduction-ready color token JSON from [FILE_KEY]. Include: W3C standard format, semantic naming with states, color scales (50-900), metadata/usage/descriptions, WCAG ratings, CSS variables, Figma variables, usage examples, documentation comments.
Expected Output
JSON file with color tokens in W3C standard format with metadata, plus CSS custom properties.
Example Output
{
"color": {
"primary": {
"50": {
"value": "#EFF6FF",
"description": "Lightest primary color for backgrounds",
"usage": "Hover states, light backgrounds",
"wcag": "N/A"
},
"500": {
"value": "#2563EB",
"description": "Primary brand color",
"usage": "Buttons, links, active states",
"wcag": "4.8:1 (white background)"
},
"900": {
"value": "#1E3A8A",
"description": "Darkest primary for high contrast",
"usage": "Text on light backgrounds, focus states",
"wcag": "7.2:1 (white background)"
}
},
"neutral": {
"0": {"value": "#FFFFFF"},
"50": {"value": "#F9FAFB"},
"900": {"value": "#111827"}
}
}
}
:root {
--color-primary-50: #EFF6FF;
--color-primary-500: #2563EB;
--color-primary-900: #1E3A8A;
--color-neutral-0: #FFFFFF;
}21
Extract Typography Scale
Export all typography (fonts, sizes, weights, line heights) as tokens.
Chat
CLI
Automation
Prompt #21 — Chat
Extract typography system from [FILE_KEY]:
1. Find all unique font families
2. Identify all font sizes used
3. Collect all font weights
4. Extract line heights and letter spacing
5. Group typography by semantic purpose (display, heading, body, caption)
6. Create token names (typography-{size}-{weight})
7. Include line height and spacing ratios
8. Generate typography scale (8px, 10px, 12px, 14px, 16px, 18px, 20px, 24px, 28px, 32px, 36px, 40px, 48px, 56px, 64px, 72px)
9. Validate typography hierarchy
10. Export as tokens (JSON, CSS, SCSS)
Provide complete typography documentation.
VARIATIONS
QUICKList all fonts and sizes from [FILE_KEY].
DETAILEDTypography system from [FILE_KEY]: fonts, sizes, weights, line heights, grouped by purpose, scale validation.
COMPLETEFull typography scale extraction from [FILE_KEY]. Include: all font families/sizes/weights, semantic grouping, token naming, line heights/spacing, scale validation, hierarchy check, exports (JSON/CSS/SCSS), documentation.
Expected Output
Complete typography scale with token names, values, and semantic grouping.
Example Output
Typography Scale: [FILE_KEY] FONT FAMILIES: - Primary: Inter - Display: Montserrat - Mono: IBM Plex Mono DISPLAY SIZES: - typography-display-large: 72px, weight 700, line-height 1.2 - typography-display-medium: 64px, weight 600, line-height 1.2 - typography-display-small: 56px, weight 600, line-height 1.3 HEADING SIZES: - typography-h1: 48px, weight 700, line-height 1.2 - typography-h2: 36px, weight 700, line-height 1.2 - typography-h3: 28px, weight 600, line-height 1.3 - typography-h4: 24px, weight 600, line-height 1.3 BODY SIZES: - typography-body-lg: 18px, weight 400, line-height 1.6 - typography-body-base: 16px, weight 400, line-height 1.6 - typography-body-sm: 14px, weight 400, line-height 1.5 CAPTION/LABEL: - typography-caption: 12px, weight 500, line-height 1.4 - typography-label: 14px, weight 500, line-height 1.4 Hierarchy Validation: ✓ OPTIMAL - Good contrast between sizes - Consistent line-height ratios - Clear semantic grouping Exports: ✓ typography.json ✓ typography.css ✓ typography.scss
22
Generate Typography CSS
Convert typography tokens to production-ready CSS/SCSS.
Chat
CLI
Automation
Prompt #22 — Chat
Generate typography CSS from [FILE_KEY]: 1. Create CSS custom properties for all typography values 2. Generate utility classes for semantic usage (.text-h1, .text-body, etc.) 3. Include responsive typography (mobile, tablet, desktop sizes) 4. Create SCSS mixins for typography declarations 5. Add font-face declarations for custom fonts 6. Include fallback fonts and font stacks 7. Generate Tailwind config if applicable 8. Add documentation comments 9. Support both CSS and SCSS output Provide copy-paste ready code.
VARIATIONS
QUICKCSS variables for typography from [FILE_KEY].
DETAILEDTypography CSS: variables, utility classes, responsive, font-face, fallbacks, Tailwind config.
FULLProduction-ready typography CSS from [FILE_KEY]. Include: CSS variables, utility classes, responsive variants, SCSS mixins, font-face declarations, font stacks, Tailwind config, documentation, copy-paste ready.
Expected Output
CSS files with custom properties, utility classes, responsive variants, and SCSS mixins.
Example Output
/* Typography CSS Variables */
:root {
--font-primary: 'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
--font-display: 'Montserrat', sans-serif;
--font-mono: 'IBM Plex Mono', monospace;
--typography-h1: var(--font-primary), 48px, 700, 1.2;
--typography-body-base: var(--font-primary), 16px, 400, 1.6;
}
/* Utility Classes */
.text-h1 {
font: 700 48px/1.2 var(--font-primary);
letter-spacing: -0.5px;
}
.text-body {
font: 400 16px/1.6 var(--font-primary);
letter-spacing: 0;
}
/* Responsive Variants */
@media (max-width: 768px) {
.text-h1 { font-size: 36px; }
.text-body { font-size: 14px; }
}
/* SCSS Mixin */
@mixin typography($style) {
@if $style == 'h1' {
font: 700 48px/1.2 var(--font-primary);
}
}
/* Font Face */
@font-face {
font-family: 'Inter';
src: url('Inter-Regular.woff2') format('woff2');
font-weight: 400;
}23
Extract Spacing System
Extract padding, margin, gap values to create spacing/sizing tokens.
Chat
CLI
Automation
Prompt #23 — Chat
Extract spacing system from [FILE_KEY]:
1. Find all padding values used in components
2. Find all margin/gap values
3. Identify spacing scale (4px, 8px, 12px, 16px, 20px, 24px, etc.)
4. Extract from auto-layout gap values
5. Extract from frame padding
6. Group by purpose (content padding, component gaps, page margins)
7. Identify spacing inconsistencies
8. Create token names (spacing-{unit})
9. Generate scale documentation
10. Export as tokens
Provide validated spacing scale.
VARIATIONS
QUICKWhat spacing values are used in [FILE_KEY]?
DETAILEDSpacing system from [FILE_KEY]: all padding/margin/gap values, identified scale, grouped by purpose, inconsistencies flagged.
COMPLETEComplete spacing system extraction from [FILE_KEY]. Include: all padding/margin/gap values, identified scale with documentation, grouping by purpose, inconsistency detection, validation, token generation, export.
Expected Output
Identified spacing scale with grouping by purpose and token definitions.
Example Output
Spacing System: [FILE_KEY] IDENTIFIED SCALE: - 4px (micro-spacing) - 8px (extra-small) - 12px (small) - 16px (base) - 20px (medium) - 24px (large) - 32px (extra-large) - 40px (2xl) - 48px (3xl) BY PURPOSE: COMPONENT PADDING: - Buttons: 12px horizontal, 8px vertical - Cards: 24px all sides - Form inputs: 12px horizontal, 10px vertical COMPONENT GAPS: - Button groups: 8px - Form layouts: 12px - Grid items: 16px CONTENT PADDING: - Page margins: 24px (mobile), 40px (desktop) - Section spacing: 48px - List item spacing: 16px INCONSISTENCIES FOUND (2): ⚠️ Button padding varies: 8px, 10px, 12px (should standardize to 8px) ⚠️ Card spacing: 24px and 32px used (should standardize to 24px) TOKENS: spacing-xs: 4px spacing-sm: 8px spacing-md: 16px spacing-lg: 24px spacing-xl: 40px
24
Generate Spacing Tokens
Convert spacing values to exportable tokens for CSS and design systems.
Chat
CLI
Automation
Prompt #24 — Chat
Generate spacing token definitions from [FILE_KEY]:
1. Extract all spacing values and create systematic scale
2. Define token names: spacing-{size} (xs, sm, md, lg, xl, 2xl, 3xl)
3. Create multiple formats: JSON, CSS, SCSS, Tailwind, JavaScript
4. Include documentation with use cases
5. Generate CSS custom properties
6. Create Tailwind extend config
7. Add validation for spacing consistency
8. Provide migration guide if changing spacing system
9. Export ready-to-use files
Provide production-ready spacing system.
VARIATIONS
QUICKGenerate spacing tokens JSON from [FILE_KEY].
DETAILEDSpacing tokens: scale definition, multiple formats (JSON/CSS/SCSS/Tailwind), documentation, CSS variables.
FULLComplete spacing token generation from [FILE_KEY]. Include: systematic scale, token naming conventions, multiple formats (JSON/CSS/SCSS/Tailwind/JS), documentation with use cases, CSS variables, Tailwind config, validation, migration guide.
Expected Output
Spacing token definitions in multiple formats with documentation and Tailwind config.
Example Output
{
"spacing": {
"xs": { "value": "4px", "description": "Micro-spacing for tight layouts", "usage": "Icon gaps, tight spacing" },
"sm": { "value": "8px", "description": "Small spacing", "usage": "Button padding, component gaps" },
"md": { "value": "16px", "description": "Base spacing", "usage": "Default padding, list spacing" },
"lg": { "value": "24px", "description": "Large spacing", "usage": "Card padding, section gaps" },
"xl": { "value": "40px", "description": "Extra-large spacing", "usage": "Page margins, large sections" },
"2xl": { "value": "48px", "description": "2x large", "usage": "Major section spacing" },
"3xl": { "value": "64px", "description": "3x large", "usage": "Page-level spacing" }
}
}
/* CSS */
:root {
--spacing-xs: 4px;
--spacing-sm: 8px;
--spacing-md: 16px;
--spacing-lg: 24px;
}
/* Tailwind */
theme: {
spacing: {
xs: '4px',
sm: '8px',
md: '16px',
lg: '24px',
xl: '40px'
}
}25
Extract Border Radius Values
Find all border radius values to create corner radius tokens.
Chat
CLI
Automation
Prompt #25 — Chat
Extract border radius system from [FILE_KEY]: 1. Find all border radius values used 2. Identify radius scale (0, 2px, 4px, 8px, 12px, 16px, 999px) 3. Find element-specific radius patterns (buttons, cards, inputs) 4. Flag inconsistencies 5. Create semantic token names (radius-none, radius-sm, radius-md, radius-lg, radius-full) 6. Document radius-to-size ratio (px or percentage) 7. Show usage examples for each radius 8. Export as tokens Validate corner radius system consistency.
VARIATIONS
QUICKWhat border radius values are in [FILE_KEY]?
DETAILEDBorder radius system: all values, identified scale, semantic naming, usage examples, inconsistencies flagged.
COMPLETEComplete border radius extraction from [FILE_KEY]. Include: all values, identified scale, semantic naming conventions, pixel/percentage ratios, usage patterns, documentation examples, inconsistencies flagged, token export.
Expected Output
Identified border radius scale with semantic token names and usage documentation.
Example Output
Border Radius System: [FILE_KEY]
IDENTIFIED SCALE:
✓ 0px (radius-none) — Square elements
✓ 4px (radius-sm) — Tight components
✓ 8px (radius-md) — Default (buttons, inputs, cards)
✓ 12px (radius-lg) — Large components
✓ 16px (radius-xl) — Extra-large components
✓ 999px (radius-full) — Circular elements
USAGE PATTERNS:
- Buttons: 8px (87% of buttons)
- Inputs: 4px (92% of inputs)
- Cards: 12px (100% of cards)
- Images: 0px or 999px (100%)
- Badges: 4px (100%)
VALIDATION: ✓ CONSISTENT
- Good semantic separation
- Appropriate scale for component hierarchy
TOKENS:
radius-none: 0px
radius-sm: 4px
radius-md: 8px
radius-lg: 12px
radius-xl: 16px
radius-full: 999px
CSS:
.rounded-sm { border-radius: var(--radius-sm); }
.rounded-md { border-radius: var(--radius-md); }
.rounded-full { border-radius: var(--radius-full); }26
Extract Shadow/Elevation Tokens
Export box shadows and elevation values as design tokens.
Chat
CLI
Automation
Prompt #26 — Chat
Extract shadow and elevation system from [FILE_KEY]: 1. Find all unique shadow values 2. Identify elevation levels (shadow-sm, shadow-md, shadow-lg, shadow-xl) 3. Extract shadow properties: blur, spread, offset, color 4. Document elevation scale (1-5 or similar) 5. Find shadows used for specific purposes (hover, focus, modal) 6. Create semantic token names 7. Validate consistency 8. Generate CSS box-shadow code 9. Export formats: CSS, SCSS, JSON 10. Provide visual documentation Provide shadow system tokens.
VARIATIONS
QUICKWhat shadows are used in [FILE_KEY]?
DETAILEDShadow/elevation system: all shadows, scale levels, token names, CSS output, consistency check.
COMPLETEComplete shadow and elevation extraction from [FILE_KEY]. Include: all shadow values, identified scale (elevation levels), semantic naming, shadow properties breakdown, usage patterns, token generation, CSS/SCSS output, visual documentation, validation.
Expected Output
Shadow/elevation scale with token definitions and CSS box-shadow values.
Example Output
Shadow & Elevation System: [FILE_KEY] IDENTIFIED SCALE (5 levels): Elevation 1 (shadow-sm): - X: 0, Y: 1px, Blur: 2px, Spread: 0 - Color: rgba(0,0,0, 0.05) - Usage: Subtle depth, hover states - CSS: box-shadow: 0 1px 2px 0 rgba(0, 0, 0, 0.05); Elevation 2 (shadow-md): - X: 0, Y: 4px, Blur: 6px, Spread: -2px - Color: rgba(0,0,0, 0.1) - Usage: Cards, default depth - CSS: box-shadow: 0 4px 6px -2px rgba(0, 0, 0, 0.1); Elevation 3 (shadow-lg): - X: 0, Y: 10px, Blur: 15px, Spread: -3px - Color: rgba(0,0,0, 0.1) - Usage: Modals, floating elements Elevation 4 (shadow-xl): - X: 0, Y: 20px, Blur: 25px, Spread: -5px - Color: rgba(0,0,0, 0.1) - Usage: Popovers, top-layer elements USAGE: - Default cards: shadow-md (100%) - Button hover: shadow-sm (89%) - Modals: shadow-xl (100%) VALIDATION: ✓ CONSISTENT - Good elevation hierarchy - Appropriate blur/spread ratios TOKENS: shadow-sm: 0 1px 2px 0 rgba(0, 0, 0, 0.05) shadow-md: 0 4px 6px -2px rgba(0, 0, 0, 0.1) shadow-lg: 0 10px 15px -3px rgba(0, 0, 0, 0.1) shadow-xl: 0 20px 25px -5px rgba(0, 0, 0, 0.1)
27
Extract Opacity Tokens
Create opacity/alpha scale tokens from opacity values used in design.
Chat
CLI
Automation
Prompt #27 — Chat
Extract opacity system from [FILE_KEY]: 1. Find all opacity values used (as percentages or decimals) 2. Identify opacity scale (0%, 10%, 25%, 50%, 75%, 90%, 100%) 3. Document opacity use cases (disabled states, overlays, hover effects) 4. Create semantic token names (opacity-disabled, opacity-muted, opacity-hover, opacity-full) 5. Flag any inconsistencies 6. Generate tokens with documentation 7. Create CSS custom properties 8. Provide usage examples 9. Export formats: JSON, CSS, SCSS Provide opacity scale documentation.
VARIATIONS
QUICKWhat opacity levels are in [FILE_KEY]?
DETAILEDOpacity system: identified scale, semantic naming, use cases, CSS variables, exports.
COMPLETEComplete opacity token extraction from [FILE_KEY]. Include: identified scale, semantic naming conventions, use case documentation, consistency validation, token generation, CSS/JSON/SCSS exports, usage examples.
Expected Output
Opacity scale with semantic token names and documented use cases.
Example Output
Opacity System: [FILE_KEY]
IDENTIFIED SCALE:
- 0% (opacity-none) — Invisible/hidden
- 10% (opacity-extra-light) — Subtle overlays
- 25% (opacity-light) — Light interaction feedback
- 50% (opacity-medium) — Disabled states
- 75% (opacity-dark) — Hover/focus overlays
- 100% (opacity-full) — Fully opaque
USE CASES:
DISABLED STATES (50% opacity):
✓ Disabled buttons (gray text at 50%)
✓ Disabled inputs (background at 50%)
✓ Disabled form elements (icons at 50%)
HOVER/FOCUS (75% opacity):
✓ Hover overlay on images
✓ Focus state on interactive elements
✓ Active state indicator
OVERLAYS (10-25% opacity):
✓ Modal backgrounds (black at 10%)
✓ Backdrop overlay (black at 25%)
✓ Loading overlay (25%)
SUBTLE INTERACTIONS (10% opacity):
✓ Tooltip backgrounds
✓ Light emphasis (25%)
TOKENS:
opacity-none: 0
opacity-extra-light: 10%
opacity-light: 25%
opacity-medium: 50%
opacity-dark: 75%
opacity-full: 100%
CSS:
:root {
--opacity-none: 0;
--opacity-light: 0.25;
--opacity-medium: 0.5;
--opacity-dark: 0.75;
--opacity-full: 1;
}28
Generate Full Token File
Create a complete, production-ready design tokens file from all extracted values.
Chat
CLI
Automation
Prompt #28 — Chat
Generate complete design token file from [FILE_KEY]: 1. Combine all tokens: colors, typography, spacing, shadows, radius, opacity 2. Use W3C Design Tokens standard format 3. Include metadata: version, created, updated, author 4. Group tokens by category with clear structure 5. Add comprehensive documentation 6. Generate multiple formats: JSON, CSS, SCSS, Tailwind, JavaScript 7. Create token version management 8. Include migration guide if tokens changed 9. Validate all tokens 10. Ready for: design tools, code repositories, CI/CD Provide production-ready token package.
VARIATIONS
QUICKGenerate all tokens from [FILE_KEY] as JSON.
DETAILEDComplete token file: all categories, W3C format, multiple exports (JSON/CSS/SCSS/Tailwind), documentation.
PRODUCTIONProduction-ready design token package from [FILE_KEY]. Include: W3C standard format, all token categories, metadata/versioning, comprehensive documentation, multiple format exports, validation, migration guides, ready for design/code/CI-CD integration.
Expected Output
Complete token file in W3C format with all categories, multiple format exports, and documentation.
Example Output
{
"$schema": "https://tokens.studio/schema.json",
"$version": "1.0.0",
"metadata": {
"created": "2026-03-15",
"updated": "2026-03-15",
"source": "[FILE_KEY]",
"author": "Design Team"
},
"color": {
"primary": {
"50": { "value": "#EFF6FF" },
"500": { "value": "#2563EB" },
"900": { "value": "#1E3A8A" }
},
"neutral": {
"0": { "value": "#FFFFFF" },
"900": { "value": "#111827" }
}
},
"typography": {
"h1": { "value": { "fontFamily": "Inter", "fontSize": "48px", "fontWeight": "700", "lineHeight": "1.2" } },
"body": { "value": { "fontFamily": "Inter", "fontSize": "16px", "fontWeight": "400", "lineHeight": "1.6" } }
},
"spacing": {
"xs": { "value": "4px" },
"sm": { "value": "8px" },
"md": { "value": "16px" }
},
"shadow": {
"sm": { "value": "0 1px 2px 0 rgba(0, 0, 0, 0.05)" },
"md": { "value": "0 4px 6px -2px rgba(0, 0, 0, 0.1)" }
}
}
EXPORTS:
✓ tokens.json
✓ tokens.css
✓ tokens.scss
✓ tailwind.config.js
✓ tokens.js
VALIDATION: ✓ All tokens valid
Format: ✓ W3C compliant
Completeness: ✓ 100% (347 tokens)29
Compare Tokens Across Files
Compare design tokens between two Figma files to identify differences.
Chat
CLI
Automation
Prompt #29 — Chat
Compare design tokens between [FILE_KEY_1] and [FILE_KEY_2]: 1. Extract tokens from both files 2. Identify new tokens in each file 3. Find tokens that exist in both but with different values 4. Show removed tokens (in first but not second) 5. Generate diff report 6. Highlight breaking changes 7. Suggest consolidation strategy 8. Show which file is the source of truth 9. Provide migration recommendations Use case: Compare old design system to new version, or compare two brand variants.
VARIATIONS
QUICKCompare tokens from [FILE_KEY_1] vs [FILE_KEY_2]. Show differences.
DETAILEDToken diff between files: new tokens, changed tokens, removed tokens, breaking changes, consolidation strategy.
ANALYSISComplete token comparison between [FILE_KEY_1] and [FILE_KEY_2]. Show: new/changed/removed tokens, diff values, breaking changes, source of truth, migration recommendations, consolidation strategy.
Expected Output
Token diff report showing new/changed/removed tokens with values and recommendations.
Example Output
Token Diff Report: [FILE_KEY_1] vs [FILE_KEY_2] NEW TOKENS (12): ✓ color-success-500: #10B981 (in v2 only) ✓ color-warning-500: #F59E0B (in v2 only) ✓ typography-label-lg: 14px (in v2 only) CHANGED TOKENS (8): ⚠️ color-primary-500: - v1: #2563EB - v2: #3B82F6 (BREAKING) ⚠️ spacing-md: - v1: 16px - v2: 12px (BREAKING) REMOVED TOKENS (2): ✗ color-legacy-blue: #1E40AF (deprecated in v2) ✗ spacing-extra-large: 64px (consolidated into xl) BREAKING CHANGES (3): 1. Primary color changed (affects all buttons/links) 2. Spacing scale adjusted (affects layouts) 3. Typography scale updated (affects text sizes) RECOMMENDATION: → Use v2 as source of truth → Plan migration with 2-week runway → Update all implementations of changed tokens → Retire 2 deprecated tokens → Add 12 new tokens to codebase
30
Validate Token Consistency
Audit tokens for consistency, unused values, and compliance issues.
Chat
CLI
Automation
Prompt #30 — Chat
Validate token consistency in [FILE_KEY]: 1. Find unused/orphaned tokens (defined but never used) 2. Detect duplicate tokens (same value, different names) 3. Identify naming convention violations 4. Flag tokens missing metadata/documentation 5. Check color contrast compliance (WCAG AA/AAA) 6. Validate typography hierarchy 7. Check spacing scale consistency 8. Audit shadow/elevation hierarchy 9. Generate validation report with recommendations 10. Provide remediation checklist Provide comprehensive token audit.
VARIATIONS
QUICKCheck tokens in [FILE_KEY] for issues. Are they consistent?
DETAILEDToken validation: unused tokens, duplicates, naming violations, missing docs, contrast issues, hierarchy checks, remediation recommendations.
COMPLETEComplete token validation audit of [FILE_KEY]. Include: unused/orphaned tokens, duplicates, naming violations, missing documentation, contrast compliance, hierarchy validation, consistency checks, detailed report with remediation checklist.
Expected Output
Validation report identifying issues (unused, duplicates, naming violations) with remediation recommendations.
Example Output
Token Validation Report: [FILE_KEY] TOTAL TOKENS: 347 VALIDATION SCORE: 87% (Good, room for improvement) UNUSED TOKENS (12) 🗑️: ✗ color-legacy-red: #E64646 (never used, can delete) ✗ color-legacy-blue: #1E40AF (never used, can delete) ✗ spacing-extra-extra-large: 96px (orphaned, consolidate) DUPLICATE TOKENS (4) ⚠️: ✗ color-primary-500 = #2563EB (same as primary-default) ✗ color-neutral-900 = #111827 (same as text-primary) ✗ spacing-md = 16px (same as spacing-base) NAMING VIOLATIONS (3) ⚠️: ✗ primaryColor (should be color-primary) ✗ med_spacing (should be spacing-md) ✗ FontLarge (should be typography-lg) MISSING DOCUMENTATION (8): ✗ shadow-custom-1 (no description) ✗ color-custom-purple (purpose unknown) CONTRAST ISSUES (2) ❌ WCAG AA FAILURE: ✗ color-neutral-500 on color-neutral-100 = 2.8:1 (needs 4.5:1) ✗ color-gray-600 on color-gray-200 = 3.1:1 (needs 4.5:1) REMEDIATION CHECKLIST: ☐ Delete 12 unused tokens ☐ Consolidate 4 duplicate tokens ☐ Rename 3 tokens to follow conventions ☐ Add documentation to 8 tokens ☐ Fix 2 contrast issues ESTIMATED EFFORT: 2-3 hours IMPACT: High (cleaner system, easier maintenance)
4
Component Analysis
10 prompts
31
List All Components
Get a comprehensive inventory of all components in a Figma file.
Chat
CLI
Automation
Prompt #31 — Chat
List all components in [FILE_KEY]: 1. List every published component with name and path 2. Show variant count for each component 3. Show component sizes (dimensions) 4. Show instance count (how many times used) 5. Identify main components vs. variants 6. Group by category (buttons, forms, etc.) 7. Mark deprecated components 8. Calculate component coverage 9. Sort by usage frequency 10. Export as structured data Provide complete component inventory.
VARIATIONS
QUICKList all components in [FILE_KEY].
DETAILEDAll components with: names, paths, variants, sizes, instance counts, grouping by category, sorted by usage.
COMPREHENSIVEComplete component inventory of [FILE_KEY]. Show: all components with paths, variant counts, dimensions, instance usage, categorization, deprecation status, coverage metrics, sorted by frequency.
Expected Output
Organized list of all components with variant counts, usage statistics, and categorization.
Example Output
Component Inventory: [FILE_KEY] Total Components: 47 Total Variants: 234 Component Coverage: 87% (well-adopted) BUTTONS (8 components): ✓ Button/Primary | Variants: 12 | Instances: 287 | 64×48 ✓ Button/Secondary | Variants: 8 | Instances: 156 | 64×48 ✓ Button/Ghost | Variants: 4 | Instances: 89 | 64×48 FORM INPUTS (12 components): ✓ Input/Text | Variants: 6 | Instances: 203 | 320×40 ✓ Input/Checkbox | Variants: 3 | Instances: 95 | 20×20 NAVIGATION (5 components): ✓ NavBar | Variants: 2 | Instances: 34 | Variable ✓ Breadcrumbs | Variants: 1 | Instances: 12 | Variable DEPRECATED (2) ⚠️: ✗ OldButton (replace with Button/Primary) ✗ LegacyInput (replace with Input/Text) Mostly Used: 1. Button/Primary (287 instances) 2. Input/Text (203 instances) 3. Badge (156 instances)
32
Component Variant Matrix
Visualize all variants of a component and their combinations.
Chat
CLI
Automation
Prompt #32 — Chat
Show variant matrix for component '[COMPONENT_NAME]' in [FILE_KEY]: 1. List all variant properties 2. Show all variant combinations (matrix view) 3. Identify missing variants 4. Show variant nesting (if applicable) 5. Display variant default values 6. Show variant reset behavior 7. Highlight problematic variants 8. Document variant naming convention Provide complete variant specification.
VARIATIONS
QUICKWhat variants does '[COMPONENT_NAME]' have?
DETAILEDComplete variant matrix for '[COMPONENT_NAME]': properties, combinations, missing variants, defaults, naming convention.
TECHNICALFull technical variant specification for '[COMPONENT_NAME]'. Show: variant properties, complete combination matrix, missing/incomplete variants, defaults, reset behavior, naming conventions, problematic variants.
Expected Output
Variant matrix showing all property combinations and their coverage.
Example Output
Component Variants: Button/Primary Variant Properties (3): 1. size: small | medium | large 2. state: default | hover | active | disabled 3. icon: none | with-icon Variant Combinations (24 total): ✓ [small, default, none] — exists ✓ [small, default, with-icon] — exists ✓ [small, hover, none] — exists ✓ [small, hover, with-icon] — exists ✓ [small, active, none] — exists ... ✓ [large, disabled, with-icon] — exists ✗ Missing: None (all combinations present) Defaults: - size: medium - state: default - icon: none Variant Naming: [size]-[state]-[icon] Example: medium-hover-with-icon ✓ Consistent
33
Component Prop Table
Document component properties, types, defaults, and descriptions.
Chat
CLI
Automation
Prompt #33 — Chat
Generate prop documentation for '[COMPONENT_NAME]' in [FILE_KEY]: 1. List all overrideable properties 2. Document property types (text, boolean, select, etc.) 3. Show default values 4. Provide descriptions and use cases 5. Show constraints/validation (min/max, allowed values) 6. Identify required vs. optional props 7. Document prop dependencies 8. Generate TypeScript/PropTypes definitions 9. Provide usage examples Format as developer documentation.
VARIATIONS
QUICKWhat props does '[COMPONENT_NAME]' have?
DETAILEDComponent props: types, defaults, descriptions, constraints, required/optional, TypeScript definitions.
DEV-READYComplete prop documentation for '[COMPONENT_NAME]'. Show: all properties with types/defaults/descriptions, constraints/validation, required/optional, dependencies, TypeScript/PropTypes, usage examples, production-ready.
Expected Output
Component prop table with types, defaults, descriptions, and code examples.
Example Output
Component Props: Button/Primary
| Prop | Type | Default | Description | Validation |
|------|------|---------|---|---|
| label | string | "Click me" | Button text | max 50 chars |
| size | enum | "medium" | Button size (small/medium/large) | — |
| disabled | boolean | false | Disable button | — |
| icon | boolean | false | Show icon | — |
| onClick | function | — | Click handler | Required |
Dependencies:
- If icon=true, iconName prop must be provided
- disabled=true → disables onClick
TypeScript:
interface ButtonProps {
label: string;
size: 'small' | 'medium' | 'large';
disabled?: boolean;
icon?: boolean;
onClick: () => void;
}
Usage:
<Button label="Submit" size="large" onClick={handleSubmit} />34
Component Usage Count
Determine how widely a component is used across the design file.
Chat
CLI
Automation
Prompt #34 — Chat
Analyze component usage for '[COMPONENT_NAME]' in [FILE_KEY]: 1. Count total instances in file 2. Show usage by page 3. Show usage by frame/section 4. Identify most-used variants 5. Show usage trend (if versioning available) 6. Flag over-used components 7. Identify components that should be consolidated 8. Suggest refactoring opportunities Provide adoption and usage metrics.
VARIATIONS
QUICKHow many times is '[COMPONENT_NAME]' used in [FILE_KEY]?
DETAILEDComponent usage: instance count, usage by page/section, variant popularity, adoption metrics.
ANALYSISComplete usage analysis for '[COMPONENT_NAME]' in [FILE_KEY]. Show: instance counts, usage distribution (pages/sections), variant popularity, trend analysis, consolidation opportunities, refactoring suggestions.
Expected Output
Usage statistics showing instance counts by location and variant popularity.
Example Output
Component Usage: Button/Primary Total Instances: 287 (across file) Adoption Rate: 92% (highly used) BY PAGE: - Components: 12 instances (master + examples) - Patterns: 45 instances (in pattern templates) - Marketing Site: 124 instances (primary CTA) - App Prototype: 89 instances (in flows) - Archive: 17 instances (old designs) BY VARIANT: - medium-default: 142 instances (49%) — Most popular - large-default: 89 instances (31%) - small-default: 34 instances (12%) - medium-hover: 22 instances (8%) ADOPTION TREND: ↑ Increasing - January: 156 instances - February: 198 instances - March: 287 instances OBSERVATION: Excellent adoption, good distribution RECOMMENDATION: Maintain current component design, monitor for new variants
35
Component Dependency Tree
Understand component nesting and dependencies.
Chat
CLI
Automation
Prompt #35 — Chat
Map component dependency tree for '[COMPONENT_NAME]' in [FILE_KEY]: 1. Identify main component 2. Show all child/nested components 3. List dependencies (what components are used inside) 4. Show nesting depth 5. Identify circular dependencies 6. Flag problematic nesting 7. Document data flow through components 8. Suggest refactoring if overly complex Provide component architecture diagram.
VARIATIONS
QUICKWhat components does '[COMPONENT_NAME]' use?
DETAILEDComponent dependencies: nested components, child/parent relationships, nesting depth, data flow.
ARCHITECTUREComplete dependency tree for '[COMPONENT_NAME]'. Show: all nested components, parent/child relationships, nesting depth, circular dependencies, data flow, architectural issues, refactoring suggestions.
Expected Output
Tree view of component hierarchy with parent/child relationships and nesting depth.
Example Output
Component Dependency Tree: Card
Card (main)
├─ Icon/Decorative (child)
│ └─ SVG (asset)
├─ Heading (child - typography)
│ └─ Text (primitive)
├─ Content (child)
│ └─ Text (primitive)
└─ Button/Primary (child - component)
├─ Icon/Check (nested child)
└─ Text (primitive)
Nesting Depth: 3 levels ✓ Reasonable
Circular Dependencies: None ✓ Good
Child Components: 2 (Button/Primary, Icon/Decorative)
Primitive Elements: 4 (Text, SVG)
Data Flow:
Card ← Title/Description (text overrides)
← Button state (prop override)
← Icon color (style override)
Complexity: Moderate (good for maintainability)
Recommendation: Current structure is optimal36
Detect Detached Instances
Find component instances that have been detached from their main component.
Chat
CLI
Automation
Prompt #36 — Chat
Scan [FILE_KEY] for detached component instances: 1. Find all detached instances 2. Show location (page, frame) of each 3. Show what component they were (original source) 4. Show how many detachments per component 5. Identify likely causes (old design, intentional override) 6. Suggest reattachment strategy 7. Identify if design differs from original 8. Flag high-risk detachments 9. Provide cleanup recommendations Provide detached instances audit.
VARIATIONS
QUICKAre there detached component instances in [FILE_KEY]?
DETAILEDAll detached instances: location, original component, count, reattachment recommendations.
AUDITComplete audit of detached instances in [FILE_KEY]. Show: all detachments with locations, original components, count by component, causes, design differences, risk assessment, cleanup strategy, reattachment plan.
Expected Output
Inventory of detached instances with locations and reattachment recommendations.
Example Output
Detached Component Instances: [FILE_KEY] Total Detached: 8 instances ⚠️ Detached from Button/Primary (5): ✗ Page: Marketing Site > Hero Element: "CTA Button variant" Status: Custom styling (differs from original) Recommendation: Reattach or create new variant ✗ Page: Archive > Old Designs Element: "Special Button (2023)" Status: Intentional override (old design) Recommendation: Safe to delete or archive Detached from Card (2): ✗ Page: Patterns > Featured Card Element: "Featured Card variant" Status: Minor customization Recommendation: Create proper variant instead Detached from Icon/Check (1): ✗ Page: Components > Icon variants Status: Color override Recommendation: Reattach to Icon/Check, use color variant RISK ASSESSMENT: - High Risk (2): Significant deviations from original - Medium Risk (4): Minor customizations - Low Risk (2): In archived pages (safe) CLEANUP PLAN: 1. Reattach 4 low-deviation instances 2. Create 3 proper variants 3. Archive 2 old detached instances ESTIMATED TIME: 30 minutes
37
Component Documentation
Auto-generate documentation for component usage and specifications.
Chat
CLI
Automation
Prompt #37 — Chat
Generate documentation for component '[COMPONENT_NAME]' in [FILE_KEY]: 1. Component overview (purpose, use cases) 2. Visual examples (all variants) 3. Prop table with descriptions 4. Do's and Don'ts guidelines 5. Accessibility features 6. Design tokens used 7. Code examples (React, HTML, etc.) 8. Common patterns and usage 9. Troubleshooting guide 10. Links to related components Generate production-ready Storybook/documentation format.
VARIATIONS
QUICKGenerate basic docs for '[COMPONENT_NAME]'.
DETAILEDComponent documentation: overview, variants, props, do's/don'ts, accessibility, tokens, code examples.
PROFESSIONALProduction-ready documentation for '[COMPONENT_NAME]'. Include: overview/use cases, visual examples, prop tables, do's/don'ts guidelines, accessibility, tokens, code examples (React/HTML), patterns, troubleshooting, related components, Storybook-ready.
Expected Output
Comprehensive component documentation in Markdown/HTML format ready for publication.
Example Output
# Button/Primary Component
## Overview
Primary action button for important user actions.
## Use Cases
- Submit forms
- Confirm actions
- Primary navigation
## Props
| Prop | Type | Default | Description |
|------|------|---------|-------------|
| label | string | — | Button text |
| size | enum | medium | small, medium, large |
| disabled | boolean | false | Disable button |
## Do's and Don'ts
✓ Do: Use for primary actions
✗ Don't: Use for secondary actions
✓ Do: Ensure label is descriptive
✗ Don't: Use vague labels like "Click here"
## Accessibility
- Includes proper ARIA labels
- Keyboard navigable (Tab/Space/Enter)
- Focus visible indicator
## Design Tokens Used
- color-primary-500 (background)
- color-white (text)
- shadow-md (elevation)
## Code Example
```jsx
<Button label="Submit" size="large" onClick={handleSubmit} />
```38
Compare Component Versions
Identify differences between old and new component versions.
Chat
CLI
Automation
Prompt #38 — Chat
Compare component '[COMPONENT_NAME]' across versions in [FILE_KEY]: 1. Get current version 2. Get previous version 3. Identify property changes 4. Show visual differences 5. Check variant changes 6. List breaking changes 7. Identify style/color updates 8. Show size/dimension changes 9. Provide migration guide 10. Generate upgrade checklist Provide version comparison and upgrade guide.
VARIATIONS
QUICKWhat changed in '[COMPONENT_NAME]' between versions?
DETAILEDComponent comparison: property changes, visual differences, breaking changes, variant updates, migration guide.
MIGRATIONComplete version comparison for '[COMPONENT_NAME]'. Show: all changes (properties/visuals/variants/styles), breaking changes identified, upgrade impact, migration guide, compatibility notes, checklist.
Expected Output
Detailed comparison showing changes, breaking changes, and migration steps.
Example Output
Component Version Comparison: Button/Primary Version 1.0 → Version 2.0 PROPERTY CHANGES: ✓ New prop: icon (boolean) ✓ New prop: loading (boolean) ⚠️ Changed: size values (sm/md/lg → small/medium/large) STYLE CHANGES: ⚠️ Color: #2563EB → #3B82F6 (slightly lighter) ⚠️ Border radius: 6px → 8px ✓ Added: transition effect (100ms ease) VARIANT CHANGES: ✓ Added: loading state ✓ Added: icon variants (8 variants) ⚠️ Removed: deprecated outline variant BREAKING CHANGES (3): 1. Size prop value change (sm → small) 2. Color value updated 3. outline variant removed MIGRATION GUIDE: 1. Update size prop: 'md' → 'medium' 2. Update color references: #2563EB → #3B82F6 3. Replace outline buttons with secondary variant 4. Test loading states ESTIMATED EFFORT: 4 hours RISK: Medium (3 breaking changes)
39
Find Unused Components
Identify components that are defined but not used in the design file.
Chat
CLI
Automation
Prompt #39 — Chat
Find unused components in [FILE_KEY]: 1. Identify components with zero instances 2. Show component details (size, last modified) 3. Identify potential reasons (deprecated, placeholder, WIP) 4. Show related components (variants, parents) 5. Flag components that should be consolidated 6. Suggest deletion candidates 7. Identify orphaned variants 8. Calculate file size savings if removed 9. Provide cleanup recommendations Provide unused component audit.
VARIATIONS
QUICKAre there unused components in [FILE_KEY]?
DETAILEDAll unused components: details, usage count, deletion candidates, space savings, cleanup recommendations.
AUDITComplete unused component audit of [FILE_KEY]. Show: all unused components with details, usage analysis, deletion safety, related variants, consolidation opportunities, space savings calculation, cleanup strategy.
Expected Output
List of unused components with deletion candidates and space savings estimates.
Example Output
Unused Components Audit: [FILE_KEY] Unused Components Found: 7 DELETION CANDIDATES (5): ✗ OldButton (v1.0) Last Modified: 6 months ago Instances: 0 Status: Deprecated (replaced by Button/Primary) Space: 45KB Recommendation: DELETE ✗ LegacyCard Last Modified: 8 months ago Instances: 0 Status: Archive (old design) Space: 32KB Recommendation: DELETE CONSOLIDATION CANDIDATES (2): ⚠️ Button/Primary-backup (exact duplicate of Button/Primary) Recommendation: DELETE (consolidate) Space: 12KB ⚠️ Icon/Arrow-old (similar to Icon/Arrow) Recommendation: DELETE or consolidate Space: 8KB TOTAL SPACE SAVINGS: 97KB (2% file size) CLEANUP CHECKLIST: ☐ Verify OldButton is deprecated ☐ Check if Button/Primary-backup is referenced anywhere ☐ Backup file (safety) ☐ Delete 7 unused components ☐ Run validation RISK: Low (all truly unused)
40
Component Naming Audit
Audit component names for consistency with naming conventions.
Chat
CLI
Automation
Prompt #40 — Chat
Audit component naming in [FILE_KEY]: 1. Check naming convention compliance 2. Identify inconsistent naming patterns 3. Find duplicate names or similar names 4. Flag confusing or unclear names 5. Check naming across variants 6. Identify components that violate hierarchy 7. Generate naming recommendations 8. Suggest renaming plan 9. Validate post-rename impact Provide naming consistency audit and renaming guide.
VARIATIONS
QUICKAre component names in [FILE_KEY] consistent?
DETAILEDNaming audit: convention compliance, inconsistencies, duplicates, confusing names, recommendations.
COMPLETEComplete component naming audit of [FILE_KEY]. Show: convention compliance, inconsistencies, duplicate/similar names, confusing names, hierarchy violations, naming recommendations, renaming plan, post-rename impact validation.
Expected Output
Naming audit report with inconsistencies identified and renaming recommendations.
Example Output
Component Naming Audit: [FILE_KEY] Naming Convention: Type/Name/State Expected Format: [ComponentType]/[ComponentName]/[Variant] COMPLIANCE: 78% (good, room for improvement) INCONSISTENCIES FOUND (8): ✗ PrimaryButton (should be: Button/Primary) ✗ Btn_Secondary (should be: Button/Secondary) ✗ CARD (should be: Card) ✗ formInput (should be: Input/Text) ✗ NavBarTop (should be: Navigation/Bar) ✗ icon-check (should be: Icon/Check) ✗ badge_success (should be: Badge/Success) ✗ TextSmall (should be: Typography/Label) DUPLICATES (2): ⚠️ Button (main) vs. button (variant) — conflicting casing ⚠️ Icon/Arrow vs. Icon/arrow — conflicting casing CONFUSING NAMES (3): ⚠️ "Element" (too generic, unclear purpose) ⚠️ "Item" (too vague, should be "List/Item") ⚠️ "Special" (not descriptive) HIERARCHY VIOLATIONS (2): ⚠️ Button/Primary/Large (too deep, should be: Button/Primary with size variant) ⚠️ Form/Input/Text/Required (should be: Input/Text with required state) RENAMING PLAN: 1. Rename 8 inconsistent components 2. Consolidate 2 duplicate casing issues 3. Rename 3 confusing components 4. Flatten 2 hierarchy violations IMPACT: Medium (update documentation, update instances: 347 components affected) ESTIMATED EFFORT: 3-4 hours
5
Figma to Code
14 prompts
41
Generate React Component
Convert a Figma component to production-ready React code.
Chat
CLI
Automation
Prompt #41 — Chat
Generate React component from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Extract component structure from Figma 2. Generate React TSX with TypeScript types 3. Create prop interface matching Figma variants 4. Extract and apply styles (CSS modules or styled-components) 5. Include accessibility (ARIA labels, semantic HTML) 6. Add PropTypes or TypeScript validation 7. Generate Storybook stories 8. Include unit test template 9. Add JSDoc documentation 10. Provide copy-paste ready code Generate production-ready React component.
VARIATIONS
QUICKGenerate React code for '[COMPONENT_NAME]' from [FILE_KEY].
TYPESCRIPTGenerate TSX with types, props interface, styled-components, Storybook stories.
FULLComplete React component from '[COMPONENT_NAME]'. Include: TSX with full TypeScript types, props interface, CSS modules/styled-components, accessibility features, Storybook stories, unit test template, JSDoc docs, copy-paste ready.
Expected Output
Production-ready React TSX component with types, styles, tests, and Storybook integration.
Example Output
// Button.tsx
import React from 'react';
import styles from './Button.module.css';
interface ButtonProps {
label: string;
size?: 'small' | 'medium' | 'large';
disabled?: boolean;
onClick?: () => void;
}
/**
* Primary action button component
* @param props - Button properties
*/
export const Button: React.FC<ButtonProps> = ({
label,
size = 'medium',
disabled = false,
onClick
}) => {
return (
<button
className={`${styles.button} ${styles[size]}`}
disabled={disabled}
onClick={onClick}
aria-label={label}
>
{label}
</button>
);
};
// Button.stories.tsx
export const Primary = () => <Button label="Click me" />;
export const Large = () => <Button label="Submit" size="large" />;42
Generate Vue Component
Convert Figma component to Vue 3 Single File Component.
Chat
CLI
Automation
Prompt #42 — Chat
Generate Vue 3 SFC from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create .vue Single File Component 2. Extract props and define reactive state 3. Apply extracted styles (scoped CSS) 4. Include TypeScript (script setup) 5. Add accessibility features 6. Generate component documentation 7. Create usage examples 8. Add type definitions 9. Include emits for events 10. Production-ready code Generate Vue 3 component.
VARIATIONS
QUICKGenerate Vue component for '[COMPONENT_NAME]'.
TYPESCRIPTGenerate Vue 3 SFC with TypeScript script setup, props, scoped styles, accessibility.
FULLComplete Vue 3 SFC from '[COMPONENT_NAME]'. Include: script setup with TypeScript, props with types, reactive state, scoped styles, accessibility, emits, documentation, usage examples, production-ready.
Expected Output
Production-ready Vue 3 Single File Component with TypeScript, styles, and documentation.
Example Output
<template>
<button
:class="['button', `button--${size}`]"
:disabled="disabled"
@click="$emit('click')"
:aria-label="label"
>
{{ label }}
</button>
</template>
<script setup lang="ts">
defineProps<{
label: string;
size?: 'small' | 'medium' | 'large';
disabled?: boolean;
}>();
defineEmits<{
click: [];
}>();
</script>
<style scoped>
.button {
padding: 12px 24px;
border: none;
border-radius: 8px;
cursor: pointer;
}
.button--medium {
font-size: 16px;
}
</style>43
Generate HTML/CSS
Convert Figma component to static HTML and CSS.
Chat
CLI
Automation
Prompt #43 — Chat
Generate HTML/CSS from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create semantic HTML structure 2. Extract styling to CSS 3. Use CSS custom properties for tokens 4. Make responsive (mobile-first) 5. Include accessibility (ARIA, semantic tags) 6. Add BEM naming convention for classes 7. Include hover/active/focus states 8. Generate self-contained HTML file 9. Include usage instructions 10. Copy-paste ready Generate standalone HTML/CSS component.
VARIATIONS
QUICKGenerate HTML/CSS for '[COMPONENT_NAME]'.
RESPONSIVEGenerate HTML/CSS with responsive design, CSS variables, accessibility, BEM naming.
COMPLETEComplete standalone HTML/CSS component from '[COMPONENT_NAME]'. Include: semantic HTML, CSS with variables, responsive design (mobile-first), accessibility, BEM naming, all states (hover/active/focus), self-contained, usage docs, copy-paste ready.
Expected Output
Standalone HTML/CSS files with semantic markup and responsive styling.
Example Output
<button class="btn btn--primary btn--medium">
Click me
</button>
<style>
:root {
--btn-padding: 12px 24px;
--btn-radius: 8px;
--color-primary: #2563EB;
}
.btn {
padding: var(--btn-padding);
border: none;
border-radius: var(--btn-radius);
cursor: pointer;
transition: all 150ms ease;
}
.btn--primary {
background: var(--color-primary);
color: white;
}
.btn--primary:hover {
opacity: 0.9;
}
.btn--medium {
font-size: 16px;
}
@media (max-width: 768px) {
.btn { padding: 10px 16px; }
}
</style>44
Generate Tailwind Component
Convert Figma component to Tailwind utility classes.
Chat
CLI
Automation
Prompt #44 — Chat
Generate Tailwind component from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Convert styles to Tailwind utility classes 2. Extract to component template (if using framework) 3. Or generate pure HTML with Tailwind classes 4. Include responsive variants 5. Use Tailwind config tokens 6. Add custom configurations if needed 7. Include dark mode support (if applicable) 8. Document Tailwind setup 9. Provide both template and component versions 10. Production-ready Generate Tailwind-based component.
VARIATIONS
QUICKGenerate Tailwind HTML for '[COMPONENT_NAME]'.
COMPONENTGenerate Tailwind component (React/Vue): utility classes, responsive, dark mode support, Tailwind config.
FULLComplete Tailwind component from '[COMPONENT_NAME]'. Include: HTML with utility classes, responsive variants, dark mode, custom Tailwind config, component versions (React/Vue), documentation, copy-paste ready.
Expected Output
HTML or component code using Tailwind utility classes with responsive variants.
Example Output
<button class="px-6 py-3 bg-blue-500 text-white rounded-lg font-semibold hover:bg-blue-600 active:bg-blue-700 disabled:opacity-50 transition-colors"> Click me </button> <!-- Responsive variant --> <button class="px-3 py-2 sm:px-4 sm:py-2 md:px-6 md:py-3 bg-blue-500 hover:bg-blue-600"> Responsive Button </button> <!-- Dark mode --> <button class="bg-blue-500 dark:bg-blue-700 text-white dark:text-gray-100"> Dark mode supported </button>
45
Generate React Native Component
Convert Figma component to React Native code for mobile apps.
Chat
CLI
Automation
Prompt #45 — Chat
Generate React Native component from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create React Native (.tsx) component 2. Use React Native primitives (View, Text, Pressable) 3. Extract styling to StyleSheet 4. Define prop types with TypeScript 5. Include platform-specific styles (iOS/Android) 6. Handle touch/press states 7. Make responsive for different screen sizes 8. Add accessibility features 9. Include example usage 10. Production-ready code Generate React Native component.
VARIATIONS
QUICKGenerate React Native code for '[COMPONENT_NAME]'.
TYPESCRIPTGenerate React Native TSX with StyleSheet, platform styles, accessibility, responsive layout.
FULLComplete React Native component from '[COMPONENT_NAME]'. Include: TSX with TypeScript, StyleSheet styling, platform-specific styles (iOS/Android), responsive layout, accessibility, touch states, usage examples, production-ready.
Expected Output
React Native component with TypeScript, StyleSheet styling, and platform-specific variants.
Example Output
import React from 'react';
import {
View,
Text,
Pressable,
StyleSheet,
Platform,
GestureResponderEvent,
} from 'react-native';
interface ButtonProps {
label: string;
size?: 'small' | 'medium' | 'large';
onPress?: (event: GestureResponderEvent) => void;
}
export const Button: React.FC<ButtonProps> = ({
label,
size = 'medium',
onPress,
}) => {
return (
<Pressable
onPress={onPress}
style={({ pressed }) => [
styles.button,
styles[size],
pressed && styles.pressed,
]}
>
<Text style={styles.text}>{label}</Text>
</Pressable>
);
};
const styles = StyleSheet.create({
button: {
paddingHorizontal: 24,
paddingVertical: 12,
backgroundColor: '#2563EB',
borderRadius: Platform.OS === 'ios' ? 8 : 4,
alignItems: 'center',
},
medium: {
paddingVertical: 12,
},
pressed: {
opacity: 0.8,
},
text: {
color: 'white',
fontSize: 16,
fontWeight: '600',
},
});46
Generate Swift UI View
Convert Figma component to SwiftUI code for iOS apps.
Chat
CLI
Automation
Prompt #46 — Chat
Generate SwiftUI view from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create SwiftUI View struct 2. Use SwiftUI primitives (VStack, HStack, Button, etc.) 3. Apply extracted styling properties 4. Include state management (@State, @Binding) 5. Add iOS-specific interactions 6. Support light/dark mode 7. Make responsive for different device sizes 8. Add accessibility (accessibility labels) 9. Include preview for development 10. Production-ready code Generate SwiftUI component.
VARIATIONS
QUICKGenerate SwiftUI code for '[COMPONENT_NAME]'.
COMPLETEGenerate SwiftUI View with state, styling, dark mode, accessibility, preview.
PRODUCTIONComplete SwiftUI View from '[COMPONENT_NAME]'. Include: View struct with styling, state management (@State/@Binding), dark mode support, responsive layout, accessibility, preview provider, production-ready.
Expected Output
SwiftUI View code with styling, state management, dark mode support, and preview.
Example Output
import SwiftUI
struct PrimaryButton: View {
let label: String
let size: ButtonSize = .medium
var action: (() -> Void)? = nil
@Environment(\.colorScheme) var colorScheme
var body: some View {
Button(action: action ?? {}) {
Text(label)
.font(size.font)
.foregroundColor(.white)
.frame(height: size.height)
.frame(maxWidth: .infinity)
.background(Color.blue)
.cornerRadius(8)
}
.accessibilityLabel(label)
}
}
enum ButtonSize {
case small, medium, large
var font: Font {
switch self {
case .small: return .caption
case .medium: return .body
case .large: return .headline
}
}
var height: CGFloat {
switch self {
case .small: return 32
case .medium: return 48
case .large: return 56
}
}
}
#Preview {
PrimaryButton(label: "Click me", size: .medium)
}47
Generate Flutter Widget
Convert Figma component to Flutter Dart code for mobile apps.
Chat
CLI
Automation
Prompt #47 — Chat
Generate Flutter widget from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create Flutter StatelessWidget or StatefulWidget 2. Use Flutter primitives (GestureDetector, Container, etc.) 3. Apply extracted colors, sizes, and styling 4. Handle onPressed/onTap callbacks 5. Support platform variants (Material/Cupertino) 6. Make responsive for different screen sizes 7. Add animation/transition support 8. Include accessibility features 9. Provide unit test template 10. Production-ready Dart code Generate Flutter widget.
VARIATIONS
QUICKGenerate Flutter Dart code for '[COMPONENT_NAME]'.
COMPLETEGenerate Flutter Widget with styling, callbacks, Material/Cupertino support, animations, accessibility.
PRODUCTIONComplete Flutter Widget from '[COMPONENT_NAME]'. Include: Dart code with styling, onTap/onPressed, Material/Cupertino variants, responsive layout, animations, accessibility, unit test template, production-ready.
Expected Output
Flutter Dart widget code with styling, callbacks, and platform variants.
Example Output
import 'package:flutter/material.dart';
class PrimaryButton extends StatelessWidget {
final String label;
final VoidCallback onPressed;
final ButtonSize size;
const PrimaryButton({
required this.label,
required this.onPressed,
this.size = ButtonSize.medium,
});
@override
Widget build(BuildContext context) {
return ElevatedButton(
style: ElevatedButton.styleFrom(
backgroundColor: Colors.blue,
padding: size.padding,
shape: RoundedRectangleBorder(
borderRadius: BorderRadius.circular(8),
),
),
onPressed: onPressed,
child: Text(
label,
style: TextStyle(
fontSize: size.fontSize,
fontWeight: FontWeight.w600,
color: Colors.white,
),
),
);
}
}
enum ButtonSize {
small(padding: EdgeInsets.symmetric(horizontal: 16, vertical: 8), fontSize: 14),
medium(padding: EdgeInsets.symmetric(horizontal: 24, vertical: 12), fontSize: 16),
large(padding: EdgeInsets.symmetric(horizontal: 32, vertical: 16), fontSize: 18);
final EdgeInsets padding;
final double fontSize;
const ButtonSize({required this.padding, required this.fontSize});
}48
Responsive Layout Code
Generate code with responsive breakpoints matching Figma design specs.
Chat
CLI
Automation
Prompt #48 — Chat
Generate responsive layout from '[COMPONENT/PAGE_NAME]' in [FILE_KEY]: 1. Extract design at multiple breakpoints (mobile, tablet, desktop) 2. Generate code for all breakpoints 3. Use mobile-first approach 4. Generate CSS media queries or framework-specific responsive utilities 5. Document breakpoints and behavior changes 6. Include touch/click targets ≥ 44px for mobile 7. Test responsive images and aspect ratios 8. Include accessibility for responsive layouts 9. Provide responsive test cases 10. Generate in multiple frameworks (CSS/Tailwind/Bootstrap) Provide complete responsive implementation.
VARIATIONS
QUICKGenerate responsive CSS for '[COMPONENT_NAME]' at mobile/tablet/desktop sizes.
MULTI-FRAMEWORKGenerate responsive code: CSS media queries, Tailwind responsive classes, Bootstrap grid variants.
COMPLETEComplete responsive layout from '[COMPONENT_NAME]'. Include: breakpoints (mobile/tablet/desktop), mobile-first approach, media queries, responsive utilities, touch targets ≥44px, responsive images, accessibility, test cases, multiple frameworks (CSS/Tailwind/Bootstrap).
Expected Output
Responsive code with CSS media queries and multiple framework implementations.
Example Output
/* Mobile-first responsive design */
.container {
width: 100%;
padding: 16px;
font-size: 14px;
}
.grid {
display: grid;
grid-template-columns: 1fr;
gap: 16px;
}
/* Tablet (≥ 768px) */
@media (min-width: 768px) {
.container {
width: 90%;
padding: 24px;
font-size: 16px;
}
.grid {
grid-template-columns: repeat(2, 1fr);
gap: 24px;
}
}
/* Desktop (≥ 1024px) */
@media (min-width: 1024px) {
.container {
width: 1200px;
padding: 40px;
}
.grid {
grid-template-columns: repeat(3, 1fr);
}
}
/* Touch targets minimum 44x44px */
.button {
min-height: 44px;
min-width: 44px;
}49
Generate Storybook Stories
Create Storybook stories from Figma component variants.
Chat
CLI
Automation
Prompt #49 — Chat
Generate Storybook stories from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Create Component Story Format (CSF) file 2. Generate story for each variant 3. Create interactive controls (Storybook Controls) 4. Document prop variations 5. Include accessibility tests (a11y) 6. Add visual regression test setup 7. Include usage documentation 8. Create playground stories 9. Generate for Storybook 7+ (main/decorators) 10. Ready for CI/CD integration Generate production-ready Storybook stories.
VARIATIONS
QUICKGenerate Storybook stories for '[COMPONENT_NAME]'.
COMPLETEGenerate CSF stories with controls, a11y tests, visual regression setup, documentation.
FULLComplete Storybook stories from '[COMPONENT_NAME]'. Include: CSF v3 format, interactive controls, all variants, a11y tests, visual regression, documentation, playground, CI/CD integration, production-ready.
Expected Output
Storybook CSF file with stories, controls, and accessibility tests.
Example Output
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './Button';
const meta: Meta<typeof Button> = {
component: Button,
argTypes: {
label: { control: 'text' },
size: { control: 'select', options: ['small', 'medium', 'large'] },
disabled: { control: 'boolean' },
},
};
export default meta;
type Story = StoryObj<typeof meta>;
export const Primary: Story = {
args: {
label: 'Click me',
size: 'medium',
disabled: false,
},
};
export const Large: Story = {
args: {
...Primary.args,
size: 'large',
},
};
export const Disabled: Story = {
args: {
...Primary.args,
disabled: true,
},
};
export const AllSizes: Story = {
render: () => (
<div style={{ display: 'flex', gap: '10px' }}>
<Button label="Small" size="small" />
<Button label="Medium" size="medium" />
<Button label="Large" size="large" />
</div>
),
};50
Generate CSS Module
Create scoped CSS modules from Figma component styles.
Chat
CLI
Automation
Prompt #50 — Chat
Generate CSS Module from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Extract all styles into CSS module 2. Use BEM naming convention 3. Organize with variables for tokens 4. Include responsive variants 5. Add hover/active/focus/disabled states 6. Use CSS custom properties for theming 7. Include media queries for breakpoints 8. Add transitions and animations 9. Document class structure 10. Production-ready scoped CSS Generate CSS module file.
VARIATIONS
QUICKGenerate CSS module for '[COMPONENT_NAME]'.
COMPLETEGenerate CSS module: BEM naming, CSS variables, responsive design, all states, animations.
FULLComplete CSS module from '[COMPONENT_NAME]'. Include: BEM naming, CSS custom properties, responsive media queries, all states (hover/active/focus/disabled), animations/transitions, documentation, production-ready.
Expected Output
CSS Module file with BEM naming, variables, responsive design, and state variants.
Example Output
/* Button.module.css */
:root {
--color-primary: #2563EB;
--radius: 8px;
--transition: all 150ms ease;
}
.button {
display: inline-flex;
align-items: center;
justify-content: center;
border: none;
border-radius: var(--radius);
cursor: pointer;
transition: var(--transition);
font-weight: 600;
}
.button--primary {
background-color: var(--color-primary);
color: white;
}
.button--primary:hover {
background-color: #1d4ed8;
box-shadow: 0 4px 6px rgba(0, 0, 0, 0.1);
}
.button--primary:active {
transform: scale(0.98);
}
.button--primary:disabled {
opacity: 0.5;
cursor: not-allowed;
}
.button--medium {
padding: 12px 24px;
font-size: 16px;
}
@media (max-width: 768px) {
.button--medium {
padding: 10px 16px;
font-size: 14px;
}
}51
Extract SVG Icons
Export Figma icons as optimized SVG files.
Chat
CLI
Automation
Prompt #51 — Chat
Extract SVG icons from '[ICON_LIBRARY]' in [FILE_KEY]: 1. Find all icon components 2. Export each as individual SVG 3. Optimize SVG (remove unnecessary data) 4. Ensure consistent viewBox and sizing 5. Use currentColor for color inheritance 6. Generate icon sprite (if needed) 7. Create TypeScript icon component wrapper 8. Generate icon list with names 9. Include usage documentation 10. Package for distribution Provide optimized icon library.
VARIATIONS
QUICKExtract SVG files for all icons in '[ICON_LIBRARY]'.
OPTIMIZEDExtract icons as optimized SVGs: remove unnecessary data, consistent sizing, currentColor support, sprite generation.
COMPLETEComplete icon library extraction from '[ICON_LIBRARY]'. Include: individual optimized SVGs, consistent viewBox, currentColor support, sprite file, TypeScript icon component, icon list, documentation, distribution package.
Expected Output
Optimized SVG files with consistent sizing and TypeScript icon component.
Example Output
<!-- icon-check.svg -->
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" xmlns="http://www.w3.org/2000/svg">
<path d="M20 6L9 17l-5-5" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
</svg>
// Icon.tsx
import React from 'react';
interface IconProps {
name: 'check' | 'arrow' | 'close';
size?: number;
color?: string;
}
export const Icon: React.FC<IconProps> = ({ name, size = 24, color = 'currentColor' }) => {
return (
<svg
width={size}
height={size}
viewBox="0 0 24 24"
fill="none"
stroke={color}
strokeWidth="2"
>
{/* Icon paths would go here */}
</svg>
);
};52
Generate Animation CSS
Create CSS animations and transitions from Figma motion/interactions.
Chat
CLI
Automation
Prompt #52 — Chat
Generate animation CSS from '[COMPONENT_NAME]' interactions in [FILE_KEY]: 1. Extract animation/transition properties from Figma 2. Document animation durations and curves 3. Generate CSS keyframes for each animation 4. Create transition definitions 5. Include easing functions 6. Generate Framer Motion equivalents (if React) 7. Add reduced-motion support (accessibility) 8. Test performance (60fps targets) 9. Provide implementation guides 10. Production-ready animation code Provide animation library.
VARIATIONS
QUICKGenerate CSS animations for '[COMPONENT_NAME]' interactions.
COMPLETEGenerate CSS/Framer Motion: keyframes, transitions, easing, reduced-motion, performance optimized.
FULLComplete animation library from '[COMPONENT_NAME]'. Include: CSS keyframes, transition definitions, easing curves, Framer Motion equivalents, reduced-motion support, performance optimization (60fps), implementation guides, production-ready.
Expected Output
CSS animations with keyframes, transitions, and Framer Motion equivalents.
Example Output
/* CSS Animations */
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
.button {
animation: fadeIn 300ms ease-out;
transition: background-color 150ms ease, transform 100ms ease;
}
.button:hover {
background-color: #1d4ed8;
transform: translateY(-2px);
}
/* Reduce motion support */
@media (prefers-reduced-motion: reduce) {
.button {
animation: none;
transition: none;
}
}
// Framer Motion equivalent
import { motion } from 'framer-motion';
export const AnimatedButton = () => (
<motion.button
initial={{ opacity: 0 }}
animate={{ opacity: 1 }}
transition={{ duration: 0.3, ease: 'easeOut' }}
whileHover={{ backgroundColor: '#1d4ed8', y: -2 }}
/>
);53
Generate Accessible Component
Create fully accessible component with ARIA attributes and semantic HTML.
Chat
CLI
Automation
Prompt #53 — Chat
Generate accessible component from '[COMPONENT_NAME]' in [FILE_KEY]: 1. Use semantic HTML elements 2. Add ARIA labels and descriptions 3. Implement keyboard navigation (Tab, Arrow keys, Enter, Escape) 4. Ensure color contrast (WCAG AA/AAA) 5. Test with screen readers 6. Document accessibility features 7. Include focus management 8. Add role attributes where needed 9. Implement error handling and announcements 10. WCAG 2.1 Level AA compliant Provide fully accessible component.
VARIATIONS
QUICKGenerate accessible version of '[COMPONENT_NAME]'.
WCAGGenerate with semantic HTML, ARIA labels, keyboard nav, contrast checks, WCAG AA compliance.
FULLComplete accessible component from '[COMPONENT_NAME]'. Include: semantic HTML, ARIA attributes, keyboard navigation (all keys), color contrast compliance, screen reader testing, focus management, error announcements, WCAG 2.1 Level AA, documentation.
Expected Output
Accessible component code with ARIA attributes, semantic HTML, and keyboard support.
Example Output
// Accessible Button Component
<button
type="button"
aria-label="Submit form"
aria-disabled={isDisabled}
disabled={isDisabled}
className={`btn btn--primary ${isDisabled ? 'btn--disabled' : ''}`}
onClick={handleClick}
onKeyDown={handleKeyDown}
>
Submit
</button>
// Accessible Dialog
<div
role="dialog"
aria-modal="true"
aria-labelledby="dialog-title"
aria-describedby="dialog-desc"
>
<h2 id="dialog-title">Confirm Action</h2>
<p id="dialog-desc">Are you sure you want to proceed?</p>
<button aria-label="Confirm action">Yes</button>
<button aria-label="Cancel action">No</button>
</div>
/* Contrast ratio check */
/* Button text on primary background: 21:1 ✓ WCAG AAA */
/* Focus indicator: 2px solid border */
button:focus-visible {
outline: 2px solid #000;
outline-offset: 2px;
}54
Full Page Code Generation
Generate entire page layout and components as production-ready code.
Chat
CLI
Automation
Prompt #54 — Chat
Generate complete page code from '[PAGE_NAME]' in [FILE_KEY]: 1. Extract page layout and structure 2. Identify all components on page 3. Generate code for all sections 4. Create responsive layout 5. Integrate all design tokens 6. Connect component instances 7. Generate route/page component 8. Create responsive navigation 9. Include metadata and head tags 10. Fully functional HTML/React/Vue page Provide complete page implementation.
VARIATIONS
QUICKGenerate HTML code for '[PAGE_NAME]'.
REACTGenerate React page component: layout, all components, responsive design, routing setup.
FULLComplete page code from '[PAGE_NAME]'. Include: full layout, all components, responsive design, design tokens, routing, navigation, metadata, fully functional HTML/React/Vue, production-ready.
Expected Output
Complete page code with layout, components, responsive design, and routing.
Example Output
// pages/Home.tsx
import React from 'react';
import { Button } from '../components/Button';
import { Card } from '../components/Card';
export const HomePage: React.FC = () => {
return (
<main className="page page--home">
<section className="hero">
<h1>Welcome</h1>
<p>Get started with our product</p>
<Button label="Get Started" size="large" />
</section>
<section className="features">
<div className="grid">
<Card title="Feature 1" />
<Card title="Feature 2" />
<Card title="Feature 3" />
</div>
</section>
</main>
);
};
export default HomePage;6
Code to Figma
10 prompts
55
Push Component to Figma
Create Figma components from code.
Chat
CLI
Automation
Prompt #55 — Chat
Create Figma component from React component. Take the '[COMPONENT_NAME]' React component and: 1. Map component structure to Figma layers 2. Extract styles to Figma fills/strokes 3. Create component variants matching props 4. Set up component properties 5. Apply design tokens 6. Create in Figma file [FILE_KEY] 7. Configure auto-layout 8. Validate and test 9. Publish component 10. Document in Figma Provide Figma component from code.
VARIATIONS
QUICKCreate '[COMPONENT_NAME]' component in Figma from React code.
COMPLETECreate Figma component: structure mapping, styles extraction, variants setup, properties, tokens, auto-layout, publishing.
FULLComplete Figma component from '[COMPONENT_NAME]' React code. Include: structure mapping, styles extraction, variant setup, component properties, design tokens integration, auto-layout config, validation, publishing, documentation.
Expected Output
Figma component created from React source with variants and properties configured.
Example Output
Created Figma Component: Button/Primary ✓ Component structure created ✓ Styles applied (colors, typography) ✓ 12 variants configured (size × state × icon) ✓ Component properties set up ✓ Design tokens linked ✓ Auto-layout configured ✓ Published to library Location: [FILE_KEY] > Components > Button/Primary
56
Sync Design Tokens to Figma
Push token updates back to Figma.
Chat
CLI
Automation
Prompt #56 — Chat
Sync design tokens from code to [FILE_KEY]: 1. Read tokens from code/JSON 2. Map to Figma variables 3. Create/update color variables 4. Create/update typography variables 5. Create/update sizing variables 6. Validate token values 7. Update existing values 8. Add new tokens 9. Remove deprecated tokens 10. Sync complete Provide token synchronization.
VARIATIONS
QUICKSync tokens from tokens.json to Figma [FILE_KEY].
COMPLETESync tokens: colors, typography, sizing variables. Update existing, add new, remove deprecated.
FULLComplete token sync from code to [FILE_KEY]. Include: all token types (color/typography/sizing), variable mapping, create/update/remove, validation, change tracking, sync report.
Expected Output
Token synchronization report showing created, updated, and removed tokens.
Example Output
Token Sync Report: [FILE_KEY] ✓ Synced: 347 tokens ✓ New: 12 tokens ✓ Updated: 23 tokens ✓ Removed: 2 tokens ✓ Validation: PASSED Status: Complete
57
Update Text Content
Batch update copy/text in Figma.
Chat
CLI
Automation
Prompt #57 — Chat
Update text content in [FILE_KEY]: 1. Read new text from CSV/JSON 2. Find matching text nodes by path or pattern 3. Update text content 4. Preserve formatting/styling 5. Handle missing/extra text 6. Validate updates 7. Track changes 8. Provide rollback capability 9. Generate change report Provide text content update.
VARIATIONS
QUICKUpdate text in [FILE_KEY] from source.
DETAILEDBatch update text: CSV/JSON source, path matching, formatting preserved, validation, change tracking.
COMPLETEComplete text content update for [FILE_KEY]. Include: source parsing (CSV/JSON), node matching (path/pattern), formatting preservation, validation, change tracking, rollback capability, comprehensive report.
Expected Output
Text update report showing updated, skipped, and failed updates.
Example Output
Text Update Report: [FILE_KEY] ✓ Updated: 45 text nodes ⚠️ Skipped: 3 (no matching pattern) ✗ Failed: 0 Status: Complete
58
Create Figma Styles from CSS
Generate Figma styles from CSS code.
Chat
CLI
Automation
Prompt #58 — Chat
Create Figma styles from CSS in [FILE_KEY]: 1. Parse CSS file or code 2. Extract color styles 3. Extract typography styles 4. Extract effects (shadows) 5. Create Figma style components 6. Organize in groups 7. Name appropriately 8. Validate style matching 9. Publish styles 10. Update components Provide Figma styles from CSS.
VARIATIONS
QUICKGenerate Figma styles from CSS code.
COMPLETECreate Figma styles: colors, typography, effects. Organized, named, published.
FULLComplete Figma style generation from CSS. Include: all style types (color/typography/effects), parsing, organization, naming, validation, publishing, component updates.
Expected Output
Figma styles created from CSS with validation report.
Example Output
Styles Created: [FILE_KEY] ✓ Colors: 34 styles ✓ Typography: 12 styles ✓ Effects: 8 styles Total: 54 styles published Status: Complete
59
Generate Component Set
Create Figma component with all variants from code.
Chat
CLI
Automation
Prompt #59 — Chat
Create component set '[COMPONENT_NAME]' in [FILE_KEY]: 1. Generate main component 2. Create all variant combinations 3. Set component properties 4. Configure variants grid 5. Apply auto-layout 6. Style consistently 7. Document properties 8. Test all variants 9. Publish 10. Validate coverage Provide complete component set.
VARIATIONS
QUICKCreate '[COMPONENT_NAME]' variant set in Figma.
COMPLETEGenerate component set: main component, all variants, properties, auto-layout, testing, publishing.
FULLComplete component set for '[COMPONENT_NAME]'. Include: main component, all variant combinations, properties setup, auto-layout config, consistent styling, documentation, variant testing, publishing, coverage validation.
Expected Output
Component variant set created with all combinations and properties configured.
Example Output
Component Set Created: Button/Primary ✓ Variants: 12 total ✓ Properties: size, state, icon ✓ Auto-layout: configured ✓ Styles: applied ✓ Published: Yes Status: Ready for use
60
Update Layout Properties
Modify Figma auto-layout and layout settings.
Chat
CLI
Automation
Prompt #60 — Chat
Update layout for '[ELEMENT_NAME]' in [FILE_KEY]: 1. Read current layout 2. Update auto-layout settings 3. Adjust gaps/padding 4. Update alignment 5. Modify sizing behavior 6. Update constraints 7. Validate layout 8. Test responsiveness 9. Update affected instances 10. Validate all changes Provide layout updates.
VARIATIONS
QUICKUpdate auto-layout for '[ELEMENT_NAME]' in [FILE_KEY].
COMPLETEUpdate layout: auto-layout, gaps, padding, alignment, sizing, constraints, validation.
FULLComplete layout update for '[ELEMENT_NAME]'. Include: auto-layout modification, gaps/padding/alignment updates, sizing/constraints changes, responsiveness testing, instance updates, comprehensive validation.
Expected Output
Layout update report showing modified properties and affected elements.
Example Output
Layout Updates: [ELEMENT_NAME] ✓ Auto-layout: flex → grid ✓ Gap: 8px → 12px ✓ Padding: updated ✓ Affected instances: 23 Status: Complete
61
Batch Rename Layers
Systematically rename layers in bulk.
Chat
CLI
Automation
Prompt #61 — Chat
Batch rename layers in [FILE_KEY]: 1. Read rename rules (CSV/JSON) 2. Find matching layers (regex/pattern) 3. Apply rename rules 4. Validate no duplicates 5. Test renames 6. Provide preview 7. Execute renames 8. Generate report 9. Provide rollback option 10. Validation complete Provide batch rename operation.
VARIATIONS
QUICKBatch rename layers in [FILE_KEY] using rules.
COMPLETEBatch rename: rules parsing, pattern matching, validation, preview, execution, rollback.
FULLComplete batch rename for [FILE_KEY]. Include: rule parsing (CSV/JSON), pattern matching (regex), validation, preview, execution, report generation, rollback capability.
Expected Output
Batch rename report showing renamed, skipped, and failed layers.
Example Output
Batch Rename Report: [FILE_KEY] ✓ Renamed: 87 layers ⚠️ Skipped: 5 (duplicates) ✗ Failed: 0 Status: Complete
62
Create Figma Variables from JSON
Push design tokens as Figma variables.
Chat
CLI
Automation
Prompt #62 — Chat
Create Figma variables from JSON in [FILE_KEY]: 1. Read variables from JSON 2. Parse variable structure 3. Create color variables 4. Create number variables 5. Create string variables 6. Set variable values 7. Create variable groups 8. Link to styles 9. Validate all variables 10. Publish complete Provide Figma variables from JSON.
VARIATIONS
QUICKCreate Figma variables from variables.json.
COMPLETECreate variables: colors, numbers, strings. Grouped, linked, validated, published.
FULLComplete Figma variable creation from JSON. Include: all variable types, grouping, value setting, linking to styles, validation, publishing.
Expected Output
Figma variables created with groups and validation report.
Example Output
Variables Created: [FILE_KEY] ✓ Colors: 34 ✓ Numbers: 12 ✓ Strings: 8 Total: 54 variables Status: Published
63
Update Instance Overrides
Modify component instance overrides in bulk.
Chat
CLI
Automation
Prompt #63 — Chat
Update instance overrides in [FILE_KEY]: 1. Find instances of '[COMPONENT_NAME]' 2. Apply override rules 3. Update text overrides 4. Update color overrides 5. Update property values 6. Validate overrides 7. Test changes 8. Update all matching instances 9. Generate report Provide instance override updates.
VARIATIONS
QUICKUpdate '[COMPONENT_NAME]' instance overrides.
COMPLETEUpdate overrides: text, colors, properties. Validate, test, apply to all instances.
FULLComplete instance override update. Include: override rule parsing, text/color/property updates, validation, testing, batch application, comprehensive report.
Expected Output
Instance override update report showing modified instances.
Example Output
Instance Overrides Updated: [COMPONENT_NAME] ✓ Updated: 23 instances ✓ Overrides: text, color Status: Complete
64
Sync Icon Library
Push SVG icons to Figma library.
Chat
CLI
Automation
Prompt #64 — Chat
Sync SVG icons to [FILE_KEY]: 1. Read icons from directory 2. Process each SVG 3. Create icon components 4. Set consistent sizing 5. Apply colors/tokens 6. Organize in groups 7. Create variants if needed 8. Publish library 9. Generate documentation 10. Complete sync Provide icon library sync.
VARIATIONS
QUICKSync SVG icons to Figma [FILE_KEY].
COMPLETESync icons: process SVGs, create components, organize, publish, document.
FULLComplete icon library sync to [FILE_KEY]. Include: SVG processing, component creation, consistent sizing, organization, publishing, documentation generation.
Expected Output
Icon library sync report showing created, updated, and organized icons.
Example Output
Icon Library Synced: [FILE_KEY] ✓ Icons: 34 total ✓ Created: 12 new ✓ Updated: 8 existing ✓ Organized: 4 categories Status: Published
7
Pixel-Perfect QA
12 prompts
65
Visual Diff Report
Compare design vs. implementation for pixel-perfect accuracy.
Chat
CLI
Automation
Prompt #65 — Chat
Generate visual diff between design and code for '[COMPONENT_NAME]': 1. Take screenshots of both 2. Compare pixel-by-pixel 3. Identify visual differences 4. Measure dimensions 5. Check colors match 6. Verify spacing 7. Test states (hover, active, disabled) 8. Document issues 9. Assign severity levels 10. Generate report Provide visual diff report.
VARIATIONS
QUICKCompare design vs. code for '[COMPONENT_NAME]'.
DETAILEDVisual diff: dimensions, colors, spacing, states, issues identified, severity.
COMPLETEComplete visual diff: pixel-perfect comparison, all states, measurements, color verification, spacing validation, issue documentation, severity assignment, comprehensive report.
Expected Output
Visual diff report showing matches, mismatches, and severity levels.
Example Output
Visual Diff Report: '[COMPONENT_NAME]' ✓ Dimensions: PASS (160×48) ⚠️ Color: MISMATCH (#2563EB vs #3B82F6) ✓ Spacing: PASS ✗ Hover state: MISMATCH (shadow missing) Issues: 2 | Critical: 1 | Warning: 1
66
Spacing Audit
Verify all spacing matches design specs.
Chat
CLI
Automation
Prompt #66 — Chat
Audit spacing in '[COMPONENT_NAME]' against [FILE_KEY]: 1. Extract design spacing values 2. Measure code spacing 3. Compare measurements 4. Flag deviations 5. Test all spacing (padding, margin, gap) 6. Validate breakpoints 7. Check touch targets (≥44px) 8. Document mismatches 9. Generate fix recommendations Provide spacing audit.
VARIATIONS
QUICKAudit spacing in '[COMPONENT_NAME]'.
DETAILEDSpacing audit: design vs. code, all spacings, breakpoints, touch targets, mismatches flagged.
COMPLETEComplete spacing audit: extract design specs, measure code, compare all spacing types, breakpoints, touch targets, document mismatches, provide fix recommendations.
Expected Output
Spacing audit report showing matches and mismatches with measurements.
Example Output
Spacing Audit: '[COMPONENT_NAME]' ✓ Padding: 12px (matches) ⚠️ Gap: 8px (design) vs 6px (code) - MISMATCH ✓ Touch target: 48px (meets 44px minimum) Matches: 4/6 | Issues: 1
67
Typography Audit
Verify typography matches design specs.
Chat
CLI
Automation
Prompt #67 — Chat
Audit typography in '[COMPONENT_NAME]' vs [FILE_KEY]: 1. Extract design typography 2. Measure code typography 3. Check font family 4. Verify font size 5. Check font weight 6. Verify line height 7. Check letter spacing 8. Compare colors 9. Test readability 10. Document mismatches Provide typography audit.
VARIATIONS
QUICKAudit typography in '[COMPONENT_NAME]'.
DETAILEDTypography audit: font, size, weight, line-height, spacing, color, readability.
COMPLETEComplete typography audit: extract design specs, measure code, check all properties (font/size/weight/line-height/spacing), compare colors, test readability, document mismatches.
Expected Output
Typography audit report showing property matches and mismatches.
Example Output
Typography Audit: '[COMPONENT_NAME]' ✓ Font: Inter (matches) ✓ Size: 16px (matches) ⚠️ Weight: 600 (code) vs 500 (design) - MISMATCH ✓ Line-height: 1.6 (matches) Matches: 3/4 | Issues: 1
68
Color Accuracy Check
Verify all colors match design specs.
Chat
CLI
Automation
Prompt #68 — Chat
Check color accuracy in '[COMPONENT_NAME]' vs [FILE_KEY]: 1. Extract design colors 2. Measure code colors 3. Compare hex values 4. Allow tolerance (±5%) 5. Check all color states 6. Verify transparency/opacity 7. Test contrast ratios 8. Document mismatches 9. Flag accessibility issues Provide color accuracy report.
VARIATIONS
QUICKCheck colors in '[COMPONENT_NAME]'.
DETAILEDColor audit: design vs code, hex values, opacity, contrast ratios, accessibility.
COMPLETEComplete color audit: extract design colors, measure code, compare with tolerance, check all states, verify opacity, test contrast, document mismatches, flag accessibility issues.
Expected Output
Color accuracy report showing matches, mismatches, and contrast ratings.
Example Output
Color Audit: '[COMPONENT_NAME]' ✓ Primary: #2563EB (matches) ⚠️ Hover: #3B82F6 (code) vs #1d4ed8 (design) - MISMATCH ✓ Contrast: 4.8:1 (WCAG AA ✓) Matches: 3/4 | Issues: 1
69
Border Radius Consistency
Verify border radius values match specs.
Chat
CLI
Automation
Prompt #69 — Chat
Audit border radius in '[COMPONENT_NAME]' vs [FILE_KEY]: 1. Extract design radius values 2. Measure code radius 3. Compare measurements 4. Check consistency 5. Test all corners 6. Verify responsive variants 7. Document deviations Provide radius audit.
VARIATIONS
QUICKCheck border radius in '[COMPONENT_NAME]'.
DETAILEDBorder radius audit: design vs code, all corners, consistency, responsive variants.
COMPLETEComplete border radius audit: extract design specs, measure code, compare all corners, check consistency across variants, responsive validation, document deviations.
Expected Output
Border radius audit report showing matches and mismatches.
Example Output
Border Radius Audit: '[COMPONENT_NAME]' ✓ All corners: 8px (matches) Matches: 4/4 | Issues: 0 | Status: PASS
70
Shadow Comparison
Verify box shadows match design specs.
Chat
CLI
Automation
Prompt #70 — Chat
Compare shadows in '[COMPONENT_NAME]' vs [FILE_KEY]: 1. Extract design shadow values 2. Measure code shadows 3. Compare blur, spread, offset, color 4. Check all shadow states 5. Verify elevation levels 6. Test on different backgrounds 7. Document mismatches Provide shadow comparison.
VARIATIONS
QUICKCheck shadows in '[COMPONENT_NAME]'.
DETAILEDShadow audit: design vs code, blur/spread/offset/color, elevation levels, backgrounds.
COMPLETEComplete shadow audit: extract design specs, measure code shadows, compare all properties, check elevation consistency, test on backgrounds, document mismatches.
Expected Output
Shadow comparison report showing property matches and mismatches.
Example Output
Shadow Audit: '[COMPONENT_NAME]' ✓ Default: 0 4px 6px rgba(0,0,0,0.1) (matches) ⚠️ Hover: offset/blur mismatch Matches: 3/4 | Issues: 1
71
Responsive Breakpoint Check
Test layout at all design breakpoints.
Chat
CLI
Automation
Prompt #71 — Chat
Test responsive layout for '[COMPONENT_NAME]' at all breakpoints: 1. Identify design breakpoints 2. Test at each breakpoint 3. Compare design vs code 4. Check layout changes 5. Verify spacing adjustments 6. Test font size changes 7. Check image sizing 8. Validate touch targets 9. Document issues Provide breakpoint testing report.
VARIATIONS
QUICKTest '[COMPONENT_NAME]' at mobile/tablet/desktop.
DETAILEDTest all breakpoints: layouts, spacing, fonts, images, touch targets, design vs code comparison.
COMPLETEComplete responsive testing: all breakpoints (mobile/tablet/desktop), layout validation, spacing verification, typography checks, image sizing, touch target validation, comparison to design specs, comprehensive report.
Expected Output
Responsive breakpoint testing report showing layout matches at each breakpoint.
Example Output
Responsive Breakpoint Test: '[COMPONENT_NAME]' ✓ Mobile (320px): PASS ✓ Tablet (768px): PASS ⚠️ Desktop (1024px): Layout mismatch Breakpoints tested: 3 | Passed: 2 | Failed: 1
72
Icon Size Audit
Verify all icon dimensions match specs.
Chat
CLI
Automation
Prompt #72 — Chat
Audit icon sizes in [FILE_KEY]: 1. Extract design icon sizes 2. Measure code icons 3. Compare dimensions 4. Check consistency (same icon, different sizes) 5. Verify stroke widths 6. Test at different scales 7. Document mismatches Provide icon size audit.
VARIATIONS
QUICKCheck icon sizes in [FILE_KEY].
DETAILEDIcon audit: dimensions, consistency, stroke widths, scaling, mismatches.
COMPLETEComplete icon audit: extract design specs, measure code icons, compare dimensions, check consistency across variants, verify stroke widths, test scaling, document mismatches.
Expected Output
Icon size audit report showing dimension matches and consistency.
Example Output
Icon Audit: [FILE_KEY] ✓ Icon/Check 16px: PASS ✓ Icon/Check 24px: PASS ✓ Icon/Check 32px: PASS Icons tested: 34 | Passed: 34 | Failed: 0
73
Alignment Grid Check
Verify elements align to design grid.
Chat
CLI
Automation
Prompt #73 — Chat
Check grid alignment in [FILE_KEY]: 1. Extract grid definition from design 2. Test element alignment 3. Check major elements 4. Verify gutter alignment 5. Test column alignment 6. Document misalignments Provide grid alignment report.
VARIATIONS
QUICKCheck grid alignment in [FILE_KEY].
DETAILEDGrid audit: grid definition, element alignment, gutters, columns, misalignments.
COMPLETEComplete grid audit: extract grid definition, test all element alignment, verify gutters/columns, document misalignments, provide alignment recommendations.
Expected Output
Grid alignment report showing aligned and misaligned elements.
Example Output
Grid Alignment Check: [FILE_KEY] ✓ Elements aligned: 89% ⚠️ Misaligned: 3 elements Recommendation: Realign 3 elements to 8px grid
74
Touch Target Audit
Verify all interactive elements meet 44×44px minimum.
Chat
CLI
Automation
Prompt #74 — Chat
Audit touch targets in '[COMPONENT_NAME]': 1. Find all interactive elements 2. Measure touch targets 3. Verify ≥44px (WCAG standard) 4. Document small targets 5. Suggest spacing adjustments Provide touch target audit.
VARIATIONS
QUICKCheck touch targets in '[COMPONENT_NAME]'.
DETAILEDTouch target audit: all interactive elements, measurements, WCAG compliance, suggestions.
COMPLETEComplete touch target audit: identify all interactive elements, measure touch targets, verify WCAG 44×44px compliance, document small targets, suggest spacing adjustments, comprehensive report.
Expected Output
Touch target audit report showing compliant and non-compliant targets.
Example Output
Touch Target Audit: '[COMPONENT_NAME]' ✓ Compliant: 12/12 (100%) ✓ All targets ≥44×44px Status: PASS
75
Contrast Ratio Check
Verify WCAG contrast compliance for all text.
Chat
CLI
Automation
Prompt #75 — Chat
Check contrast ratios in '[COMPONENT_NAME]': 1. Identify all text elements 2. Measure contrast ratios 3. Check against WCAG AA (4.5:1) 4. Check against WCAG AAA (7:1) 5. Document failures 6. Suggest fixes Provide contrast audit.
VARIATIONS
QUICKCheck contrast in '[COMPONENT_NAME]'.
DETAILEDContrast audit: all text, WCAG AA/AAA compliance, failures, suggestions.
COMPLETEComplete contrast audit: all text elements, measure ratios, check WCAG AA/AAA compliance, document failures, suggest color adjustments, comprehensive report.
Expected Output
Contrast audit report showing WCAG AA/AAA compliance levels.
Example Output
Contrast Audit: '[COMPONENT_NAME]' ✓ WCAG AA: 12/12 (100%) ✓ WCAG AAA: 10/12 (83%) ⚠️ 2 elements need darker text Recommendation: Adjust colors for AAA compliance
76
Full QA Checklist
Run comprehensive QA checks on component or page.
Chat
CLI
Automation
Prompt #76 — Chat
Run full QA checklist for '[COMPONENT_NAME]' in [FILE_KEY]: 1. Visual diff 2. Spacing audit 3. Typography check 4. Color accuracy 5. Border radius check 6. Shadow comparison 7. Responsive testing 8. Icon sizing 9. Grid alignment 10. Touch targets 11. Contrast ratios 12. Accessibility scan 13. Generate comprehensive report Provide complete QA report.
VARIATIONS
QUICKRun QA checklist for '[COMPONENT_NAME]'.
DETAILEDFull QA: visual, spacing, typography, colors, radius, shadows, responsive, icons, grid, touch, contrast, accessibility.
COMPLETEComplete QA checklist for '[COMPONENT_NAME]'. Include: all 12 checks (visual/spacing/typography/colors/radius/shadows/responsive/icons/grid/touch/contrast/accessibility), detailed report, issue severity, recommendations.
Expected Output
Comprehensive QA report with all checks and overall compliance score.
Example Output
Full QA Report: '[COMPONENT_NAME]' ✓ Visual: PASS ✓ Spacing: PASS ⚠️ Typography: 1 issue ✓ Colors: PASS ✓ Radius: PASS ✓ Shadows: PASS ✓ Responsive: PASS ✓ Icons: PASS ✓ Grid: PASS ✓ Touch targets: PASS ✓ Contrast: PASS ✓ Accessibility: PASS Overall Score: 92% (Very Good) Critical Issues: 0 Warnings: 1
8
Design System Documentation
10 prompts
77
Generate Component Catalog
Create complete component documentation.
Chat
CLI
Automation
Prompt #77 — Chat
Generate component catalog from [FILE_KEY]: 1. List all components 2. Create documentation page for each 3. Include visual examples 4. Document props 5. Show usage code 6. Add do's/don'ts 7. Accessibility notes 8. Related components 9. Export as HTML/Markdown 10. Publish to Storybook Provide complete component catalog.
VARIATIONS
QUICKGenerate catalog from [FILE_KEY].
HTMLGenerate HTML catalog: all components, documentation, examples, code.
COMPLETEComplete catalog: all components with full documentation, visual examples, prop tables, usage code, do's/don'ts, accessibility, related components, HTML/Markdown/Storybook exports.
Expected Output
Component catalog with documentation for all components.
Example Output
Component Catalog Generated ✓ Components: 47 ✓ Pages: 47 (one per component) ✓ Examples: 234 (all variants) ✓ Code snippets: 47 Status: Published to Storybook
78
Create Color Documentation
Document color palette usage.
Chat
CLI
Automation
Prompt #78 — Chat
Create color documentation from [FILE_KEY]: 1. Extract color palette 2. Document color meanings 3. Show usage examples 4. Include accessibility ratings 5. Provide color combinations 6. Create color swatches 7. Document color updates 8. Export as visual guide Provide color guide.
VARIATIONS
QUICKCreate color guide from [FILE_KEY].
COMPLETEColor documentation: palette, meanings, usage, accessibility, combinations, swatches, guide.
FULLComplete color documentation from [FILE_KEY]. Include: palette, semantic meanings, usage examples, accessibility ratings, color combinations, visual swatches, update history, exportable guide.
Expected Output
Color documentation with swatches and usage examples.
Example Output
Color Documentation ✓ Colors: 34 total ✓ Swatches: generated ✓ Usage examples: 34 ✓ Accessibility: WCAG AA compliant Status: Published
79
Create Typography Guide
Document typography system.
Chat
CLI
Automation
Prompt #79 — Chat
Create typography guide from [FILE_KEY]: 1. Extract typography scale 2. Show font specimens 3. Document sizing 4. Show line heights 5. Example usage 6. Accessibility notes 7. Web font setup 8. Create visual guide Provide typography guide.
VARIATIONS
QUICKCreate typography guide from [FILE_KEY].
COMPLETETypography guide: scale, specimens, sizing, line heights, usage, accessibility, fonts.
FULLComplete typography guide from [FILE_KEY]. Include: scale with specimens, sizing documentation, line height ratios, usage examples, accessibility notes, web font setup, visual guide, exportable PDF.
Expected Output
Typography guide with specimens and usage examples.
Example Output
Typography Guide ✓ Font families: 3 ✓ Sizes: 12 variants ✓ Specimens: generated ✓ Usage examples: complete Status: Published
80
Generate Spacing Reference
Document spacing system.
Chat
CLI
Automation
Prompt #80 — Chat
Create spacing reference from [FILE_KEY]: 1. Extract spacing scale 2. Show measurements 3. Document use cases 4. Create visual examples 5. Include code examples 6. Responsive variants 7. Best practices 8. Export reference Provide spacing reference.
VARIATIONS
QUICKCreate spacing reference from [FILE_KEY].
COMPLETESpacing reference: scale, measurements, use cases, visuals, code, responsive, best practices.
FULLComplete spacing reference from [FILE_KEY]. Include: scale with measurements, use cases per value, visual examples, code snippets, responsive variants, best practices, comprehensive guide.
Expected Output
Spacing reference with measurements and use cases.
Example Output
Spacing Reference ✓ Scale: 7 levels (4px-64px) ✓ Use cases: documented ✓ Visuals: generated ✓ Code examples: complete Status: Published
81
Create Icon Reference Sheet
Document icon library.
Chat
CLI
Automation
Prompt #81 — Chat
Create icon reference from [FILE_KEY]: 1. List all icons 2. Show icon grid 3. Name each icon 4. Usage examples 5. Size variants 6. Color variants 7. Download options 8. Create visual sheet Provide icon reference.
VARIATIONS
QUICKCreate icon reference from [FILE_KEY].
VISUALIcon grid: all icons, names, sizes, colors, usage, download.
COMPLETEComplete icon reference from [FILE_KEY]. Include: icon grid with names, all sizes/colors shown, usage examples, download options (SVG/PNG), naming conventions, searchable reference, PDF export.
Expected Output
Icon reference sheet with grid and naming.
Example Output
Icon Reference ✓ Icons: 34 total ✓ Grid: generated ✓ Sizes: 3 variants each ✓ Colors: 5 variants each Status: Published
82
Document Component API
Create API documentation for components.
Chat
CLI
Automation
Prompt #82 — Chat
Create API docs for '[COMPONENT_NAME]': 1. Document all props 2. Show prop types 3. Default values 4. Code examples 5. Prop descriptions 6. Type definitions (TypeScript) 7. Usage patterns 8. Common mistakes Provide API documentation.
VARIATIONS
QUICKDocument API for '[COMPONENT_NAME]'.
TYPESCRIPTAPI docs: props, types, defaults, examples, TypeScript definitions.
COMPLETEComplete API documentation for '[COMPONENT_NAME]'. Include: all props with types/defaults/descriptions, TypeScript definitions, code examples, usage patterns, common pitfalls, troubleshooting, comprehensive guide.
Expected Output
API documentation with prop table and examples.
Example Output
API Documentation: Button ✓ Props: 5 documented ✓ Types: TypeScript definitions ✓ Examples: 8 code samples ✓ Patterns: 5 common uses Status: Published
83
Generate Style Guide Page
Create visual style guide document.
Chat
CLI
Automation
Prompt #83 — Chat
Generate style guide from [FILE_KEY]: 1. Extract all styles 2. Create visual pages 3. Colors section 4. Typography section 5. Spacing section 6. Components section 7. Pattern library 8. Export as PDF/HTML Provide style guide.
VARIATIONS
QUICKGenerate style guide from [FILE_KEY].
VISUALStyle guide: colors, typography, spacing, components, patterns, visual.
COMPLETEComplete style guide from [FILE_KEY]. Include: all design systems (colors/typography/spacing), components with examples, patterns, usage guidelines, design principles, visual style, PDF/HTML export, comprehensive guide.
Expected Output
Style guide document with all design system elements.
Example Output
Style Guide ✓ Pages: 12 total ✓ Sections: colors, type, spacing, components, patterns ✓ Examples: 234 total Status: Published as PDF
84
Create Pattern Library
Document reusable UI patterns.
Chat
CLI
Automation
Prompt #84 — Chat
Create pattern library from [FILE_KEY]: 1. Identify all patterns 2. Document each pattern 3. Show examples 4. Provide code 5. Usage guidelines 6. Variations 7. Accessibility notes 8. Export library Provide pattern library.
VARIATIONS
QUICKCreate pattern library from [FILE_KEY].
COMPLETEPattern library: all patterns, examples, code, guidelines, variations, accessibility.
FULLComplete pattern library from [FILE_KEY]. Include: all patterns with examples, code implementations, usage guidelines, variations, accessibility, best practices, comprehensive library reference.
Expected Output
Pattern library with documentation and examples.
Example Output
Pattern Library ✓ Patterns: 15 total ✓ Examples: per pattern ✓ Code: provided ✓ Guidelines: documented Status: Published
85
Generate Changelog
Document design system changes.
Chat
CLI
Automation
Prompt #85 — Chat
Generate changelog from [FILE_KEY]: 1. Extract version history 2. Document changes per version 3. Highlight breaking changes 4. Show new features 5. Bug fixes 6. Improvements 7. Deprecations 8. Migration guides Provide changelog.
VARIATIONS
QUICKGenerate changelog from [FILE_KEY].
DETAILEDChangelog: versions, changes, breaking changes, new features, fixes, deprecations.
COMPLETEComplete changelog from [FILE_KEY]. Include: all versions with detailed changes, breaking changes highlighted, new features listed, bug fixes, deprecations, migration guides, comprehensive history.
Expected Output
Changelog documenting all version changes.
Example Output
Changelog ✓ Versions: 12 total ✓ Changes: documented ✓ Breaking changes: 3 ✓ New features: 8 Status: Published
86
Create Onboarding Guide
Create guide for design system adoption.
Chat
CLI
Automation
Prompt #86 — Chat
Create onboarding guide from [FILE_KEY]: 1. Getting started steps 2. Setup instructions 3. How to use components 4. Best practices 5. Common tasks 6. Troubleshooting 7. Resources 8. FAQ Provide onboarding guide.
VARIATIONS
QUICKCreate onboarding guide for [FILE_KEY].
COMPLETEOnboarding guide: getting started, setup, usage, best practices, troubleshooting, FAQ.
FULLComplete onboarding guide for [FILE_KEY]. Include: step-by-step getting started, setup instructions, component usage, best practices, common workflows, troubleshooting, resources, FAQ, comprehensive guide.
Expected Output
Onboarding guide with setup and usage steps.
Example Output
Onboarding Guide ✓ Sections: 8 ✓ Steps: 24 total ✓ Examples: 15 ✓ FAQ: 12 items Status: Published
9
Batch Operations
8 prompts
87
Batch Export Components
Export multiple components as code.
Chat
CLI
Automation
Prompt #87 — Chat
Batch export components from [FILE_KEY]: 1. Select components 2. Generate code for all 3. Create separate files 4. Organize by component 5. Include documentation 6. Create index file 7. Package for export 8. Generate manifest Provide batch export.
VARIATIONS
QUICKExport all components from [FILE_KEY] as code.
COMPLETEBatch export: all components, code generation, organized files, documentation, index.
FULLComplete batch export from [FILE_KEY]. Include: all components as separate files, code generation, organization, documentation per component, index/manifest, packaged export, ready for distribution.
Expected Output
Batch export package with all components and documentation.
Example Output
Batch Export ✓ Components: 47 ✓ Files: 47 generated ✓ Documentation: included ✓ Index: created Status: Ready for download
88
Batch Extract All Tokens
Export all design tokens at once.
Chat
CLI
Automation
Prompt #88 — Chat
Extract all tokens from [FILE_KEY]: 1. Extract colors 2. Extract typography 3. Extract spacing 4. Extract shadows 5. Extract all tokens 6. Generate all formats 7. Package tokens 8. Create manifest Provide token batch export.
VARIATIONS
QUICKExtract all tokens from [FILE_KEY].
COMPLETEBatch extract: colors, typography, spacing, shadows, all formats (JSON/CSS/JS).
FULLComplete token batch extraction from [FILE_KEY]. Include: all token types, multiple format exports (JSON/CSS/SCSS/JS/Tailwind), organized package, manifest, ready for distribution.
Expected Output
Complete token package with all formats.
Example Output
Token Batch Export ✓ Colors: 34 ✓ Typography: 12 ✓ Spacing: 7 ✓ Shadows: 8 ✓ Formats: 5 (JSON/CSS/SCSS/JS/Tailwind) Status: Ready
89
Batch Generate Documentation
Generate all documentation at once.
Chat
CLI
Automation
Prompt #89 — Chat
Generate all documentation from [FILE_KEY]: 1. Component docs 2. API docs 3. Token docs 4. Style guide 5. Pattern library 6. Changelog 7. Onboarding 8. Package docs Provide documentation batch generation.
VARIATIONS
QUICKGenerate all documentation from [FILE_KEY].
COMPLETEBatch generate: component docs, API, tokens, styles, patterns, changelog, onboarding.
FULLComplete documentation batch generation from [FILE_KEY]. Include: all documentation types (components/API/tokens/styles/patterns/changelog/onboarding), organized, HTML/Markdown exports, complete package, ready to publish.
Expected Output
Complete documentation package with all guides.
Example Output
Documentation Batch ✓ Components: 47 docs ✓ API: documented ✓ Tokens: documented ✓ Style guide: generated ✓ Patterns: 15 documented Status: Complete
90
Mass Layer Rename
Rename many layers using regex patterns.
Chat
CLI
Automation
Prompt #90 — Chat
Mass rename layers in [FILE_KEY]: 1. Create rename rules 2. Apply regex patterns 3. Preview changes 4. Execute renames 5. Verify results 6. Generate report Provide mass rename operation.
VARIATIONS
QUICKMass rename layers in [FILE_KEY] using pattern.
COMPLETEMass rename: rules creation, regex patterns, preview, execution, verification, report.
FULLComplete mass rename operation for [FILE_KEY]. Include: rule parsing, regex pattern support, comprehensive preview, safe execution, verification, detailed report, rollback capability.
Expected Output
Mass rename report showing completed renames.
Example Output
Mass Rename Report ✓ Renamed: 156 layers ⚠️ Skipped: 8 (duplicates) ✗ Failed: 0 Status: Complete
91
Batch Image Export
Export all images at once.
Chat
CLI
Automation
Prompt #91 — Chat
Batch export images from [FILE_KEY]: 1. Find all images 2. Export each image 3. Optimize images 4. Organize by folder 5. Generate manifest 6. Create index Provide batch image export.
VARIATIONS
QUICKExport all images from [FILE_KEY].
OPTIMIZEDBatch export: all images, optimized, organized, manifest, index.
COMPLETEComplete batch image export from [FILE_KEY]. Include: all images extracted, optimization, organized folders, manifest file, index/catalog, ready for distribution.
Expected Output
Batch image export with manifest and organization.
Example Output
Image Batch Export ✓ Images: 34 ✓ Optimized: 34/34 ✓ Folders: organized ✓ Manifest: created Status: Complete
92
Batch Style Update
Update multiple styles at once.
Chat
CLI
Automation
Prompt #92 — Chat
Batch update styles in [FILE_KEY]: 1. Define changes 2. Apply to styles 3. Update all components 4. Validate changes 5. Preview all 6. Execute update Provide batch style update.
VARIATIONS
QUICKUpdate styles in [FILE_KEY] in batch.
COMPLETEBatch update: define changes, apply to styles, update components, validate, preview, execute.
FULLComplete batch style update for [FILE_KEY]. Include: change definition, multi-style application, component updates, comprehensive validation, preview all changes, safe execution, rollback capability.
Expected Output
Batch style update report showing changes applied.
Example Output
Batch Style Update ✓ Styles updated: 23 ✓ Components affected: 134 ✓ Validation: passed Status: Complete
93
Batch Component Audit
Audit all components at once.
Chat
CLI
Automation
Prompt #93 — Chat
Audit all components in [FILE_KEY]: 1. Check all components 2. Assess variants 3. Check usage 4. Validate naming 5. Find unused 6. Detect issues 7. Generate report Provide component batch audit.
VARIATIONS
QUICKAudit all components in [FILE_KEY].
COMPLETEBatch audit: variants, usage, naming, unused, issues, comprehensive report.
FULLComplete batch audit of all components in [FILE_KEY]. Include: variant validation, usage analysis, naming convention checks, unused component detection, issue detection, severity assessment, comprehensive report, recommendations.
Expected Output
Batch component audit report with issues and recommendations.
Example Output
Component Batch Audit ✓ Components: 47 ✓ Issues found: 12 ✓ Unused: 3 ✓ Naming violations: 5 Status: Complete
94
Batch Accessibility Scan
Scan entire file for accessibility issues.
Chat
CLI
Automation
Prompt #94 — Chat
Scan [FILE_KEY] for accessibility issues: 1. Check contrast ratios 2. Check touch targets 3. Check text labels 4. Check structure 5. Find issues 6. Assign severity 7. Generate report Provide accessibility scan.
VARIATIONS
QUICKScan [FILE_KEY] for accessibility issues.
COMPLETEBatch scan: contrast, touch targets, labels, structure, issues, severity, report.
FULLComplete accessibility scan of [FILE_KEY]. Include: contrast ratio checks, touch target validation, text label verification, structure assessment, all issues identified, severity levels, detailed report, remediation recommendations.
Expected Output
Accessibility scan report with issues and severity levels.
Example Output
Accessibility Scan ✓ Elements scanned: 847 ⚠️ Issues found: 12 ✗ Critical: 2 (contrast) ⚠️ Warnings: 10 Status: Complete
10
Collaboration & Workflow
8 prompts
95
Design Handoff Summary
Create handoff document for developers.
Chat
CLI
Automation
Prompt #95 — Chat
Create handoff summary from [FILE_KEY]: 1. List all components 2. Document specs 3. Export assets 4. Create code snippets 5. Document behaviors 6. Design guidelines 7. Checklist Provide handoff document.
VARIATIONS
QUICKCreate handoff summary from [FILE_KEY].
COMPLETEHandoff: components, specs, assets, code, behaviors, guidelines.
FULLComplete handoff document from [FILE_KEY]. Include: all components with specs, asset exports, code snippets, interaction documentation, design guidelines, implementation checklist, ready for developer handoff.
Expected Output
Handoff document ready for developer implementation.
Example Output
Design Handoff ✓ Components: 47 ✓ Assets: exported ✓ Code: provided ✓ Specs: documented Status: Ready for handoff
96
Sprint Component List
List components needed for current sprint.
Chat
CLI
Automation
Prompt #96 — Chat
Generate sprint component list for [FILE_KEY]: 1. Review current sprint 2. Identify components needed 3. List dependencies 4. Check status 5. Prioritize 6. Create checklist Provide sprint list.
VARIATIONS
QUICKList components needed for sprint from [FILE_KEY].
COMPLETESprint list: needed components, dependencies, status, priority.
FULLComplete sprint component list from [FILE_KEY]. Include: components needed, dependencies identified, current status, prioritization, implementation checklist, timeline, ready for sprint planning.
Expected Output
Sprint component list with priorities and dependencies.
Example Output
Sprint Components ✓ Needed: 12 components ✓ Dependencies: mapped ✓ Status: 8 ready, 4 in progress ✓ Priority: assigned
97
Code Review Checklist
Create checklist for design system compliance review.
Chat
CLI
Automation
Prompt #97 — Chat
Generate code review checklist for [FILE_KEY]: 1. Design compliance 2. Token usage 3. Component usage 4. Accessibility 5. Responsive design 6. Performance 7. Documentation 8. Tests Provide review checklist.
VARIATIONS
QUICKCreate code review checklist from [FILE_KEY].
COMPLETEReview checklist: design compliance, tokens, components, accessibility, responsive, performance, docs, tests.
FULLComplete code review checklist from [FILE_KEY]. Include: design compliance checks, token usage verification, component usage validation, accessibility requirements, responsive design checks, performance guidelines, documentation review, test requirements.
Expected Output
Code review checklist with design system compliance items.
Example Output
Review Checklist ✓ Items: 24 total ✓ Categories: 8 ✓ Checkboxes: ready Status: Ready to use
98
Designer-Developer Sync
Create alignment summary between design and development.
Chat
CLI
Automation
Prompt #98 — Chat
Create design-dev sync summary for [FILE_KEY]: 1. Current state (design) 2. Current state (code) 3. Identify gaps 4. Sync plan 5. Timeline 6. Action items 7. Ownership Provide sync summary.
VARIATIONS
QUICKCreate design-dev sync for [FILE_KEY].
DETAILEDSync: design state, code state, gaps, plan, timeline, actions.
COMPLETEComplete design-dev alignment summary for [FILE_KEY]. Include: current state both sides, gap identification, synchronization plan, timeline, action items, ownership assignment, next steps.
Expected Output
Design-dev sync summary with alignment plan.
Example Output
Sync Summary ✓ Design: 100% complete ✓ Code: 75% implemented ✓ Gaps: 8 components ✓ Plan: Alignment in 2 weeks
99
PR Description Generator
Generate PR description from Figma changes.
Chat
CLI
Automation
Prompt #99 — Chat
Generate PR description for [FILE_KEY]: 1. Changed components 2. What changed 3. Why changed 4. Impact 5. Testing 6. Breaking changes 7. Screenshots Provide PR description.
VARIATIONS
QUICKGenerate PR description from [FILE_KEY].
COMPLETEPR description: changes, impacts, testing, breaking changes, screenshots.
FULLComplete PR description generation from [FILE_KEY]. Include: changed components listed, detailed change descriptions, reasoning, impact analysis, testing guidance, breaking change warnings, before/after screenshots, ready to paste.
Expected Output
PR description ready for GitHub/GitLab.
Example Output
PR Description ✓ Changes: 12 components ✓ Description: detailed ✓ Testing: documented ✓ Screenshots: included Status: Ready to post
100
Release Notes Generator
Generate release notes from design system changes.
Chat
CLI
Automation
Prompt #100 — Chat
Generate release notes from [FILE_KEY]: 1. Versions 2. New features 3. Improvements 4. Breaking changes 5. Bug fixes 6. Deprecations 7. Migration guide Provide release notes.
VARIATIONS
QUICKGenerate release notes from [FILE_KEY].
COMPLETERelease notes: features, improvements, breaking changes, fixes, deprecations, migration.
FULLComplete release notes from [FILE_KEY]. Include: version history, new features, improvements, breaking changes highlighted, bug fixes, deprecations, migration guides, ready to publish.
Expected Output
Release notes document ready for publication.
Example Output
Release Notes ✓ Version: 2.4.0 ✓ New features: 8 ✓ Improvements: 5 ✓ Breaking changes: 1 Status: Ready to publish
101
Stakeholder Presentation
Create presentation summary of design progress.
Chat
CLI
Automation
Prompt #101 — Chat
Create stakeholder presentation from [FILE_KEY]: 1. Progress summary 2. Completed items 3. In progress 4. Upcoming 5. Metrics 6. Timeline 7. Blockers 8. Next steps Provide presentation summary.
VARIATIONS
QUICKCreate presentation summary from [FILE_KEY].
COMPLETEPresentation: progress, completed, in-progress, upcoming, metrics, timeline, blockers.
FULLComplete stakeholder presentation summary from [FILE_KEY]. Include: progress overview, completed/in-progress/upcoming items, key metrics, timeline, blockers/risks, next steps, ready for presentation.
Expected Output
Presentation summary ready for stakeholder review.
Example Output
Presentation ✓ Progress: 78% ✓ Completed: 45 items ✓ In-progress: 12 items ✓ Timeline: on track Status: Ready
102
Component Status Tracker
Track component build status (design vs code).
Chat
CLI
Automation
Prompt #102 — Chat
Create component status tracker for [FILE_KEY]: 1. List all components 2. Design status 3. Code status 4. Testing status 5. Documentation status 6. Overall progress 7. Timeline Provide status tracker.
VARIATIONS
QUICKCreate status tracker from [FILE_KEY].
DETAILEDTracker: components, design/code/test/doc status, progress, timeline.
COMPLETEComplete component status tracker for [FILE_KEY]. Include: all components, design status, code implementation status, testing status, documentation status, overall progress percentage, timeline, owner assignment.
Expected Output
Component status tracker with progress visualization.
Example Output
Status Tracker ✓ Components: 47 ✓ Designed: 47/47 (100%) ✓ Coded: 35/47 (74%) ✓ Tested: 30/47 (64%) ✓ Documented: 25/47 (53%) Overall: 72% complete
11
Advanced & Automation
6 prompts
103
CI/CD Token Sync Pipeline
Set up automated token synchronization.
Chat
CLI
Automation
Prompt #103 — Chat
Set up token sync CI/CD pipeline for [FILE_KEY]: 1. Extract tokens from Figma 2. Generate token files 3. Commit to repository 4. Run validation 5. Deploy to package registry 6. Notify team 7. Schedule automation Provide pipeline setup.
VARIATIONS
QUICKSet up token sync pipeline from [FILE_KEY].
COMPLETEPipeline: token extraction, generation, commit, validation, deploy, notification.
FULLComplete CI/CD token sync pipeline for [FILE_KEY]. Include: automated token extraction, file generation, git commit, validation checks, package registry deployment, team notifications, scheduled triggers, ready to deploy.
Expected Output
CI/CD pipeline configured for automated token sync.
Example Output
Token Sync Pipeline ✓ Trigger: Daily at 9am ✓ Extract: automated ✓ Generate: automated ✓ Validate: automated ✓ Deploy: automated Status: Active
104
Figma Webhook Listener
Set up webhooks to detect Figma changes.
Chat
CLI
Automation
Prompt #104 — Chat
Set up Figma webhook listener for [FILE_KEY]: 1. Create webhook endpoint 2. Configure events 3. Handle file changes 4. Trigger updates 5. Log events 6. Error handling 7. Test setup Provide webhook setup.
VARIATIONS
QUICKSet up webhook listener for [FILE_KEY].
COMPLETEWebhook: endpoint, events, change handling, triggers, logging, errors.
FULLComplete Figma webhook listener setup for [FILE_KEY]. Include: webhook endpoint creation, event configuration, change detection, automated trigger actions, event logging, error handling, testing, ready for production.
Expected Output
Webhook listener configured and tested.
Example Output
Webhook Listener ✓ Endpoint: configured ✓ Events: all file changes ✓ Status: active ✓ Last event: 5min ago Status: Monitoring
105
Custom Lint Rules
Create linting rules for design system compliance.
Chat
CLI
Automation
Prompt #105 — Chat
Create custom lint rules for [FILE_KEY]: 1. Define rule violations 2. Create rules 3. Test rules 4. Document rules 5. Integrate with CI 6. Generate reports Provide custom lint rules.
VARIATIONS
QUICKCreate lint rules from [FILE_KEY].
COMPLETELint rules: violations, rules, tests, documentation, integration, reports.
FULLComplete custom lint rules for [FILE_KEY]. Include: rule definitions, violation detection, comprehensive testing, documentation, CI/CD integration, report generation, ready to deploy.
Expected Output
Custom lint rules configured and integrated.
Example Output
Lint Rules ✓ Rules: 12 created ✓ Integration: CI/CD ✓ Reports: automated Status: Active
106
Multi-File Token Merge
Merge tokens from multiple Figma files.
Chat
CLI
Automation
Prompt #106 — Chat
Merge tokens across files: 1. Extract tokens from multiple files 2. Identify conflicts 3. Merge with priority rules 4. Validate merge 5. Generate output 6. Document conflicts Provide multi-file merge.
VARIATIONS
QUICKMerge tokens from multiple files.
COMPLETEMerge: extraction, conflict detection, merge logic, validation, output.
FULLComplete multi-file token merge. Include: token extraction from all files, conflict detection and resolution, custom merge rules, comprehensive validation, output generation, conflict documentation, ready for use.
Expected Output
Merged token file with conflict resolution.
Example Output
Token Merge ✓ Files: 3 merged ✓ Tokens: 347 total ✓ Conflicts: 5 (resolved) Status: Complete
107
Design-to-Test Generator
Generate test cases from design specifications.
Chat
CLI
Automation
Prompt #107 — Chat
Generate test cases from [FILE_KEY]: 1. Extract component specs 2. Identify test scenarios 3. Generate test cases 4. Create test code 5. Document tests 6. Integration ready Provide test generation.
VARIATIONS
QUICKGenerate test cases from [FILE_KEY].
COMPLETETests: specs extraction, scenarios, test generation, code creation, documentation.
FULLComplete test case generation from [FILE_KEY]. Include: component spec extraction, test scenario identification, test code generation (Jest/Cypress), documentation, integration with CI/CD, ready for automation.
Expected Output
Generated test cases ready for implementation.
Example Output
Test Generation ✓ Components: 47 ✓ Test cases: 234 ✓ Code: generated Status: Ready
108
Full Design System Pipeline
Complete end-to-end design system automation.
Chat
CLI
Automation
Prompt #108 — Chat
Set up full DS pipeline from [FILE_KEY]: 1. Token sync 2. Component generation 3. Documentation generation 4. Testing 5. Validation 6. Deployment 7. Notifications 8. Complete automation Provide full pipeline.
VARIATIONS
QUICKSet up complete DS pipeline from [FILE_KEY].
COMPLETEPipeline: tokens, components, docs, tests, validation, deploy, notifications, automation.
FULLComplete end-to-end design system pipeline from [FILE_KEY]. Include: automated token sync, component code generation, documentation generation, automated testing, validation checks, deployment to registries, team notifications, full CI/CD automation, production-ready.
Expected Output
Complete automated design system pipeline operational.
Example Output
Full DS Pipeline ✓ Trigger: Git push or Figma change ✓ Tokens: sync ✓ ✓ Components: generate ✓ ✓ Docs: generate ✓ ✓ Tests: run ✓ ✓ Validate: ✓ ✓ Deploy: ✓ ✓ Notify: ✓ Status: Fully automated