Thanks for considering a contribution. This repo is intentionally small — its job is to be a clean, copy-paste starter for Claude Code anti-regression configs. PRs that add real, battle-tested artifacts are very welcome.
- Sister rules for new languages —
.claude/rules/go-backend.md,rust-backend.md,typescript-node.md,kotlin.md, etc. Follow the existingpython-backend.mdshape (frontmatterglobs:+ sections + a one-line "why" per rule). - Framework-specific subagents —
django-tester.md,nextjs-reviewer.md,rails-planner.md. Constraintools:to the minimum set needed and document the output format. - Additional
PreToolUsehooks — examples that would fit:- Lint gate on
git commit*(ruff check/eslint/golangci-lint) - Secret-scanning gate on
git commit*(gitleaks detect --staged) - Migration-safety gate on writes to
migrations/directory
- Lint gate on
- Stack-specific test-command swap-ins for the README's
Configuration notessection (Maven, Gradle, sbt, mix, etc.). - Recording assets — better demo GIF / asciinema cast than the placeholder.
- "Best practices" essays without code artifacts.
- Vendor-specific rules that lock the user into a single editor or shell beyond what the existing setup already does.
- Hooks that silently weaken the commit gate (e.g.
pytest --pass-with-no-testswithout a clear opt-in note). - Generic linter configs that already have canonical homes elsewhere (just link to them in
docs/MCP-SETUP.mdstyle).
- New rule file has frontmatter
globs:and at least one "why" rationale per bullet - New subagent has
name:,description:,tools:frontmatter and an explicit output format - New hook has a stated timeout, a stated shell (bash / pwsh / cross-platform), and a tested failure path
-
README.mdandCHANGELOG.mdupdated when surface area changes -
validate.ymlworkflow still passes (it checkssettings.jsonis valid JSON and every.claude/agents/*.mdhas aname:frontmatter field)
- Prefer concrete commands and version numbers over abstract advice.
- One sentence per rule. If you need a paragraph, you are explaining the wrong thing.
- Cite the source of any "best practice" you import (Anthropic docs, SFEIR Institute, real incident).
@CreatmanCEO — Nick Podolyak. Open an issue first for anything larger than a single rule or subagent.