This directory contains the core configuration and extensions that transform Claude Code from a coding assistant into a complete development platform.
.claude/
├── agents/ # AI agents that assist with various tasks
├── commands/ # Custom commands that extend Claude Code
├── tools/ # Shell scripts for automation and notifications
├── docs/ # Deep-dive documentation
├── settings.json # Claude Code configuration
└── README.md # This file
The agents/ directory contains the AI agents that assist with various tasks within Claude Code.
- Each
.mdfile defines a specific agent and its capabilities. - The agents can be composed together to handle more complex tasks.
- Agents can also share data and context with each other.
The commands/ directory contains markdown files that define custom workflows:
- Each
.mdfile becomes a slash command in Claude Code - Commands can orchestrate complex multi-step processes
- They encode best practices and methodologies
- Key commands include
/transcriptsfor restoring conversation history after compaction
The tools/ directory contains scripts that integrate with Claude Code:
notify.sh- Cross-platform desktop notificationsmake-check.sh- Intelligent quality check runnersubagent-logger.py- Logs interactions with sub-agentshook_precompact.py- Exports conversation transcripts before compactiontranscript_manager.py- CLI tool for managing conversation transcripts- Triggered by hooks defined in
settings.json
settings.json defines:
- Hooks: Automated actions after specific events
- Permissions: Allowed commands and operations
- MCP Servers: Extended capabilities
- You make a code change in Claude Code
- PostToolUse hook triggers
make-check.sh - Quality checks run automatically
- Notification hook triggers
notify.sh - You get desktop notification of results
- If sub-agents were used,
subagent-logger.pylogs their interactions to.data/subagents-logs - Before conversation compaction, PreCompact hook triggers
hook_precompact.py - Full transcript is exported to
.data/transcripts/preserving your entire conversation
- You type
/command-namein Claude Code - Claude reads the command definition
- Executes the defined process
- Can spawn sub-agents for complex tasks
- Returns results in structured format
/primecommand loads philosophy documents- These guide all subsequent AI interactions
- Ensures consistent coding style and decisions
- Philosophy becomes executable through commands
Options:
- [Preferred]: Create via Claude Code:
- Use the
/agentscommand to define the agent's capabilities. - Provide the definition for the agent's behavior and context.
- Let Claude Code perform its own optimization to improve the agent's performance.
- Use the
- [Alternative]: Create manually:
- Define the agent in a new
.mdfile withinagents/. - Include all necessary context and dependencies.
- Must follow the existing agent structure and guidelines.
- Define the agent in a new
Create a new file in commands/:
## Usage
`/your-command <args>`
## Context
- What this command does
- When to use it
## Process
1. Step one
2. Step two
3. Step three
## Output Format
- What the user sees
- How results are structuredEdit settings.json:
{
"hooks": {
"YourEvent": [
{
"matcher": "pattern",
"hooks": [
{
"type": "command",
"command": "your-script.sh"
}
]
}
]
}
}- Create script in
tools/ - Make it executable:
chmod +x tools/your-tool.sh - Add to hooks or commands as needed
- Minimal Intrusion: Stay in
.claude/to not interfere with user's project - Cross-Platform: Everything works on Mac, Linux, Windows, WSL
- Fail Gracefully: Scripts handle errors without breaking workflow
- User Control: Easy to modify or disable any feature
- Team Friendly: Configurations are shareable via Git