Solo Unicorn Club logo

CLAUDE.md Configs

Enterprise Dev Config

Guard rails for teams that need PR reviews and audit trails

// First 7 days

What can be running fast.

01

Get a ready-to-run system that replaces blank-page setup.

02

Ship a usable package with 10 included files and working structure.

03

Move from purchase to first setup in about 5 min.

// Included files

What is inside the package.

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

Description

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.

claude-code

Upgrade path

  • 01Start with this package and validate the workflow.
  • 02Add specialized skills or bundles once the core system is stable.
  • 03Use the community to sharpen positioning, demos, and feedback loops.
PreviewCLAUDE.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 guide

// Community acceleration

Use the room after the purchase.

Bring your workflow into the Solo Unicorn community for sharper feedback, operator critique, and more visibility once the system is live.

Discuss implementation