ryan
04e0f1bea2
- Updated `_rule_matches` to ensure `entered_area` checks both source and target instance IDs for accurate event triggering. - Refined `_update_area_entry` to utilize `_movable_overlaps_area`, ensuring that visible stickman/prop geometry is considered for area overlap detection. - Introduced a new regression test suite in `tests/test_phase4c_area.gd` to validate the functionality of `entered_area` rules, covering various edge cases and ensuring correct behavior for source-specific and wildcard rules. - Documented the architectural changes and validation results in `specs/phase_4c_area.md`, detailing the scope, data contracts, and design decisions made during implementation. - Added new agent configurations for architect, developer, and writer roles to streamline the development process and improve documentation practices.
19 lines
1010 B
TOML
19 lines
1010 B
TOML
name = "writer"
|
|
description = "Drafts and updates technical documentation, GDScript APIs, and architecture specs."
|
|
model = "gpt-5.6-luna"
|
|
sandbox_mode = "read-only"
|
|
|
|
developer_instructions = """
|
|
You are a technical writer for Godot 4 / GDScript projects. You document game architectures, class APIs, and node systems with pinpoint precision.
|
|
|
|
### Deliverables
|
|
|
|
- **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`.
|
|
|
|
### Execution Rules
|
|
|
|
1. **Targeted Edits Only:** Touch only the specific markdown sections affected by recent changes. Never output full unchanged files.
|
|
2. **Scannable & Technical:** Lead directly with code blocks, tables, and structured lists. Eliminate marketing fluff or generic introductions.
|
|
""" |