CLAUDE_MD_TEMPLATE.md Configuration
Complete CLAUDE.md template with sections for project overview, build/run commands, architecture, code style, testing, git workflow, environment variables, constraints, and common gotchas. The foundation of every Claude Code project.
When to use: Copy to CLAUDE.md or .claude/CLAUDE.md when setting up Claude Code on a new project. Customize each section for your stack. This is the first file to create -- it defines how Claude understands and works with your codebase.
RULES_TEMPLATE.md Configuration
Examples of modular rule files for .claude/rules/ with path-scoped frontmatter. Includes templates for code style, testing conventions, database rules, security rules, and API design rules that load on demand when matching files are accessed.
When to use: Use when your CLAUDE.md grows beyond 200 lines or when you need path-specific instructions (different rules for test files vs. source files vs. migration files). Each rule file is a standalone topic.
SETTINGS_PROJECT_TEMPLATE.md Guardrails
Template for .claude/settings.json with permission allow/deny lists and hook configurations. Includes auto-formatting on edit, destructive command blocking, sensitive file protection, and notification hooks. Shared with the team via version control.
When to use: Copy the JSON to .claude/settings.json to establish team-wide guardrails. Customize permissions for your package manager and tools. Adjust hooks for your formatter. This is the enforcement layer -- CLAUDE.md is advisory, settings are deterministic.
SETTINGS_LOCAL_TEMPLATE.md Guardrails
Template for .claude/settings.local.json with personal permission overrides and OS-specific notification hooks. Includes macOS and Linux notification examples. This file is gitignored and overrides project settings for the current user.
When to use: Copy to .claude/settings.local.json for personal preferences that should not be shared (push permissions, OS-specific notifications, personal tool allowlists). Add .claude/settings.local.json to .gitignore.
MEMORY_TEMPLATE.md Memory
Complete memory system reference with MEMORY.md index format and individual memory file templates for all four types: user (role and preferences), feedback (corrections and confirmations), project (ongoing work context), and reference (external system pointers).
When to use: Reference when understanding how Claude Code's auto-memory works, when manually creating memory entries, or when onboarding a team to the memory system. Claude maintains memory automatically, but understanding the format helps you curate it.
HOOKS_REFERENCE.md Guardrails
Comprehensive hook recipe collection with copy-paste JSON configurations. Includes auto-formatters (Prettier, Biome, dart format, Black), destructive command blockers, sensitive file protectors, lint-on-edit hooks, notification hooks, and environment reload hooks.
When to use: Reference when configuring hooks in .claude/settings.json. Find the hook recipe for your tool, copy the JSON, and customize. Covers the most common hook patterns across multiple languages and frameworks.
GITHUB_WORKFLOW_TEMPLATE.md GitHub
GitHub Actions workflow for Claude Code integration. Enables @claude mentions in issues and PR comments to trigger Claude Code for implementation, code review, and bug fixes. Includes configurations for Anthropic API, AWS Bedrock, and Google Vertex AI.
When to use: Copy the YAML to .github/workflows/claude.yml to enable GitHub-based Claude Code automation. Requires the Claude GitHub App and an ANTHROPIC_API_KEY in repository secrets. Set up once per repository.
PR_TEMPLATE.md GitHub
Pull request template with structured sections for summary, change type classification, testing checklist, security checklist, environment impact assessment, related issues, and reviewer notes. Ensures consistent, reviewable PRs from both humans and Claude.
When to use: Copy to .github/pull_request_template.md to standardize PR descriptions across the team. Particularly valuable when Claude Code creates PRs -- the template ensures AI-generated PRs include security checks and test plans.
ISSUE_BUG_TEMPLATE.md GitHub
Bug report issue template with structured fields for description, reproduction steps, expected vs. actual behavior, environment details, severity classification, and logs/screenshots. Provides Claude Code with the context needed to fix bugs from issue descriptions.
When to use: Copy to .github/ISSUE_TEMPLATE/bug_report.md. When bug reports follow this structure, Claude Code can read the issue via @claude and implement fixes with full context about the problem, environment, and severity.
ISSUE_FEATURE_TEMPLATE.md GitHub
Feature request issue template with fields for problem statement, proposed solution, user story, acceptance criteria, technical considerations, design mockups, alternatives considered, and priority. Gives Claude Code clear requirements for feature implementation.
When to use: Copy to .github/ISSUE_TEMPLATE/feature_request.md. Well-structured feature requests with acceptance criteria enable Claude Code to implement features directly from @claude mentions on issues.
AGENTS_TEMPLATE.md Extensibility
Custom subagent definitions for .claude/agents/ with examples for security reviewer, test writer, PR reviewer, and migration writer agents. Each agent has focused tools, clear instructions, and a specific responsibility.
When to use: Copy agent definitions to .claude/agents/ when you want Claude to delegate specialized tasks to focused subagents. Particularly valuable for security review, test generation, and code review workflows that benefit from isolated, focused analysis.
SKILLS_TEMPLATE.md Extensibility
Custom slash-command workflow definitions for .claude/skills/ with examples for fix-issue (end-to-end issue resolution with PR), review-pr (structured code review), release-notes (automated changelog generation), and scaffold (feature module creation).
When to use: Copy skill definitions to .claude/skills/ when you have repeatable multi-step workflows. Skills turn complex procedures (fix a GitHub issue, review a PR, generate release notes) into single slash commands that Claude executes consistently.
PROJECT_SETUP_GUIDE.md Guide
Step-by-step guide for configuring a complete Claude Code project. Covers the full directory structure, setup sequence (CLAUDE.md, settings, rules, agents, skills, GitHub integration), verification steps, gitignore additions, and ongoing maintenance tasks.
When to use: Follow this guide when setting up Claude Code on a new or existing repository for the first time. It ties all the other templates together into a coherent setup sequence. Also useful as a checklist when auditing an existing Claude Code configuration.