Figma To Generateblocks

Community

wpgaurav

figma-to-generateblocks

Convert Figma designs to GenerateBlocks V2 format for WordPress

Overview

Publisher	wpgaurav
Repository	`generateblocks-skills`
Skill name	`figma-to-generateblocks`
Stars	130
Forks	19
Bundled files	2
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by wpgaurav on GitHub. Read the source before you install it.

Installation

Install the Figma To Generateblocks AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/wpgaurav/generateblocks-skills/tree/main/skills/figma-to-generateblocks

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/wpgaurav/generateblocks-skills.git /tmp/generateblocks-skills
mkdir -p .claude/skills
cp -r /tmp/generateblocks-skills/skills/figma-to-generateblocks .claude/skills/figma-to-generateblocks

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Figma To Generateblocks in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Figma To Generateblocks on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Figma To Generateblocks is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Inspect the relevant frames, assets, variants, and available measurements. Follow required Figma tool/skill prerequisites when using its connector.
Map Auto Layout to intrinsic flex/grid structure, retaining semantic headings and reading order. Use the mapping reference for uncertain properties.
Preserve typography and source states. Frame widths are not automatically breakpoints; document responsive decisions absent from the source.
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 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

CLAUDE.md1 KB
references/design-mapping.md4 KB

Frequently asked questions

What does the Figma To Generateblocks AI skill do?

Convert Figma designs to GenerateBlocks V2 format for WordPress

Why use Figma To Generateblocks on TypingMind?

Because you install it once and use it with any model. Figma To Generateblocks is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Figma To Generateblocks in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wpgaurav/generateblocks-skills/tree/main/skills/figma-to-generateblocks. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Figma To Generateblocks?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Figma To Generateblocks?

As many as you like. As long as a model supports skills, you can use Figma To Generateblocks with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Figma To Generateblocks AI skill free?

It is published on GitHub by wpgaurav. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Slides

nextlevelbuilder

OrganizationPopular

Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Figma to GenerateBlocks

Shared contract

Conversion workflow

Delivery

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now