mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-02-13 01:43:10 +08:00
86b5a53e5d
* refactor(rules): restructure rules into common + language-specific directories - Split 8 flat rule files into common/, typescript/, python/, golang/ - common/ contains language-agnostic principles (no code examples) - typescript/ extracts TS/JS specifics (Zod, Playwright, Prettier hooks, etc.) - python/ adds Python rules (PEP 8, pytest, black/ruff, bandit) - golang/ adds Go rules (gofmt, table-driven tests, gosec, functional options) - Replace deprecated ultrathink with extended thinking documentation - Add README.md with installation guide and new-language template Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix installation commands for rules Updated installation instructions to copy all rules to a single directory. * docs: update README.md to reflect new rules directory structure Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Hor1zonZzz <Hor1zonZzz@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
50 lines
1.5 KiB
Markdown
50 lines
1.5 KiB
Markdown
# Agent Orchestration
|
|
|
|
## Available Agents
|
|
|
|
Located in `~/.claude/agents/`:
|
|
|
|
| Agent | Purpose | When to Use |
|
|
|-------|---------|-------------|
|
|
| planner | Implementation planning | Complex features, refactoring |
|
|
| architect | System design | Architectural decisions |
|
|
| tdd-guide | Test-driven development | New features, bug fixes |
|
|
| code-reviewer | Code review | After writing code |
|
|
| security-reviewer | Security analysis | Before commits |
|
|
| build-error-resolver | Fix build errors | When build fails |
|
|
| e2e-runner | E2E testing | Critical user flows |
|
|
| refactor-cleaner | Dead code cleanup | Code maintenance |
|
|
| doc-updater | Documentation | Updating docs |
|
|
|
|
## Immediate Agent Usage
|
|
|
|
No user prompt needed:
|
|
1. Complex feature requests - Use **planner** agent
|
|
2. Code just written/modified - Use **code-reviewer** agent
|
|
3. Bug fix or new feature - Use **tdd-guide** agent
|
|
4. Architectural decision - Use **architect** agent
|
|
|
|
## Parallel Task Execution
|
|
|
|
ALWAYS use parallel Task execution for independent operations:
|
|
|
|
```markdown
|
|
# GOOD: Parallel execution
|
|
Launch 3 agents in parallel:
|
|
1. Agent 1: Security analysis of auth module
|
|
2. Agent 2: Performance review of cache system
|
|
3. Agent 3: Type checking of utilities
|
|
|
|
# BAD: Sequential when unnecessary
|
|
First agent 1, then agent 2, then agent 3
|
|
```
|
|
|
|
## Multi-Perspective Analysis
|
|
|
|
For complex problems, use split role sub-agents:
|
|
- Factual reviewer
|
|
- Senior engineer
|
|
- Security expert
|
|
- Consistency reviewer
|
|
- Redundancy checker
|