Files
sar/.agents/skills/wds-6-asset-generation/data/figma-integration-guide.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00:00

38 lines
1.1 KiB
Markdown

# Figma to Code Workshop
**Status:** Coming Soon
**Purpose:** Extract design specifications from Figma and implement them in code
**Tool:** Figma Desktop MCP Server
**Direction:** Figma → Code
---
## Overview
This workshop will guide AI agents through importing design specifications from Figma to generate or update code implementations.
### When to Use Figma to Code
Import from Figma when:
- ✅ Designer has updated visual specifications in Figma
- ✅ New design system components need implementation
- ✅ Design tokens (colors, spacing, typography) need extraction
- ✅ Component states have been refined visually
- ✅ Design-code sync is needed after visual iteration
---
## Planned Workflow
1. **Connection Check** - Verify Figma Desktop MCP server
2. **Select Figma Node** - Identify what to import
3. **Extract Design Specs** - Get colors, spacing, typography, layout
4. **Generate/Update Code** - Create or update components
5. **Verify Implementation** - Compare code output to Figma design
---
*This workshop will be developed to complement the Code to Figma workflow.*