craft-project-setup

To set up Claude Code for Craft CMS, run the craft-project-setup skill which detects your project type from composer.json, .ddev/config.yaml, templates/, config/project/, and modules/, then generates a tailored CLAUDE.md and .claude/rules directory with consistent coding standards and tooling references.

Yes, Claude Code can detect project type by analyzing composer.json, .ddev/config.yaml, templates/, config/project/, and modules/ to determine whether your Craft CMS project is a plugin, module, site, hybrid, or monorepo, and scaffolds configuration accordingly.

The best way to scaffold CLAUDE.md for a Craft CMS monorepo is to run the craft-project-setup skill, which detects the monorepo structure from composer.json and modules/ directories, then generates customized rule files under .claude/rules/ tailored to that project type.

Yes, the Craft CMS project setup preserves your existing CLAUDE.md file when present. The skill generates a usable configuration that references craftcms skills and universal defaults while safeguarding any current CLAUDE.md content you already have.

You do not strictly need DDEV, but the skill uses .ddev/config.yaml as one of several detection signals alongside composer.json, templates/, config/project/, and modules/ to identify your Craft CMS project type and generate appropriate configuration.

Your Craft CMS project type matters because the scaffolding generates different CLAUDE.md content and .claude/rules files depending on whether your project is a plugin, module, site, hybrid, or monorepo, ensuring coding standards match your specific development context.