All skills
michtio avatar

/craft-project-setup

@64a3c26

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), .ddev/config.yaml, templates/, config/project/, and modules/. NOT for installing Craft CMS itself, creating DDEV environments, writing PHP code, building templates, or content modeling. NOT for non-Craft projects — if the project is React, Next.js, Laravel, or any non-Craft framework, this skill does not apply.

Use this Skill: https://skilld.dev/gh/michtio/craftcms-claude-skills/craft-project-setup

This session only. Nothing lands on disk.

templatessiteCLAUDE.md

≈475 tokens on demand. Your agent reads this file only when SKILL.md points to it.

{{projectName}} — Craft CMS 5 Site

@.claude/rules/templates.md @.claude/rules/git-workflow.md @.claude/rules/security.md

General

Be critical. We're equals — push back when something doesn't make sense.

Do not excessively use emojis. Do not include AI attribution in commits, PRs, issues, or comments.

Do not include "Test plan" sections in PR descriptions.

Tools

Use ddev shorthand commands: ddev composer, ddev craft, ddev npm. Never run php, composer, or npm on the host — everything goes through DDEV.

Never install Craft plugins (ddev composer require) without explicit approval. Plugin selection is a planning decision.

Use gh for all GitHub operations.

Environment

ddev npm run dev                     # Vite dev server
ddev npm run build                   # Production build
ddev craft up                        # Migrations + project config
ddev composer install                # Install deps (auto-runs craft up)

Template Structure

templates/
├── _boilerplate/                # Base layouts, HTML head, critical partials
├── _atoms/                      # Smallest UI elements (buttons, links, text)
├── _molecules/                  # Composed atoms (cards, media objects)
├── _organisms/                  # Complex sections (heroes, footers, navs)
├── _views/                      # Page-level templates (entry type views)
├── _builders/                   # Content builder block renderers
└── index.twig                   # Homepage

Content Model

Document the key sections, entry types, and fields here after content modeling is complete.

Documentation

Source: SKILL.md on GitHub

1 warning16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill automates Craft CMS project setup by scaffolding configuration and pre-approving developer commands to improve agent efficiency. While functional, the broad permission grants and the audit workflow for external repositories introduce surfaces for unauthorized command execution and indirect prompt injection.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

Signed by skilld at 64a3c26. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 weeks ago.

Activeupdated 2 weeks ago

README badge

README badge for michtio/craftcms-claude-skills/craft-project-setup