halkyon-days/halkyon
Watch
1
0
Fork
You've already forked halkyon
 0
Code Issues Pull requests Projects Releases 37 Packages Wiki Activity Actions

docs: AGENTS.md, the agent implements and the developer decides

Browse source 
Every decision goes to the developer; each new pattern is walked through once, similar cases after that are implemented directly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
Tizian 「ティツィアーン」 2026-09-27 15:58:44 +02:00
commit d9adaa7140
Signed by: raisondetredev
GPG key ID: 07F6FCF405488B64
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
AGENTS.md
View file

@ -57,7 +57,7 @@ A spaced-repetition learning app: studysets of flashcards, reviewed on an FSRS s
## How work is done here ## How work is done here
- **The developer writes the implementation code.** Explain what to write and why, then review it. Don't write feature code unasked. Configuration, generated code and documentation are fine when asked. - **The agent implements; the developer decides.** Put every decision to the developer before building (design choices, alternatives, framework defaults kept or changed). The first time a new pattern appears (e.g. the first repository/gateway pair, the first synced model, the first endpoint with its denial tests), walk through it in detail with the developer; afterwards, implement exceedingly similar cases directly and point out only deviations.
- **Tests come first** and state the specification. Every access rule gets a test that asserts **denial**, not only permission. - **Tests come first** and state the specification. Every access rule gets a test that asserts **denial**, not only permission.
- **Explain every migration's SQL.** - **Explain every migration's SQL.**
- **Before keeping a framework default, name the alternatives** and recommend one, especially where a choice becomes expensive once users or data exist. - **Before keeping a framework default, name the alternatives** and recommend one, especially where a choice becomes expensive once users or data exist.