Step-by-step guide to set up project-specific Claude Code configuration.
mkdir -p .claude/{commands,agents,rules/{common,infrastructure},skills,hooks/{pre-tool-use,post-tool-use,stop}}Create .claude/settings.local.json (see implementation/project/settings.local.json.example):
- Add
$schemafor IDE validation - Add
plansDirectoryif custom plan location needed - Add
attributionsettings for commits/PRs - Add
statuslineconfiguration - Add
alwaysThinkingEnabledif desired - Add
outputStylepreferences (explanatory for Insight boxes)
Copy commands from implementation/project/commands/:
start-ticket.mdraise-pr.mdplan.mdtdd.mdrefactor-clean.md
Copy rules from implementation/project/rules/:
common/git-workflow.mdcommon/code-style.mdinfrastructure/terraform-patterns.mdinfrastructure/secrets-management.mdinfrastructure/style-verification.mdworkflows.mdmcp-servers.mdbuilt-in-features.mdadvanced-features.mdcli-reference.mdREADME.md
Copy hooks from implementation/project/hooks/:
pre-tool-use/dev-server-block.mdpre-tool-use/git-push-reminder.mdpost-tool-use/prettier-format.mdstop/console-log-check.md
Copy implementation/project/WORKFLOWS.md to .claude/WORKFLOWS.md (or create based on your project needs)
Create .claude/.mcp.json (see implementation/project/.mcp.json.example):
- Replace all secrets with environment variables
- Configure project-specific MCPs (postgres, terraform, expo, etc.)
Create .claude/CLAUDE.local.md with project-specific instructions (see implementation/project/CLAUDE.local.md for example).
claude --version
# Test a command
claude /start-ticket 1- Adapt commands to your project's needs
- Add project-specific agents
- Configure project-specific MCP servers
- Customize rules for your tech stack
- See best-practice/ for configuration patterns
- See workflows/ for workflow examples