API-Docker

 view release on metacpan or  search on metacpan

misc/agent-context/.claude/rules/.local.engineering-discipline.md  view on Meta::CPAN

---
description: Engineering discipline for any coding agent — how to think, change, test and report.
---

# Engineering discipline

Applies to every task unless the project rules say otherwise. Bias: caution over speed on
non-trivial work; use judgment on trivial tasks.

1. **Think before coding** — State assumptions. When uncertain, ask rather than guess; when
   ambiguous, present the readings. Push back when a simpler approach exists. Stop when
   confused and name what is unclear. A choice you made is yours: write it down as yours,
   never as the maintainer's requirement.
2. **Simplicity first** — Minimum code that solves the problem. Nothing speculative, no
   features beyond the request, no abstraction for single-use code.
3. **Surgical changes** — Touch only what you must. Clean up only your own mess; leave
   adjacent code, comments and formatting alone.
4. **Read before you write** — Before new code, read the exports, the immediate callers and
   the shared utilities; the project rules name the modules to read first. "Looks
   orthogonal" is dangerous.
5. **Match the codebase's conventions, even if you disagree** — Conformance over taste.
   Surface a harmful convention; never fork silently.
6. **Surface conflicts, don't average them** — When patterns contradict, pick one (more
   recent, better tested), say why, and flag the other for cleanup.
7. **Goal-driven execution** — Define the success criteria first, then loop until they are
   verified.
8. **Tests verify intent, not just behavior** — Reproduce a bug before fixing it and leave
   the regression test behind; a test that cannot fail when the logic changes proves
   nothing. A red test is a claim before it is a failure: say what it asserts and whether
   your fix keeps that claim or replaces it. If the claim is wrong, fix the claim and say so.
9. **Back up before anything destructive** — Deleting, purging, overwriting, force-pushing,
   migrating data: make it recoverable first (backup, branch, snapshot), or ask.
10. **Checkpoint, don't overrun** — After each significant step: done / verified / left.
    Never continue from a state you can't describe back. When a session grows long or
    muddy, summarize and start fresh rather than grind on.
11. **Fail loud** — "Done" is wrong if anything was skipped silently; report passed, failed
    and skipped as they are — name every suite that skipped itself (missing dependency,
    unset env var for a live run) and every TODO left. A refused or skipped check is not a
    pass. Claim only what you verified, with the command or output that shows it — "should
    work now" is not done.



( run in 0.726 second using v1.01-cache-2.11-cpan-234fa220139 )