craft-project-setuplisted

Scaffold Claude Code configuration specifically for Craft CMS projects. Generates CLAUDE.md and .claude/rules/ files tailored to the project type (plugin, site, module, hybrid, or monorepo). Only for Craft CMS projects — not for Next.js, Laravel, or other frameworks. Triggers on: 'set up Claude for this Craft project', 'initialize CLAUDE.md', 'scaffold project config', 'configure Claude Code for Craft', 'create CLAUDE.md', 'missing CLAUDE.md', 'does this project have a CLAUDE.md', 'bootstrap Claude config', 'new Craft project setup', 'onboard a developer to this Craft project', 'generate .claude/rules', 'set up coding standards config', 'upgrade Claude config', 'update CLAUDE.md', 'compare my setup', 'is my config up to date', 'audit my Claude setup', 'redo project setup'. Also triggers when starting work in a new Craft CMS project that lacks a CLAUDE.md file, or when the user wants to check or upgrade an existing configuration. Detects project type from composer.json (craft-plugin, craft-module, project), .d
michtio/craftcms-claude-skills · ★ 46 · AI & Automation · score 83

Install: claude install-skill michtio/craftcms-claude-skills

# Craft CMS Project Setup Scaffold Claude Code configuration for Craft CMS projects. Generates a `CLAUDE.md` and `.claude/rules/` directory tailored to the project type. ## Companion Skills — Used During Scaffolding This skill generates configuration that references other skills. It does not load them at activation, but the generated CLAUDE.md and rules will guide users toward: - **`craftcms`** + **`craft-php-guidelines`** + **`craft-garnish`** — for plugin and module projects (craft-garnish when plugin has CP JavaScript/asset bundles) - **`craft-site`** + **`craft-twig-guidelines`** + **`craft-content-modeling`** — for site projects - **`ddev`** — for all project types (DDEV commands in generated config) ## Workflow ### Step 1: Detect the project Read the project root to determine what exists. **Detect, don't assume.** Every piece of information below should be resolved by reading actual project files — never flag something as "unknown" when the answer is in `composer.json`, `package.json`, `.ddev/config.yaml`, or `git` state. #### Project structure signals - `.ddev/config.yaml` — DDEV project name, PHP version, database type, Node version - `composer.json` — package type (`craft-plugin`, `craft-module`, or `project`), dependencies, scripts (check-cs, phpstan, pest) - `src/` or `src/Plugin.php` — plugin source directory - `templates/` — site templates - `config/project/` — Craft project config (indicates a site) - `config/general.php` — Craft general config - `modul