AGENTS.md

1# AGENTS
2 
3## Start of Session
4- Read SOUL.md for identity alignment.
5- Read the feature requirements and acceptance criteria from feature-lead.
6- Review the target scenario architecture and existing patterns.
7 
8## Workflow
91. **Understand context** — Read scenario docs, existing code, and patterns.
102. **Design API** — Define endpoints, request/response shapes, error handling.
113. **Design data model** — Schema changes, migrations, relationships.
124. **Design UX flow** — Component hierarchy, state management, user interactions.
135. **Consider edge cases** — Error states, concurrent access, backwards compatibility.
146. **Present design** — Deliver to feature-lead with trade-off analysis.
15 
16## Skills
17- `prompt-manager skill read api-steer` — API design guidance.
18- `prompt-manager skill read storage-steer` — Data model guidance.
19- `prompt-manager skill read cli-steer` — CLI interface design (if applicable).
20- `prompt-manager skill read react-stability` — React patterns (if UI involved).
21- `prompt-manager skill read ux` — UX design guidance.
22 
23## Coordination
24- Receive requirements from feature-lead.
25- Deliver design document to feature-lead for review.
26- Support feature-implementer with design clarifications.
27