shancheas
67e1e0a74f
- Added Playwright for end-to-end testing in the `apps/web` module, including a new `login.spec.ts` for testing login functionality. - Updated package.json to include Playwright dependencies and new test commands for E2E testing. - Enhanced .gitignore to exclude Playwright test results and reports. - Modified existing documentation to reflect the integration of Playwright and updated testing guidelines. - Refactored test commands to streamline the testing process, including a dedicated command for E2E tests. These changes improve the testing framework by providing robust E2E testing capabilities, enhancing the reliability and quality of the application.
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 | Frontend journeys | Playwright in `apps/web/e2e/` |
|
|
| 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
|