Generateblocks Layouts logo

Generateblocks Layouts

Community
wpgaurav
generateblocks-layouts

Build and audit WordPress layouts with GenerateBlocks V2, including CSS Mode, responsive at-rules, dynamic data, Pro components, and recovery-safe block serialization. Use for new GB layouts, conversions, repairs, and hand-authored block markup.

Overview

Publisherwpgaurav
Repositorygenerateblocks-skills
Skill namegenerateblocks-layouts
Stars
130
Forks
19
Bundled files
58
Links
  • 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.

  • 58 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 Generateblocks Layouts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/generateblocks-layouts .claude/skills/generateblocks-layouts
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Generateblocks Layouts 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 Generateblocks Layouts 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 Generateblocks Layouts 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.

GenerateBlocks layout builder

Build or repair GenerateBlocks V2 layouts using the installed plugin's native serialization. This skill supports local styling, dynamic content, Pro blocks, and explicitly requested shared systems.

Use GenerateBlocks and core blocks only. Keep styling in native block styles/css and use native Pro blocks for interactions. Do not introduce Scripts Manager, Page Block, Custom HTML/CSS/JS, another builder, or theme/plugin code to complete a GenerateBlocks design. An external implementation requires an explicit user request. Simplify unsupported effects within native blocks.

Read only what the task needs

Before generating markup, read authoring-contract.md. It owns the scope prompt, IDs, blocks, serialization, CSS parity, responsive basics, and validation rules. Use _index.md to select additional references. Do not load the entire library or recovery catalog for a routine static layout; the compact contract is sufficient for familiar Element/Text layouts using ordinary states and native breakpoints.

Local styles are the default. Prompt once about shared Global Styles and Design Tokens unless the user already chose. Add shared records or new shared dependencies only after explicit opt-in; preserve existing references. The contract contains the exact prompt; styling-scope.md covers edge cases.

Workflow

  1. Inspect the source/target, versions, and design guidance. Use the real post ID when available; otherwise use a random four-digit block-ID scope.
  2. Select semantic blocks and preserve content/behavior. For new designs, read design-quality.md; for dynamic data, read dynamic-tags.md and its task guide.
  3. Generate file output with the native serializer or scripts/gb_serialize.py. Keep editable styles and compiled css aligned.
  4. Run scripts/preflight.py FILE --id-scope SCOPE, then validate unfamiliar output in the real editor. Check visible content and relevant responsive/interactivity behavior. Static preflight alone is not proof of editor validity.
  5. For live writes, first read mcp-publishing.md; snapshot, splice, read back, and verify with scripts/verify_roundtrip.py.

Keep summaries short: what changed, output path, required Pro features, tests, and any unverified behavior. Source conversion does not authorize publication.

Examples and failures

Use examples as structural starting points; replace their IDs, URLs, and content. Choose a relevant file in examples/basic, compound, layouts, or svg only when needed. examples/beta-design-system is an opt-in shared-system example, not the default starter.

For a recovery/preflight failure, open the matching topic in recovery-rules.md or troubleshooting.md. For an unfamiliar attribute/tag, use block-types.md or installed block.json. Reuse scripts rather than duplicating escape tables or embedding another block manual here.

Bundled files

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

Frequently asked questions

What does the Generateblocks Layouts AI skill do?

Build and audit WordPress layouts with GenerateBlocks V2, including CSS Mode, responsive at-rules, dynamic data, Pro components, and recovery-safe block serialization. Use for new GB layouts, conversions, repairs, and hand-authored block markup.

Why use Generateblocks Layouts on TypingMind?

Because you install it once and use it with any model. Generateblocks Layouts 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 Generateblocks Layouts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wpgaurav/generateblocks-skills/tree/main/skills/generateblocks-layouts. 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 Generateblocks Layouts?

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 Generateblocks Layouts?

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

Is the Generateblocks Layouts 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇