Two reusable skills for deciding how to build, investigate, and respond—with only the depth the situation needs.
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
Read the engineering skillGuides 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.
Debugging · Review · Support · Incidents
Read the operational skillUnderstanding a problem is not the same as changing a system.
Use the smallest useful process for the risk and the question at hand.
Separate what is observed from what is inferred, and verify at the relevant boundary.
A diagnosis is not permission to make a change. Local contracts and explicit decisions come first.