My Personal Claude Code Development Kit

4 months ago 1

An integrated system that transforms Claude Code into an orchestrated development environment through automated documentation management, multi-agent workflows, and external AI expertise.

Ever tried to build a large project with AI assistance, only to watch it struggle as your codebase grows?

Claude Code's output quality directly depends on what it knows about your project. As AI-assisted development scales, three critical challenges emerge:

Challenge 1: Context Management

The Problem:

❌ Loses track of your architecture patterns and design decisions ❌ Forgets your coding standards and team conventions ❌ No guidance on where to find the right context in large codebases

The Solution: ✅ Automated context delivery through two integrated systems:

3-tier documentation system - Auto-loads the right docs at the right time
Custom commands with sub-agents - Orchestrates specialized agents that already know your project
Result: No manual context loading, consistent knowledge across all agents

Challenge 2: AI Reliability

The Problem:

❌ Outdated library documentation ❌ Hallucinated API methods ❌ Inconsistent architectural decisions

The Solution: ✅ "Four eyes principle" through MCP integration:

Service Purpose Benefit

Context7	Real-time library docs	Current APIs, not training data
Gemini	Architecture consultation	Cross-validation & best practices

Result: Fewer errors, better code, current standards

Challenge 3: Automation Without Complexity

The Problem:

❌ Manual context loading for every session ❌ Repetitive command sequences ❌ No feedback when tasks complete

The Solution: ✅ Intelligent automation through hooks and commands:

Automatic updates of documentation through custom commands
Context injection for all Sub-agents and Gemini MCP calls
Audio notifications for task completion (optional)
One-command workflows for complex tasks

Claude Code transforms from a helpful tool into a reliable development partner that remembers your project context, validates its own work, and handles the tedious stuff automatically.

Required: Claude Code
Recommended: MCP servers like Context7 and Gemini Assistant

Option 1: Quick Install (Recommended)

Run this single command in your terminal:

curl -fsSL https://raw.githubusercontent.com/peterkrueck/Claude-Code-Development-Kit/main/install.sh | bash

This will:

Download the framework
Guide you through an interactive setup
Install everything in your chosen project directory
Provide links to optional MCP server installations

Claude.Code.Development.Kit.-.Setup.mov

Option 2: Clone and Install

git clone https://github.com/peterkrueck/Claude-Code-Development-Kit.git cd Claude-Code-Development-Kit ./setup.sh

The setup script will create the following structure in your project:

your-project/ ├── commands/ # AI orchestration templates (.md files) ├── hooks/ # Automation scripts │ ├── config/ # Security patterns configuration │ ├── sounds/ # Notification sounds (if notifications enabled) │ └── *.sh # Hook scripts (based on your selections) ├── docs/ # Documentation templates and examples │ ├── ai-context/ # Core documentation files │ ├── open-issues/ # Issue tracking examples │ └── specs/ # Specification templates ├── logs/ # Hook execution logs (created at runtime) ├── .claude/ │ └── settings.local.json # Generated Claude Code configuration ├── CLAUDE.md # Your project's AI context (from template) └── MCP-ASSISTANT-RULES.md # MCP coding standards (if Gemini-Assistant-MCP selected)

Note: The exact files installed depend on your choices during setup (MCP servers, notifications, etc.)

Customize your AI context:
- Edit CLAUDE.md with your project standards
- Update docs/ai-context/project-structure.md with your tech stack
Install MCP servers (if selected during setup):
- Follow the links provided by the installer
- Configure in .claude/settings.local.json
Test your installation:

claude /full-context "analyze my project structure"

CLAUDE.md - Master context files containing project-specific AI instructions, coding standards, and integration patterns
CONTEXT.md - Component and feature-level documentation files (Tier 2 and Tier 3) that provide specific implementation details and patterns
MCP (Model Context Protocol) - Standard for integrating external AI services with Claude Code
Sub-agents - Specialized AI agents spawned by Claude Code to work on specific aspects of a task in parallel
3-Tier Documentation - Hierarchical organization (Foundation/Component/Feature) that minimizes maintenance while maximizing AI effectiveness
Auto-loading - Automatic inclusion of relevant documentation when commands execute
Hooks - Shell scripts that execute at specific points in Claude Code's lifecycle for security, automation, and UX enhancements

Integrated Intelligence Loop

CLAUDE CODE ┌─────────────────┐ │ │ │ COMMANDS │ │ │ └────────┬────────┘ Multi-agent│orchestration Parallel │execution Dynamic │scaling ╱│╲ ╱ │ ╲ Routes agents ╱ │ ╲ Leverages to right docs ╱ │ ╲ expertise ╱ │ ╲ ▼ │ ▼ ┌─────────────────┐│┌─────────────────┐ │ │││ │ │ DOCUMENTATION │││ MCP SERVERS │ │ │││ │ └─────────────────┘│└─────────────────┘ 3-tier structure │ Context7 + Gemini Auto-loading │ Real-time updates Context routing │ AI consultation ╲ │ ╱ ╲ │ ╱ Provides project╲ │ ╱ Enhances with context for ╲ │ ╱ current best consultation ╲ │ ╱ practices ╲│╱ ▼ Integrated Workflow

Every command execution automatically loads critical documentation:

@/CLAUDE.md # Master AI context and coding standards @/docs/ai-context/project-structure.md # Complete technology stack and file tree @/docs/ai-context/docs-overview.md # Documentation routing map

The subagent-context-injector.sh hook extends auto-loading to all sub-agents:

Sub-agents spawned via the Task tool automatically receive the same core documentation
No manual context inclusion needed in Task prompts
Ensures consistent knowledge across all agents in multi-agent workflows

This ensures:

Consistent AI behavior across all sessions and sub-agents
Zero manual context management at any level

Commands ↔️ Documentation

Commands determine which documentation tiers to load based on task complexity
Documentation structure guides agent spawning patterns
Commands update documentation to maintain current context

Commands ↔️ MCP Servers

Context7 provides up-to-date library documentation
Gemini offers architectural consultation for complex problems
Integration happens seamlessly within command workflows

Documentation ↔️ MCP Servers

Project structure and MCP assistant rules auto-attach to Gemini consultations
Ensures external AI understands specific architecture and coding standards
Makes all recommendations project-relevant and standards-compliant

The kit includes battle-tested hooks that enhance Claude Code's capabilities:

Security Scanner - Prevents accidental exposure of secrets when using MCP servers
Gemini Context Injector - Automatically includes project structure in Gemini consultations
Subagent Context Injector - Ensures all sub-agents receive core documentation automatically
Notification System - Provides non-blocking audio feedback for task completion and input requests (optional)

These hooks integrate seamlessly with the command and MCP server workflows, providing:

Pre-execution security checks for all external AI calls
Automatic context enhancement for both external AI and sub-agents
Consistent knowledge across all agents in multi-agent workflows
Developer awareness through pleasant, non-blocking audio notifications

Starting New Feature Development

/full-context "implement user authentication across backend and frontend"

The system:

Auto-loads project documentation
Spawns specialized agents (security, backend, frontend)
Consults Context7 for authentication framework documentation
Asks Gemini 2.5 pro for feedback and improvement suggestions
Provides comprehensive analysis and implementation plan

Code Review with Multiple Perspectives

/code-review "review authentication implementation"

Multiple agents analyze:

Security vulnerabilities
Performance implications
Architectural alignment
Integration impacts

Maintaining Documentation Currency

/update-docs "document authentication changes"

Automatically:

Updates affected CLAUDE.md files across all tiers
Keeps project-structure.md and docs-overview.md up-to-date
Maintains context for future AI sessions
Ensures documentation matches implementation

Creating Your Project Structure

After installation, you'll add your own project-specific documentation:

your-project/ ├── .claude/ │ ├── commands/ # AI orchestration templates │ ├── hooks/ # Security and automation hooks │ │ ├── config/ # Hook configuration files │ │ ├── sounds/ # Notification audio files │ │ ├── gemini-context-injector.sh │ │ ├── mcp-security-scan.sh │ │ ├── notify.sh │ │ └── subagent-context-injector.sh │ └── settings.json # Claude Code configuration ├── docs/ │ ├── ai-context/ # Foundation documentation (Tier 1) │ │ ├── docs-overview.md # Documentation routing map │ │ ├── project-structure.md # Technology stack and file tree │ │ ├── system-integration.md # Cross-component patterns │ │ ├── deployment-infrastructure.md # Infrastructure context │ │ └── handoff.md # Session continuity │ ├── open-issues/ # Issue tracking templates │ ├── specs/ # Feature specifications │ └── README.md # Documentation system guide ├── CLAUDE.md # Master AI context (Tier 1) ├── backend/ │ └── CONTEXT.md # Backend context (Tier 2) - create this └── backend/src/api/ └── CONTEXT.md # API context (Tier 3) - create this

The framework provides templates for CONTEXT.md files in docs/:

docs/CONTEXT-tier2-component.md - Use as template for component-level docs
docs/CONTEXT-tier3-feature.md - Use as template for feature-level docs

The kit is designed for adaptation:

Commands - Modify orchestration patterns in .claude/commands/
Documentation - Adjust tier structure for your architecture
MCP Integration - Add additional servers for specialized expertise
Hooks - Customize security patterns, add new hooks, or modify notifications in .claude/hooks/
MCP Assistant Rules - Copy docs/MCP-ASSISTANT-RULES.md template to project root and customize for project-specific standards

Let documentation guide development - The 3-tier structure reflects natural boundaries
Update documentation immediately - Use /update-docs after significant changes
Trust the auto-loading - Avoid manual context management
Scale complexity naturally - Simple tasks stay simple, complex tasks get sophisticated analysis