drupal-gutenberg

drupal-gutenberg-llm-skills

Skills for Drupal Gutenberg, Drupal's implementation of the WordPress Gutenberg block editor. Installable as a plugin in both Claude Code and GitHub Copilot CLI.

Skills

drupal-gutenberg-markup

Generates valid Drupal Gutenberg HTML block markup. Covers <!-- wp:blockname --> comment syntax, attributes, nested blocks, column layouts, and block patterns.

Both tools auto-detect this skill when you ask about creating Gutenberg content. You can also invoke it explicitly:

• Claude Code: /drupal-gutenberg:drupal-gutenberg-markup
• Copilot CLI: include /drupal-gutenberg-markup in your prompt, e.g. "Use the /drupal-gutenberg-markup skill to create a hero section"

Example prompts:

• "Create a Drupal Gutenberg page with a hero image, two columns, and a call-to-action button"
• "Write Gutenberg block markup for a testimonials section with three cards"
• "Convert this HTML into valid Gutenberg block markup"

drupal-gutenberg-dev

Helps build custom Gutenberg blocks and modules for Drupal. Covers module structure, .gutenberg.yml configuration, ES6/Babel build toolchain, block registration, Twig server-side rendering, and media integration.

Both tools auto-detect this skill when you're working on Gutenberg module code. You can also invoke it explicitly:

• Claude Code: /drupal-gutenberg:drupal-gutenberg-dev
• Copilot CLI: include /drupal-gutenberg-dev in your prompt

Example prompts:

• "Create a custom Gutenberg block module that displays a featured content carousel"
• "Set up server-side rendering for my custom block with a Twig template"
• "What's the Twig template naming convention for Drupal Gutenberg?"

Installation

Claude Code

Quick start (single session):

claude --plugin-dir /path/to/drupal-gutenberg-llm-skills

Permanent install via local marketplace:

# Register the repo as a local marketplace (one-time setup)
/plugin marketplace add /path/to/drupal-gutenberg-llm-skills

# Install the plugin
/plugin install drupal-gutenberg@drupal-gutenberg-llm-skills

GitHub Copilot CLI

Install from a local clone:

copilot plugin install /path/to/drupal-gutenberg-llm-skills

Install directly from GitHub (no local clone needed):

copilot plugin install owner/drupal-gutenberg-llm-skills

Verify the install:

copilot plugin list

Or inside an interactive session:

/skills list

Development

If you're working on the skill content in this repo:

1. Clone the repo and make your changes to the Markdown files under skills/.

2. Test locally — load directly from your working copy without an install step:

   • Claude Code: claude --plugin-dir ./
   • Copilot CLI: copilot --plugin-dir ./

3. Iterate — edit skill files, restart the tool, and verify the skills activate and produce correct output.

   • In Copilot CLI you can also run /skills reload during a session after adding or editing a skill.

4. Publish — push to the repo. To pick up changes in Copilot CLI after a pull: copilot plugin install /path/to/repo (re-run install to refresh the cache).

---

Maintaining this plugin

Note (March 2026): Both Claude Code and Copilot CLI converged on a very similar plugin/skill structure, which is why this repo works for both without duplication. Both systems are actively evolving — treat the specifics below as current best-effort, not permanent truth.

What both tools share

Because of deliberate format alignment between the two tools, a single set of files serves both:

File	Used by	Notes
.claude-plugin/plugin.json	Both	Both tools recognize this path as a valid plugin manifest location
.claude-plugin/marketplace.json	Both	Both tools recognize this path for marketplace registration
skills/*/SKILL.md	Both	Default skill convention for both; the name and description frontmatter fields drive auto-detection in both
Supporting .md files in skills/*/	Both	Referenced from SKILL.md body; loaded into context by both tools
CLAUDE.md	Both	Claude Code uses it as plugin-level instructions; Copilot CLI uses it as project-level instructions — keep it accurate for both contexts

What to keep in sync when editing

When you change any of the following, check that both tools still behave correctly: