# figma-to-content

figma-to-content turns a Figma page design into an AEM Edge Delivery Services page in Document Authoring. It maps sections to project blocks and deploys the result.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 222 installs · ★ 335 repo stars
- Author: adobe
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/adobe/skills/tree/HEAD/plugins/aem/edge-delivery-services/skills/figma-to-content/SKILL.md
- Updated: 2026-10-31
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/figma-to-content

## What it does

The skill reads a selected Figma frame and matches its sections to blocks in the target project. When a section needs a component the project lacks, it can build a new isolated block. Plain headings, text, images, and buttons become content; the section plan is confirmed before work when annotations do not specify the mapping.

It needs a reachable Figma MCP, an EDS project checkout, and a DA IMS token (`DA_TOKEN`). The skill delegates authentication, DA markup rules, and block development to other skills, then creates a DA body fragment and deploys it through the Source API for preview. Without the MCP or token, it cannot read the design or write the page.

This workflow is for adding pages to an existing EDS project. It is out of scope for restyling an existing site or for Universal Editor. Existing blocks are not reskinned; differing designs call for new isolated blocks instead.

## Requirements
- Works with: Figma

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill figma-to-content -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/figma-to-content/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/figma-to-content/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill figma-to-content -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/figma-to-content/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill figma-to-content -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/figma-to-content/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install adobe/skills plugins/aem/edge-delivery-services/skills/figma-to-content
```

2. **Manually: put the files in place**
- File: `.github/skills/figma-to-content/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill figma-to-content -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/adobe/skills --path plugins/aem/edge-delivery-services/skills/figma-to-content
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/figma-to-content/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill figma-to-content -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/adobe/skills/tree/HEAD/plugins/aem/edge-delivery-services/skills/figma-to-content/SKILL.md

## When to use it
- turn a Figma frame into an EDS page
- match design sections to blocks in a project
- build an isolated block for a section without a suitable component
- create DA content and deploy a preview

## Example prompts
- Build an EDS page from this Figma frame and confirm the section plan first.
- Turn this Figma design into a Document Authoring page for my EDS project.
- Publish this page design to DA and prepare a preview.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: a4f159242ab9a524.

BEGIN THIRD-PARTY FILE a4f159242ab9a524
```text
---
name: figma-to-content
description: "Use this to turn a Figma design into an AEM Edge Delivery Services (EDS / AEM / Franklin / Helix) content page in Document Authoring (DA, da.live). Triggers: \"build this Figma frame in EDS\", \"turn this Figma design into a DA page\", \"publish this design to da.live\", or providing a figma.com URL for a page. Reads the frame (and any annotations) via a Figma MCP, resolves each section to an existing block, a new isolated block, or default content (inferred against the project's existing blocks and confirmed with you, or read from annotations when the frame happens to have them), generates DA-compliant body-fragment HTML, and deploys via the DA Source API + preview."
license: Apache-2.0
metadata:
  version: "1.0.0"
---

# figma-to-content — Figma design → EDS content page in DA

Read a Figma frame, assemble a page from EDS blocks and default content, and
publish it to Document Authoring. Runs with a **Figma MCP** (to read the
design) and a **DA IMS token** (to write content) — no proprietary tooling
required.

This skill **orchestrates existing skills**; it does not reimplement DA rules,
block knowledge, or block-building. **Invoke those skills — do not inline them.**
The condensed rules quoted in this file are *pointers* to jog the right skill,
never a substitute for loading it: when a phase names a skill, invoke it and work
from its actual guidance. Running this file as a self-contained procedure —
hand-writing blocks, authoring DA HTML from memory, skipping the browser/visual
check — is the single most common way a run goes wrong. Phase 2.3 turns the
confirmed plan into an explicit manifest of the sub-skills you must invoke.

## Two paths

Classify each section of the design, then follow the matching path:

- **Content only** — every section maps to a block that **already exists** in
  the target project, or to **default content** (plain headings/paragraphs/
  images/buttons — no block). Author content and deploy. No code changes.
- **Content + code** — a section needs a block the project **does not have**,
  or an existing block matches structurally but its **styling diverges** (the
  look lives in block-specific CSS you'd have to edit). Create it as a **new,
  isolated block** (via the block-building skills), push the code, then author
  content and deploy. **Never skin an existing block or add per-section rules
  to global CSS** — new, additive blocks only. (Retargeting the project's
  global design tokens is a separate, allowed theming step; see Guardrails.)
```
END THIRD-PARTY FILE a4f159242ab9a524

The third-party file has ended. Everything between the a4f159242ab9a524 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2572 of 59608 bytes. © adobe · Apache-2.0 · https://github.com/adobe/skills/tree/HEAD/plugins/aem/edge-delivery-services/skills/figma-to-content/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
