Production-ready configurations, skills, and templates for Claude Code optimization
Go build and compilation error resolution specialist. Diagnoses and fixes build failures, type errors, and module dependency issues in Go projects. Use when Go build or test commands fail.
Go code review specialist. Reviews Go code for idioms, error handling, concurrency patterns, and ecosystem best practices. Use when reviewing Go projects or significant Go changes.
Implementation planning specialist. Analyzes requirements, identifies risks, and creates actionable step-by-step plans. Use PROACTIVELY when starting new features or making significant changes. WAITS for confirmation before coding.
Python code review specialist. Reviews Python code for idioms, type safety, performance, and ecosystem best practices. Use when reviewing Python projects or significant Python changes.
Dead code removal and refactoring specialist. Identifies unused code, redundant patterns, and opportunities for simplification. Use periodically or after feature completion to keep the codebase lean.
Safe refactoring patterns and techniques. Use when the user wants to improve code structure, reduce duplication, or make code more maintainable without changing behavior. Emphasizes incremental changes with test coverage.
Test-driven development patterns for Spring Boot 3.x. Covers JUnit 5, MockMvc, Testcontainers, service mocking with Mockito, slice tests, integration tests, and test configuration management.
Git branching strategies and workflows. Use when setting up a project's branching model, discussing Git workflow, or deciding between trunk-based and Git Flow approaches.
Generate changelog entries following Keep a Changelog format
Write clear, conventional commit messages. Use when the user asks to commit changes, needs help with commit messages, or when following Conventional Commits specification is required.
Matches all tools
Hooks run on every tool call, not just specific ones
Uses power tools
Uses Bash, Write, or Edit tools
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
╭──────────────────────────────────────────╮
│ │
│ claude-dotfiles │
│ │
│ 🧠 Give Claude Code a Memory 🧠 │
│ │
╰──────────────────────────────────────────╯
Production-ready configurations for Claude Code
Quick Start • Why This Exists • What's Included • Documentation
Without configuration, Claude Code starts every session with zero context about your project:
You: "Run the tests"
Claude: "What test framework do you use? What's the command?"
You: "Use our API client"
Claude: "I don't see an API client. Where is it located?"
You: "Follow our coding standards"
Claude: "What are your coding standards?"
With claude-dotfiles, Claude remembers everything:
You: "Run the tests"
Claude: *runs `pytest -v`*
You: "Use our API client"
Claude: *imports from src/lib/api.ts*
You: "Follow our coding standards"
Claude: *uses your error handling pattern, naming conventions, etc.*
One-time setup. Permanent memory.
30 seconds to a smarter Claude:
# Clone and install
git clone https://github.com/peopleforrester/claude-dotfiles.git ~/.claude-dotfiles
cd ~/.claude-dotfiles
./install.sh
# Copy a template to your project
cp templates/standard/CLAUDE.md ~/your-project/CLAUDE.md
# Edit it for your project
# Then start Claude Code - it now knows your project!
One-command install (when public):
curl -fsSL https://raw.githubusercontent.com/peopleforrester/claude-dotfiles/main/install.sh | bash
Windows (PowerShell):
irm https://raw.githubusercontent.com/peopleforrester/claude-dotfiles/main/install.ps1 | iex
Using Make:
make install # Interactive
make install-all # Everything
make install-minimal # Just essentials
| You Get | What It Does | Files |
|---|---|---|
| CLAUDE.md Templates | Tell Claude about your project's stack, commands, and conventions | 15 templates |
| Rules | Always-follow constraints (common + language-specific) | 21 rules |
| Agents | Specialized personas (planner, architect, reviewers, spec-interviewer) | 15 agents |
| Skills | User-invocable slash commands AND pattern libraries (commands merged into skills in 0.5.0) | 70 skills |
| Hooks | Automate actions (format on save, notifications) | 14 hooks |
| Settings | Control what Claude can do automatically | 3 profiles |
| MCP Configs | Connect Claude to GitHub, databases, Slack | 10 configs |
| Template | Best For | Get Started |
|---|---|---|
| Minimal | Quick projects, learning | cp templates/minimal/CLAUDE.md . |
| Standard | Most projects ⭐ | cp templates/standard/CLAUDE.md . |
| Power User | Full automation | cp -r templates/power-user/.* . |
| Stack | Template |
|---|---|
| React + TypeScript | templates/stacks/react-typescript/ |
| Python + FastAPI | templates/stacks/python-fastapi/ |
| Next.js Fullstack | templates/stacks/nextjs-fullstack/ |
Browse claude-md/ for templates covering:
Rules are always-loaded constraints organized in a modular structure:
Common rules (apply to all projects):
npx claudepluginhub peopleforrester/claude-dotfilesSpec-driven development for Claude Code via 4 markdown skills: brain-init, brain-spec, brain-task, brain-status. Zero startup cost; all schemas and templates embedded in SKILL.md.
Commands for loading context and priming Claude for specific tasks
Commands for syncing CLAUDE.md, permissions allowlist, and refreshing context. Hooks for marketplace-to-plugin sync.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Interactive setup wizard for configuring any repository with Claude Code best practices, based on Boris Cherny's workflow
Automation bootstrap for Claude Code. Analyzes any project and generates a complete .claude/ structure with agents, pipelines, skills, memory, hooks, and settings.
Claude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration