/ Directory / Playground / craftcms-claude-skills
● Community michtio ⚡ Instant

craftcms-claude-skills

by michtio · michtio/craftcms-claude-skills

A Claude Code skill bundle that knows Craft CMS 5 inside out — writes modules, Twig templates, migrations, and GraphQL queries the Craft way.

Production-ready skills, agents and project templates that teach Claude Code how Craft CMS 5 actually works. Instead of generic PHP suggestions, you get idiomatic Craft patterns — proper element queries, field handles, module structure, Pixel & Tonic conventions.

Why use it

Key features

Live Demo

What it looks like in practice

craftcms-claude-skill.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use craftcms-claude-skills

Scaffold a custom Craft CMS module without leaving Claude Code

👤 Craft CMS developers building site-specific modules ⏱ ~30 min intermediate

When to use: You need a new module and don't want to hand-copy another one as a template.

Flow
  1. Describe the module's job
    Use craftcms-claude-skills. Create a new module called 'Inventory' that registers a custom element type for warehouse items.✓ Copied
    → Claude scaffolds modules/inventory/ with src/Inventory.php, elements/WarehouseItem.php, and a config entry
  2. Wire it up
    Register the module in config/app.php and add the bootstrap entry.✓ Copied
    → Config diff shown; module loads without errors on craft setup/check
  3. Add an element query
    Add a WarehouseItemQuery class with a custom 'sku' parameter that filters on the content table.✓ Copied
    → Query class with proper WHERE clauses, not raw SQL soup

Outcome: A working Craft module that follows Pixel & Tonic conventions — ready for your first migration.

Pitfalls
  • Claude writes Craft 3/4 style code — Explicitly state Craft CMS 5 in every prompt — the API surface changed
Combine with: filesystem · mysql

Refactor a mess of Twig templates into idiomatic Craft

👤 Front-end devs inheriting a Craft site with sketchy templates ⏱ ~45 min intermediate

When to use: You took over a Craft project and the templates are full of raw SQL, inline PHP, and cache tags that don't work.

Flow
  1. Point Claude at the worst template
    Using craftcms-claude-skills, review templates/_entries/blog.twig and rewrite it using proper element queries and {% cache %} tags.✓ Copied
    → Refactored template with craft.entries, section handle, and correct cache scoping
  2. Extract reusable macros
    Pull the card markup into a macro in _macros/cards.twig and include it properly.✓ Copied
    → Macro file created; includes use {% from %} syntax

Outcome: Templates that load faster and future devs can actually read.

Pitfalls
  • Cache tags wrap dynamic user data and show wrong content — Use {% cache %} with globally keyed variations, never around authenticated user data
Combine with: filesystem

Write a safe Craft migration for content model changes

👤 Craft devs shipping schema changes to production ⏱ ~30 min advanced

When to use: You're adding a new field or restructuring an existing one and need a migration that won't eat data.

Flow
  1. Describe the change
    Use craftcms-claude-skills. Write a Craft migration that adds a 'featuredAt' datetime field to the News section, with a safe backfill from postDate.✓ Copied
    → Migration file with safeUp / safeDown; uses Craft's Fields service, not raw schema hacks
  2. Dry-run in dev
    Walk me through testing this with ./craft migrate/up --interactive=0 on a staging copy first.✓ Copied
    → Step-by-step checklist including DB backup

Outcome: A migration you can ship on a Friday without panic.

Pitfalls
  • Forgetting to register the field type in project config — Always run craft project-config/write after the migration and commit the YAML
Combine with: mysql · git

Combinations

Pair with other MCPs for X10 leverage

craftcms-claude-skill + filesystem

Skill provides Craft patterns; filesystem lets Claude actually apply them in your project

Apply the craftcms-claude-skills module scaffold to my current project directory.✓ Copied
craftcms-claude-skill + mysql

Inspect Craft's content tables while writing migrations

Show me the current schema of the elements_sites table before I write this migration.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
module_scaffold module name, element types Starting a new module 0
field_generator field name, type, handle Adding a custom field type 0
twig_refactor template path Cleaning up legacy templates 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Moderate — reference files load on demand
Monetary
Free
Tip
Reference the skill by name only when working on Craft code; it adds context overhead to unrelated tasks.

Security

Permissions, secrets, blast radius

Credential storage: No credentials
Data egress: None — local prompts and files only

Troubleshooting

Common errors and fixes

Claude generates Craft 3-era code (craft()->elements)

Mention 'Craft CMS 5' explicitly; the API namespace is craft\elements in 5.x

Verify: grep -r 'craft()->' src/ should return nothing in Craft 5 code
Migration runs but field doesn't appear in CP

Run ./craft project-config/write and ./craft project-config/apply — project config drift is the usual cause

Verify: ./craft project-config/diff

Alternatives

craftcms-claude-skills vs others

AlternativeWhen to use it insteadTradeoff
Raw Claude CodeSimple Twig-only tweaks that don't need Craft-specific idiomsGeneric PHP suggestions, often wrong for Craft
symfony-hexagonal-skillYou're on Symfony, not CraftDifferent framework conventions

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Shared context · cms

Payload CMS Skills

Apply Payload’s TypeScript-first development guidance to collections, fields, hooks, access control, queries, and plugins.

Skill

Browse all topic collections → · See 29 new official additions →