/ Verzeichnis / Playground / craftcms-claude-skills
● Community michtio ⚡ Sofort

craftcms-claude-skills

von 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.

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

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

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: craftcms-claude-skills

Scaffold a custom Craft CMS module without leaving Claude Code

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

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

Ablauf
  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.✓ Kopiert
    → 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.✓ Kopiert
    → 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.✓ Kopiert
    → Query class with proper WHERE clauses, not raw SQL soup

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

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

Refactor a mess of Twig templates into idiomatic Craft

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

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

Ablauf
  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.✓ Kopiert
    → 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.✓ Kopiert
    → Macro file created; includes use {% from %} syntax

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

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

Write a safe Craft migration for content model changes

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

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

Ablauf
  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.✓ Kopiert
    → 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.✓ Kopiert
    → Step-by-step checklist including DB backup

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

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert
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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
Moderate — reference files load on demand
Kosten in €
Free
Tipp
Reference the skill by name only when working on Craft code; it adds context overhead to unrelated tasks.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials
Datenabfluss: None — local prompts and files only

Fehlerbehebung

Häufige Fehler und Lösungen

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

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

Prüfen: 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

Prüfen: ./craft project-config/diff

Alternativen

craftcms-claude-skills vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen