Enterprise Dev Config
Guard rails for teams that need PR reviews and audit trails
$9Starter SkillFor specialists, founders, and lean teams
What is Enterprise Dev Config?
A comprehensive CLAUDE.md for engineering teams at companies with compliance requirements. Includes branch protection rules, PR template enforcement, commit signing expectations, security scanning gates, and documentation requirements. Covers monorepo conventions, service ownership, and incident response protocols.
Setup Time
5 min
Difficulty
Advanced
Works With
claude-code
What's Included
- CLAUDE.md
- conventions/branch-strategy.md
- conventions/pr-template.md
- conventions/commit-signing.md
- conventions/service-ownership.md
- security/scanning-gates.md
- security/secret-handling.md
- templates/incident-report.md
- templates/design-doc.md
- README.md
Preview
CLAUDE.md
# CLAUDE.md — Enterprise Dev Config
## Branch Strategy
- `main` is protected — no direct commits
- Feature branches: `feat/<ticket-id>-<description>`
- Hotfix branches: `fix/<ticket-id>-<description>`
- All PRs require 1 approval + passing CI
## Security Requirements
- NEVER commit secrets, tokens, or API keys
- NEVER disable ESLint rules without team approval
- Run `bun run security-scan` before every PR
- Flag any new dependency additions for review
## PR Checklist (all must pass)
- [ ] Tests cover new code paths
- [ ] No TODO without a linked ticket
- [ ] CHANGELOG.md updated for user-facing changes
- [ ] API changes have migration guideInstallation Guide
1
Copy config to project root
cp enterprise-dev/CLAUDE.md ./CLAUDE.md2
Start Claude Code — config loads automatically
claudeRelated Products
CLAUDE.md ConfigFree
DevOps/SRE Config
A CLAUDE.md for DevOps teams with incident and change management
CLAUDE.md ConfigFree
Content Creator Config
A CLAUDE.md tuned for writing, editing, and publishing workflows
CLAUDE.md Config$9
Customer Success Config
A CLAUDE.md for proactive, retention-focused customer management
CLAUDE.md Config$9
Data Science Config
A CLAUDE.md for data science workflows with experiment tracking