What is first principles thinking? How do you use it in engineering?

[swapnildahiphale]

Welcome

Most engineering decisions start from analogy: "Netflix uses microservices, so we should too." First principles thinking flips that. You break the problem down to fundamental truths and build your solution from there.

This skill brings that method into your coding agent workflow -- Claude Code, Cursor, Codex, OpenCode, or Gemini CLI.

How it works

The skill runs 5 phases at up to 3 depth levels:

1. Problem Intake -- what are you actually trying to solve?
2. Assumption Surfacing -- what are you taking for granted?
3. Decomposition -- what are the ground truths vs. inherited conventions?
4. Reconstruction -- build a solution from verified truths only
5. Solution Output -- code, architecture, or decision with embedded reasoning

Try it

Next time you're choosing a database, designing an API, or debugging something weird -- trigger the skill:

"Think about this from first principles"

Then share what happened. What assumptions did it catch? What did you build differently?

Discussion starters

• What's an engineering decision you made from convention that you later regretted?
• Have you used first principles thinking in your work? How did it change the outcome?
• What problem types benefit most from this approach?
• Feature requests, feedback, and ideas are all welcome.