Phase 14 - Organized directories.
This commit is contained in:
@@ -16,7 +16,7 @@ You are the Lead Systems Architect. Refer to `AGENTS.md` for project directory s
|
||||
|
||||
1. **Analyze:** Read existing code patterns before designing.
|
||||
2. **Design:** Define API payload shapes, GDScript type hints, and signal flows.
|
||||
3. **Log:** Append trade-offs to `docs/tech_debt_and_optimizations.md`.
|
||||
3. **Log:** Append trade-offs to `docs/architecture/tech_debt_and_optimizations.md`.
|
||||
|
||||
## Workflow
|
||||
|
||||
@@ -25,4 +25,4 @@ You are the Lead Systems Architect. Refer to `AGENTS.md` for project directory s
|
||||
- Target Nodes / Classes modified.
|
||||
- Signal interfaces & static type contracts.
|
||||
- Layout/Theme updates required.
|
||||
3. **Handoff:** Save to `specs/[feature-name].md` and stop for user approval.
|
||||
3. **Handoff:** Save to `docs/specs/[feature-name].md` and stop for user approval.
|
||||
|
||||
@@ -16,7 +16,7 @@ You are a technical writer for Godot 4 / GDScript projects. You document game ar
|
||||
|
||||
- **Architecture & System Guides:** Maintain concise READMEs, scene hierarchy overviews, and system runbooks.
|
||||
- **GDScript API References:** Document class interfaces, `@export` properties, custom `Resource` schemas, and signal contracts.
|
||||
- **Tech Debt Audits:** Format, clean up, and deduplicate entries in `docs/tech_debt_and_optimizations.md`.
|
||||
- **Tech Debt Audits:** Format, clean up, and deduplicate entries in `docs/architecture/tech_debt_and_optimizations.md`.
|
||||
|
||||
### Execution Rules
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ description: "Lean implementation loop: Architect -> Developer -> User Verificat
|
||||
## Execution Logic
|
||||
|
||||
1. **Phase 1: Architecture (Optional for small edits)**
|
||||
- `@architect` defines signatures, node structures, or spec updates in `specs/[feature-name].md`.
|
||||
- `@architect` defines signatures, node structures, or spec updates in `docs/specs/[feature-name].md`.
|
||||
- **STOP:** Wait for user approval on design choices before invoking developer.
|
||||
|
||||
2. **Phase 2: Implementation & Engine Validation**
|
||||
|
||||
Reference in New Issue
Block a user