PlunderStruck

Design autonomous agent systems and the human oversight around them — specifying what an agent can perceive and act on, why a stateless…

Apply compatibility rules when changing anything another process will read — API request/response shapes, event and message payloads…

Decide where a boundary goes — and whether it earns its keep at all.

State and honour what a boundary promises — preconditions as the caller's obligation, postconditions as the supplier's guarantee, class…

Apply data-correctness rules when writing or reviewing code that touches shared state — SQL/ORM queries and transactions, read replicas…

Make data actually survive a crash — what fsync guarantees and what it does not, why a successful write() means nothing, the directory…

Index of engineering failure-mode skills — routes to the right one for evidence-driven bug hunting, fuzzing, data correctness, resilience…

Find and fix bugs worth fixing instead of inventing hypothetical edge cases.

Design, run, and interpret high-signal fuzzing campaigns that generate many reproducible experiments without mistaking random volume or…

Conduct a postmortem and judge decisions fairly after the fact — writing up a conjunction of contributing factors instead of a single root…

Design interactions people can figure out and recover from — signifiers versus affordances, natural versus arbitrary mapping, feedback…

Change code that has no tests, without breaking it — finding seams to substitute behavior, pinning current behavior with characterization…