Claude Governance

Claude Code Governance Templates

Ready-to-use governance templates for Claude Code, organized by tech stack.
Rules load automatically on every session: no prompting required.

If this saves you time, consider giving it a ⭐: it helps others find the project.

Why this exists

Without structure, Claude Code generates inconsistent code, ignores your conventions, and repeats the same mistakes across sessions. This project fixes that with a hierarchy of CLAUDE.md files that load automatically: no prompting required.

What you get:
- Consistent code that respects your architecture and naming conventions
- Security rules enforced by default (no IDOR, no raw SQL, no hardcoded secrets)
- Cost control: precise diffs instead of full rewrites, right model for the right task
- Behavior adapted to the developer's experience level (Junior → Tech Lead)

Installation

Via plugin marketplace (recommended):

Then run /setup in any project: select your stack, governance files are copied automatically, and rules inject at every session start.

Local / development:

Manual (no plugin):

1. Copy the stack folder into your project root
2. Update CLAUDE.md with your project name and stack versions
3. Copy CLAUDE.local.md.example → CLAUDE.local.md (do not commit)
4. Set your experience level in dev-level.md

Available stacks

Java

JavaScript / TypeScript

Python

.NET / Go / PHP

What's inside each template

Generated files carry a header saying so. Edit the source — policies/ or core/rules/ — and run
tools/govctl build. tools/govctl check fails CI when a generated file was edited by hand.

Load order

Security

security.md loads on every file automatically. It enforces:

- No IDOR: public_id UUID in all URLs, never internal sequential IDs
- No hardcoded secrets: all credentials via…