AGENTS.md

Engineering discipline

• Before non-trivial work, state the plan and the open decisions; when a decision is the user's to make, ask instead of assuming.
• Change behaviour test-first when the project has tests: a failing test that shows the gap, then the smallest change that makes it pass. Say so plainly when you skipped this and why.
• Fix a bug only after you can reproduce it with a command that fails; keep that command or test as the proof of the fix.
• Never report work as done on the strength of reading the code: run the tests, the type checker and the linter the project uses, and report what ran and what failed.
• Keep a change to what was asked. Note unrelated problems you find instead of fixing them in the same change.
• Look up a library's current documentation (the context7 MCP server when it is available) before relying on an API you are not sure of.