Use Claude Code like a Director, not a Programmer
Website | Quick Start | Features | Examples | Discord
"Don't write code. Direct Claude to write code for you."
After installing, run these 3 commands:
/getting-started # Guided 5-minute onboarding
/project-init # Auto-detect project and configure
/workflow # Start your first featureNew to Director Mode? Read What is Director Mode? below, or jump to Quick Start.
Compatibility
Director Mode Lite is fully compatible with the latest Claude Code release (Opus 4.6 era), including support for:
- Claude Opus 4.6 model selection in agent/skill frontmatter
- Agent Teams (experimental multi-agent collaboration)
- 1M context window models (
opus[1m],sonnet[1m]) - All 12 hook types including
SessionStart,PreCompact, andPostCompact
Tested with Claude Code CLI as of March 2026. Works with Sonnet 4.6, Opus 4.6, and Haiku 4.5.
Director Mode is a paradigm shift in AI-assisted development. Instead of writing code line by line, you direct Claude to execute your vision autonomously.
Traditional Coding Director Mode
━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━
You: Write code You: Define the vision
AI: Follow orders AI: Execute autonomously
↓ ↓
Micromanagement Strategic oversight
One task at a time Parallel agent execution
Manual intervention Continuous automation
| Principle | Description |
|---|---|
| Efficiency First | Direct execution, minimal interruption |
| Parallel Processing | Multiple agents working simultaneously |
| Autonomous Execution | AI handles implementation details |
| Strategic Oversight | You focus on "what" and "why" |
|
Similar to Ralph Wiggum, Auto-Loop uses Stop hooks but focuses on TDD:
Stop anytime with: touch .auto-loop/stop |
|
|
Self-Evolving Loop takes automation further by:
Key difference from auto-loop:
|
/evolving-loop "Build REST API
Acceptance Criteria:
- [ ] GET /users endpoint
- [ ] POST /users endpoint
- [ ] Input validation
- [ ] Error handling
"
# The loop:
# 1. Analyzes requirements deeply
# 2. Generates custom executor skill
# 3. Executes with TDD
# 4. Validates results
# 5. If fails: learns & evolves skills
# 6. Repeats until all criteria pass
# 7. Ships the final resultCheck status: /evolving-status
/evolving-status --history
/evolving-status --evolution |
See docs/SELF-EVOLVING-LOOP.md for complete documentation.
# 1. Install plugin via Claude Code marketplace
claude plugin install director-mode-lite
# 2. Navigate to your project directory
cd your-project
# 3. Run installation script from cached plugin
~/.claude/plugins/cache/director-mode-lite/director-mode-lite/1.7.2/install.sh .
# 4. Verify installation
~/.claude/plugins/cache/director-mode-lite/director-mode-lite/1.7.2/scripts/verify-install.sh .🔧 Plugin Management Commands
# Update plugin to latest version
claude plugin marketplace update director-mode-lite
claude plugin uninstall director-mode-lite
claude plugin install director-mode-lite
# Check installed plugins
cat ~/.claude/plugins/installed_plugins.json | jq '.'
# View plugin cache
ls -la ~/.claude/plugins/cache/director-mode-lite/director-mode-lite/1.7.2/git clone https://github.com/claude-world/director-mode-lite.git
cd director-mode-lite
./install.sh /path/to/your/projectgit clone https://github.com/claude-world/director-mode-lite.git
cd director-mode-lite
./demo.sh ~/director-mode-demoRun the verifier against the project where you installed Director Mode Lite:
# Plugin install
~/.claude/plugins/cache/director-mode-lite/director-mode-lite/1.7.2/scripts/verify-install.sh .
# Clone install
./scripts/verify-install.sh /path/to/your/projectThe script checks:
CLAUDE.mdplus core.claude/files and directories- Required
CLAUDE.mdsections from the template .claude/skills/and.claude/agents/are populated
It prints colored PASS and FAIL lines, exits 0 when all checks pass, and exits 1 if any check fails.
✨ Installation Features
- Automatic Backup - Backups existing
.claude/to.claude-backup-TIMESTAMP/ - Portable Path Hooks - All hooks use
$CLAUDE_PROJECT_DIRfor portability (no more "file not found" errors) - Smart Merge - Preserves existing settings, only adds new hooks
- Skip Existing - Won't overwrite already-installed commands/agents/skills
- Clean Uninstall -
./uninstall.shremoves all installed files - Automated Tests -
./tests/run-tests.shvalidates installation
|
Workflow:
Setup & Health:
Validators (NEW):
Generators (NEW):
Utilities:
|
Core Agents:
Expert Agents:
Self-Evolving Agents (NEW):
|
Plus:
|
┌─────────────────────────────────────────────────────────────────┐
│ │
│ Step 1 Step 2 Step 3 │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ FOCUS │ ──► │ PREVENT │ ──► │ TEST │ │
│ │ PROBLEM │ │ OVERDEV │ │ FIRST │ │
│ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │ │
│ Understand Only build Red-Green- │
│ before coding what's needed Refactor │
│ │
│ Step 4 Step 5 │
│ ┌─────────┐ ┌─────────┐ │
│ ──► │DOCUMENT │ ──► │ COMMIT │ │
│ └─────────┘ └─────────┘ │
│ │ │ │
│ Auto-generated Conventional │
│ documentation Commits │
│ │
└─────────────────────────────────────────────────────────────────┘
One of Director Mode's key advantages is parallel processing:
|
|
# Old way: Sequential manual searches
grep -r "authentication" src/
grep -r "login" src/
cat src/auth/index.ts
# ... slow, tedious
# Director Mode: One command, 5 parallel agents
/focus-problem "understand the authentication flow"|
Automatically reviews:
Triggers: Code changes, commits, "review" |
5-step debugging:
Triggers: Errors, test failures, "bug" |
Creates and maintains:
Triggers: New features, structure changes |
Director Mode Lite includes 5 Expert Agents that deeply understand Claude Code's official features:
|
Your guide for:
Ask: "How should I structure my CLAUDE.md?" |
Your guide for:
Ask: "How do I add a Notion MCP?" |
Your guide for:
Ask: "Create a security-reviewer agent" |
Your guide for:
Ask: "Make a /deploy command" |
Your guide for:
Ask: "How do I protect .env files?" |
Why? Anthropic provides documentation, but no specialized helpers. These experts know the official docs and help you implement correctly.
Pair with Expert Agents for validate-then-fix or template-then-customize workflows:
|
Validate your configurations and get actionable fix suggestions: /claude-md-check # Check CLAUDE.md structure
/mcp-check # Check MCP settings.json
/agent-check [file.md] # Check agent file format
/skill-check [file.md] # Check skill file format
/hooks-check # Check hooks config + scriptsOutput format: ## Validation Report
### Status: ✅ PASS / ⚠️ WARNINGS / ❌ FAIL
| Check | Status | Notes |
|-------|--------|-------|
| ... | ✅/❌ | ... |
### Issues Found
1. [Issue and recommendation]
### Auto-Fix Available
- Run command X to fix... |
Generate properly-formatted files from templates: /claude-md-template # Generate CLAUDE.md
/agent-template [name] [purpose] # Generate agent
/skill-template [name] [purpose] # Generate skill
/hook-template [type] [purpose] # Generate hookExample: /agent-template security-scanner "scan for vulnerabilities"
# Creates: .claude/agents/security-scanner.md
# with proper frontmatter, activation triggers,
# output format, and guidelinesHook types:
|
The CLAUDE.md file configures Claude's behavior in your project:
# Project: My App
Tech: TypeScript, React, PostgreSQL
# Policies
- Always write tests first
- Use conventional commits
- Document public APIs
# Workflow
- Parallel agents: enabled
- Auto-commit: disabled
- Review before merge: requiredSee docs/CLAUDE-TEMPLATE.md for a complete template.
| Traditional AI Coding | Director Mode Lite | |
|---|---|---|
| Workflow | Ask → Wait → Copy → Test → Repeat | Direct → Auto-execute → Review |
| Parallelism | One task at a time | Multiple agents simultaneously |
| Automation | Manual intervention needed | Auto-Loop runs until done |
| Testing | Often forgotten | TDD built into workflow |
| Documentation | Afterthought | Auto-generated |
Learn by doing with hands-on tutorials:
| Example | Description | Time |
|---|---|---|
| Calculator | Auto-Loop TDD demo | 5 min |
| REST API | Building an API with TDD | 15 min |
| CLI Tool | Command-line tool | 10 min |
| TypeScript Library | Publishable npm library | 20 min |
See examples/ for full tutorials.
|
🌐 Website claude-world.com |
💬 Discord Join the community |
📊 Live Stats Traffic & community growth |
🐛 Issues Report bugs, request features |
| Document | Description |
|---|---|
| FAQ | Common questions answered |
| Concepts | Deep dive into methodology |
| CLAUDE.md Template | Project configuration guide |
| Hooks Guide | Hook implementation reference (12 types) |
| Self-Evolving Loop | Dynamic skill evolution system |
| Development Patterns | Learned best practices |
Other open-source tools from the Claude World community:
| Project | Description | Link |
|---|---|---|
| cf-browser | Cloudflare Browser MCP server for headless browsing, screenshots, and web scraping within Claude Code | github.com/anthropic-community/cf-browser |
| trend-pulse | Real-time trend aggregation MCP server -- monitors 8+ sources (GitHub, Hacker News, Reddit, etc.) for content ideas | github.com/anthropic-community/trend-pulse |
These tools work great alongside Director Mode Lite. Use
cf-browserfor web research agents andtrend-pulsefor staying on top of developer trends.
Lucas Wang (@lukashanren1)
- GitHub: @gn00295120
- Website: claude-world.com
MIT License - Free for personal and commercial use.
See LICENSE for details.
This is a free, open-source toolkit (v1.7.2) from the Claude World community, compatible with the latest Claude Code (Opus 4.6).
|
What's included (FREE):
|
Want more? Visit claude-world.com for:
|
Made with direction by Claude World Taiwan