shancheas
0b0bdd9c4b
- Introduced backend patterns skill with guidelines on API design, database optimization, and server-side best practices. - Added coding standards skill outlining universal coding principles for TypeScript, NestJS, and Node.js development. - Implemented continuous learning skill to automatically extract reusable patterns from Cursor sessions. - Created NestJS best practices skill detailing architecture patterns, dependency injection, error handling, and security measures. - Included various rules and templates for NestJS best practices to ensure production-ready applications.
65 lines
2.0 KiB
Plaintext
65 lines
2.0 KiB
Plaintext
---
|
|
description: When to use planner, architect, tdd-guide, code-reviewer, and other agents; parallel Task execution
|
|
alwaysApply: true
|
|
---
|
|
|
|
# Agent Orchestration
|
|
|
|
## Layout
|
|
|
|
- Agents: `.cursor/agents/`
|
|
- Skills: `.agents/skills/`
|
|
- Rules: `.cursor/rules/`
|
|
- Hooks: `.cursor/hooks.json` and `.cursor/hooks/`
|
|
|
|
## Available 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 | NestJS E2E testing | Critical API 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.ts
|
|
2. Agent 2: Performance review of cache system
|
|
3. Agent 3: Type checking of utils.ts
|
|
|
|
# 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
|