claude-code-starter
CLAUDE.md16 starsChanged 10 months agoMITView on GitHub
A starter template for setting up Claude Code in any project. This is a template repo - clone it and run ./setup.sh to configure Claude Code for your project. When working in this repo: - Write clear, readable code - Use descriptive names - Keep functions small and focused - Follow existing patterns in the codebase Before committing changes, always: 1. Show the user what files are being committed 2. Briefly explain the key changes 3. Ask for confirmation before…
- Reads credentials
We split this CLAUDE.md into the rules it gives an agent
19 rules. About 0 are common, 15 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
When working in this repo:
- Distinctive: line 12
Write clear, readable code
- Distinctive: line 14
Keep functions small and focused
- Distinctive: line 15
Follow existing patterns in the codebase
- Distinctive: line 19
Never commit secrets or credentials
- Distinctive: line 21
Use environment variables for sensitive config
- Distinctive: line 27
Before committing changes, always:
- Distinctive: line 30
Ask for confirmation before proceeding
- Distinctive: line 39
/status: Check git state and recent activity
- Very specific: line 50
wiggum: Start autonomous implementation loop from spec/PRD (/wiggum)
- Very specific: line 51
refresh-claude: Update CLAUDE.md with recent changes (/refresh-claude)
- Very specific: line 54
risk-register: Document risks for auth/data/migration changes (/risk-register)
- Distinctive: line 58
Use these specialized agents for focused tasks:
- Distinctive: line 64
adr-writer: Create Architecture Decision Records for significant decisions
- Distinctive: line 73
Consults researcher: when stuck
- Distinctive: line 81
Commits incrementally: after each chunk passes all gates
- Distinctive: line 83
Final verification: - All command gates, smoke test, production hygiene
- Distinctive: line 84
Only finishes: when ALL gates pass AND all agents approve
- Very specific: line 144
After cloning, replace this CLAUDE.md with your project-specific version.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code Starter
A starter template for setting up Claude Code in any project.
This Repository
This is a template repo - clone it and run ./setup.sh to configure Claude Code for your project.
Code Style
When working in this repo:
- Write clear, readable code
- Use descriptive names
- Keep functions small and focused
- Follow existing patterns in the codebase
Security
- Never commit secrets or credentials
- Validate all external input
- Use environment variables for sensitive config
.envand.env.*files are blocked from reading (see.claude/settings.json)- See
.claude/rules/security-model.mdfor full security documentation
Commit Review
Before committing changes, always:
- Show the user what files are being committed
- Briefly explain the key changes
- Ask for confirmation before proceeding
This prevents "vibe coding" - blindly committing AI-generated changes without review.
Quick Commands
Simple workflow commands invoked with /<command> [arguments]:
- /onboard [area]: Quick project orientation and overview
- /pr-summary: Generate PR description from current changes
- /status: Check git state and recent activity
Available Skills
Skills are invoked automatically when your request matches their description:
- code-review: Review code changes for quality and security
- explain-code: Explain how code works
- generate-tests: Generate comprehensive tests
- refactor-code: Improve code without changing behavior
- review-mr: Review merge/pull requests
- install-precommit: Install the pre-commit review hook
- wiggum: Start autonomous implementation loop from spec/PRD (
/wiggum) - refresh-claude: Update CLAUDE.md with recent changes (
/refresh-claude) - changelog-writer: Maintain CHANGELOG.md with categorized entries (
/changelog-writer) - release-checklist: Final quality gate before shipping (
/release-checklist) - risk-register: Document risks for auth/data/migration changes (
/risk-register)
Available Agents
Use these specialized agents for focused tasks:
- researcher: Explore and understand code (read-only)
- code-reviewer: Thorough code reviews
- code-simplifier: Simplify code for clarity and maintainability
- test-writer: Generate comprehensive tests
- documentation-writer: Generate and update documentation for code changes
- adr-writer: Create Architecture Decision Records for significant decisions
Wiggum Skill
The wiggum skill (inspired by the Ralph Wiggum technique) takes a specification or PRD and autonomously implements it to completion. It coordinates with specialized agents and enforces production-ready quality gates:
Workflow:
- Plans first - Enters plan mode, identifies commands from CLAUDE.md, gets user approval
- Implements iteratively in small chunks (blast-radius awareness)
- Consults researcher when stuck
- Documents decisions with adr-writer for significant choices
- Validates dependencies - Checklist for any new packages (license, security, maintenance)
- Uses test-writer for comprehensive test coverage
- Gets code-reviewer feedback (includes security checklist)
- Applies code-simplifier for clarity
- Updates documentation with documentation-writer
- Runs command gates per chunk (test, lint, typecheck)
- Commits incrementally after each chunk passes all gates
- Maintains changelog with changelog-writer
- Final verification - All command gates, smoke test, production hygiene
- Only finishes when ALL gates pass AND all agents approve
Invoke via: /wiggum "implement feature X per this spec..."
Project Structure
.claude/
├── settings.json # Permissions, hooks
├── commands/ # Quick workflow commands
│ ├── onboard.md
│ ├── pr-summary.md
│ └── status.md
├── skills/ # Custom skills (YAML frontmatter + instructions)
│ ├── code-review/SKILL.md
│ ├── explain-code/SKILL.md
│ ├── generate-tests/SKILL.md
│ ├── refactor-code/SKILL.md
│ ├── review-mr/SKILL.md
│ ├── install-precommit/SKILL.md
│ ├── refresh-claude/SKILL.md
│ ├── wiggum/SKILL.md
│ ├── changelog-writer/SKILL.md
│ ├── release-checklist/SKILL.md
│ └── risk-register/SKILL.md
├── agents/ # Specialized subagents
│ ├── researcher.md
│ ├── code-reviewer.md
│ ├── code-simplifier.md
│ ├── test-writer.md
│ ├── documentation-writer.md
│ └── adr-writer.md
├── hooks/ # Automation scripts
│ ├── validate-bash.sh # Pre-command validation
│ ├── auto-format.sh # Post-edit formatting
│ └── pre-commit-review.sh # Git pre-commit hook
└── rules/ # Documentation (not auto-loaded)
├── code-style.md
├── git.md
├── quality-gates.md
├── security.md
├── security-model.md
└── testing.md
stacks/ # Stack-specific presets (starter repo only)
├── typescript/
├── python/
├── go/
├── rust/
├── ruby/
└── elixir/Commands
./setup.sh # Interactive setup for any projectFor Users
After cloning, replace this CLAUDE.md with your project-specific version.
See CLAUDE.template.md for a starting point.
In this repository12 other files it gives its agents.
- docs/agents.mdAGENTS.md
- changelog-writerSkill
- code-reviewSkill
- explain-codeSkill
- generate-testsSkill
- install-precommitSkill
- refactor-codeSkill
- refresh-claudeSkill
- release-checklistSkill
- review-mrSkill
- risk-registerSkill
- wiggumSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

