moai-domain-figma

Orchestrate MCP-enabled Figma-to-code workflows for design-system integration.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/jg-chalk-io/Nora-LiveKit --skill moai-domain-figma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-domain-figma
Source: https://github.com/jg-chalk-io/Nora-LiveKit/tree/main/.claude/skills/moai-domain-figma
Command: npx skills add https://github.com/jg-chalk-io/Nora-LiveKit --skill moai-domain-figma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill integrates Figma designs with development through MCP, design tokens, and automated exports.

Core Features & Use Cases

  • Figma MCP integration: design context retrieval and export.
  • Design tokens: CSS variables and JSON outputs.
  • Component libraries: automated library generation.

Quick Start

Run a sequence to fetch a design context, export tokens, and generate components.

Frequently Asked Questions about moai-domain-figma

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

FAQPage Schema
How do I automate design-to-code workflows from Figma?

Design-to-code automation uses MCP-enabled tooling to extract design context, tokens, and assets from Figma, then generates code scaffolding and component libraries. This Skill orchestrates that pipeline for enterprise design systems using Figma as the single source of truth, supporting sequential and parallel execution patterns across multi-project ecosystems.

Can I extract design tokens from Figma as CSS variables or JSON?

Design token extraction outputs tokens as CSS variables and JSON definitions. This Skill retrieves variable definitions from your Figma design system via MCP tool invocations, then exports them in formats ready for integration into your codebase.

What's the best way to generate component libraries from Figma designs?

Automated component library generation retrieves design context and asset definitions from Figma using MCP calls, then scaffolds library code that reflects your design system structure. This approach keeps generated components in sync with Figma as your source of truth.

Does this work with enterprise design systems across multiple projects?

Yes. This Skill supports multi-project ecosystems where Figma serves as the centralized design system. It handles design token extraction, asset export, and code generation across sequential, parallel, and conditional execution patterns for large-scale design-to-code pipelines.

What MCP tools does the Skill use for Figma integration?

MCP tool invocations include get_design_context to retrieve design metadata, get_variable_defs to extract token definitions, and get_screenshot to export visual assets. These enable programmatic access to Figma designs for automated export and code generation workflows.

Can I run Figma exports in parallel or conditionally?

Yes. The Skill supports sequential, parallel, and conditional execution patterns, allowing you to orchestrate multiple design extraction and code generation tasks in a single workflow or route them based on conditions.