/figma-to-generateblocks

name: figma-to-generateblocks
description: Convert Figma designs to GenerateBlocks V2 format for WordPress
metadata:
  version: 1.0.0
  author: Gaurav Tiwari
  updated: '2026-09-18'
  trigger:
  - Figma to GenerateBlocks
  - convert Figma
  - Figma design to WordPress
  - Figma to GB
  - implement Figma design
  - Figma screenshot
  - design to blocks
  tags:
  - wordpress
  - generateblocks
  - figma
  - conversion
  - design
  compatibility: V2 guidance verified on free 2.5.0 / Pro 2.8.0 (WordPress 7.1.3); design-system
    routing

Figma to GenerateBlocks

Convert a supplied Figma design, exported CSS, or screenshot into editable native blocks. Distinguish measured source properties from inferred behavior.

Use GenerateBlocks (including Pro) and core blocks only. Keep CSS in native block styles and interactions in native blocks. Do not add Scripts Manager, Page Block, Custom HTML/CSS/JS, or another builder without an explicit request.

Shared contract

Use the companion `generateblocks-layouts` skill's `references/authoring-contract.md` before emitting markup, and its `references/_index.md` to select task-specific guides. With installed skills it is the sibling `../generateblocks-layouts/`; a standalone bundle carries the same dependency under `references/generateblocks-layouts/`. Do not read both copies or the entire library.

**Local block styles are the default.** Prompt once about shared Global Styles and Design Tokens unless the user already chose. Create/import shared records or add new shared dependencies only after explicit opt-in; preserve existing references. The companion contract owns the exact scope and prompt. Use the real post ID when available, otherwise one random four-digit scope for the layout.

Conversion workflow

1. Inspect the relevant frames, assets, variants, and available measurements. Follow required Figma tool/skill prerequisites when using its connector. 2. Map Auto Layout to intrinsic flex/grid structure, retaining semantic headings and reading order. Use the mapping reference for uncertain properties. 3. Preserve typography and source states. Frame widths are not automatically breakpoints; document responsive decisions absent from the source. 4. Generate `{design-name}.html`, compare against the design, and run the shared validation flow. A screenshot alone cannot establish CMS or form behavior.

The companion contract contains the familiar static Element/Text path. Load [this conversion reference](references/design-mapping.md) only when the source mapping requires it. New visual decisions additionally require `design-quality.md`. Dynamic data requires `dynamic-tags.md` plus the relevant query/field guide; interactive Pro blocks require their native schemas/save output.

Delivery

Write blocks to files, not chat. Use the companion serializer helpers and run `preflight.py FILE --id-scope SCOPE`. Confirm unfamiliar output in the actual editor and compare visible content and behavior; static preflight is not sufficient. A live write also requires `mcp-publishing.md`, a snapshot, and raw-content readback. A conversion request by itself does not authorize publication.

Keep serialization, class-order, link, CSS-state, and breakpoint rules in the companion contract rather than duplicating them here. Examples are not current brand defaults or import-ready markup for a different post.