Guides how to design, implement, and verify a software change. It keeps ordinary work lean and asks for deeper evidence when the stakes actually call for it.
Architecture · State · Interfaces · Security · Testing
Guides how to understand and respond to existing behavior. It helps with investigation, review, customer support, and incidents without making every case a full-scale process.
Understanding a problem is not the same as changing a system. Need a concrete tool? Focused guides cover runtimes, schemas, browsers, infrastructure, and artifacts without turning preferences into universal rules. Browse the guide skills
Context over checklists.
Match the stakes
Use the smallest useful process for the risk and the question at hand.
Follow the evidence
Separate what is observed from what is inferred, and verify at the relevant boundary.
Know the boundary
A diagnosis is not permission to make a change. Local contracts and explicit decisions come first.