AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
中文简介正在准备中。当前显示原文说明。
Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
| Phase | Focus | Output |
|---|---|---|
| Discovery | Feasibility | Risk notes, complexity |
| PRD | Requirements clarity | Questions, edge cases |
| Tech Spec | Architecture | Spec, APIs, data models |
| Development | Implementation | Code, tests, docs |
| QA & Ship | Bug fixes | Fixes, deployment docs |
RED (Write failing test) -> GREEN (Minimal code) -> REFACTOR (Clean up) -> REPEAT
NO FIXES WITHOUT ROOT CAUSE.
If 3+ fixes failed -> Stop, question architecture.
Validate at EVERY layer:
| Layer | Purpose |
|---|---|
| Entry Point | Reject invalid at boundary |
| Business Logic | Validate for operation |
| Environment Guards | Block dangerous ops |
| Debug Instrumentation | Log for forensics |
| Size | Action |
|---|---|
| < 200 | Ideal |
| 200-300 | Consider splitting |
| 300-400 | Split now |
| > 400 | Must refactor |
feature/
feature.controller.ts # HTTP (thin)
feature.service.ts # Business logic
feature.repository.ts # Data access
feature.types.ts # Types
feature.validation.ts # Validation
Must have: single responsibility, DRY code, type hints, meaningful names, error handling, files < 300 lines.
Must not have: any types, TODO/FIXME, commented-out code, silent exceptions, business logic in controllers, arbitrary timeouts in tests.
// Wrong
await sleep(100);
// Right
await waitFor(() => result !== undefined);
| Anti-Pattern | Fix |
|---|---|
| No TDD | Tests first |
| if is_test in prod | No test logic |
| Happy path only | Test errors |
| Over-mocking | Real dependencies |
| Guessing at fixes | Systematic debug |
| Large files | Split modules |
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
中文简介正在准备中。当前显示原文说明。
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
中文简介正在准备中。当前显示原文说明。
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
中文简介正在准备中。当前显示原文说明。
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
中文简介正在准备中。当前显示原文说明。
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
中文简介正在准备中。当前显示原文说明。
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
中文简介正在准备中。当前显示原文说明。