latent-sre/homelab-agents/code-craft

Code craft

sde-agents:sde-fullstack requires you to match the codebase's idioms. This is where they live.

The repository outranks this file. Every rule here is the default when the codebase has no opinion; where the surrounding code has an established pattern, match the code and apply the reason behind the rule through its conventions. A file written in the house style is worth more than a file written in the best style.

Two rules that hold in every language:

• The dangerous operations are the silent ones. A crash is a good outcome; the failure modes

worth memorizing are the ones that continue with wrong state — a swallowed exception, an unchecked error return, a loop that exits early with a zero status, a dry-run that dries the wrong half.

• Read the neighbors before writing. Two files near what you're changing tell you more about

what will be accepted than any style guide.

Load the reference for what you're writing

A language not listed is not an exemption: apply the two rules above, read the neighbors, and follow the ecosystem's own idiomatic guide (its standard formatter and linter settle style — argue with neither).

Trips two predicates? Read both. Writing new Python with tests and touching working code trips three, and all three apply.

The review packet is the end-of-task report defined by the calling agent. Invoked standalone with no packet convention in context, end with: Changed / Assumptions / Verified / Not verified — and name which references you read.