Skip to content

michtio/craftcms-claude-skills / skills/craft-project-setup

craft-project-setup

Verified

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.

templates/site/.claude/rules/git-workflow.md

View on GitHub
# Git Workflow

- Conventional commits: `feat(scope):`, `fix(scope):`, `refactor(scope):`, `docs:`, `test:`, `chore:`.
- **Subject line only** for most commits. One line, under 72 characters, describes the what: `feat(blog): add hero image preset for card thumbnails`.
- **Body only when the why isn't obvious** — a content model change that affects existing entries, a breaking template change, a multi-site propagation decision. Even then, keep it to 3-5 lines max. If the commit message is longer than the diff, something is wrong.
- Never include: "Verification" sections, "How to undo" sections, "Follow-up" sections, file-by-file change lists, or test count reports. The diff shows what changed. The PR description (if any) covers the broader context. The commit message covers the why.
- `--amend` for fixes to the most recent unpushed commit. New commit once pushed.
- No AI attribution in commit messages. No "Co-Authored-By" lines referencing AI tools.
- All comments, commit messages, and documentation in English only.
- Use absolute paths in git commands. Never `cd path && git commit` — the target directory may have untrusted hooks.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall