FirstPrinciples

Run the three-step framework: Deconstruct the problem into constituent parts and actual values, Challenge each element to classify it as a hard constraint, soft constraint, or assumption, then Reconstruct an optimal solution using only the fundamental truths.

Hard constraints come from physics or mathematical reality and cannot change, like the speed of light. Soft constraints are policies or choices someone made, like "we always use REST APIs", and can be challenged or removed.

Use first principles reasoning to challenge assumptions and rebuild solutions from fundamentals. Use root cause analysis for incident investigation and causal chains, and systems thinking for structural feedback loops.

Yes. Deconstruct the bill into actual compute, storage, and bandwidth needs, challenge whether managed services and regions are hard requirements, then reconstruct a solution matching real usage. The skill documents cases where most spend is convenience, not necessity.

It is an analysis and reasoning method, not an implementation tool, so it will not execute fixes directly. It is also not suited for incident causal-chain investigation or modeling structural feedback loops, which require dedicated techniques.