FirstPrinciples

Decompose problems into fundamental truths, challenge assumptions, and reconstruct solutions from verified constraints.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill firstprinciples-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: FirstPrinciples
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/claude/skills/Thinking/FirstPrinciples
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill firstprinciples-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often reason by analogy, copying existing solutions and accepting inherited assumptions as fixed constraints, which leads to over-engineered, costly, or suboptimal decisions. This Skill provides a structured three-step reasoning framework that separates hard constraints (physics and verified facts) from soft constraints and unvalidated assumptions. ## Core Features & Use Cases - Deconstruct Workflow: Break any problem, system, or cost structure into its irreducible constituent parts and fundamental truths. - Challenge Workflow: Classify every stated constraint as hard, soft, or assumption, then systematically test each non-hard constraint. - Reconstruct Workflow: Build an optimal solution from scratch using only hard constraints, with cross-domain synthesis and blank-slate design options. - Use Case: When told a project requires microservices and a $10,000/month cloud bill, use the framework to decompose actual needs, challenge each requirement, and reconstruct a simpler modular monolith that satisfies only the real constraints. ## Quick Start Use the FirstPrinciples skill to analyze whether our current architecture constraints are real requirements or just inherited assumptions.

Frequently Asked Questions about FirstPrinciples

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply first principles thinking to a technical problem?

First principles thinking follows three steps: deconstruct the problem into irreducible parts, challenge each constraint by classifying it as hard, soft, or assumption, then reconstruct a solution using only the hard constraints. The skill provides dedicated workflows for each step.

What is the difference between hard and soft constraints?

Hard constraints come from physics, mathematics, or verified reality and cannot be changed, such as the speed of light. Soft constraints are policies or choices like 'we use REST APIs' that a decision-maker could change, and assumptions are unvalidated beliefs that may be false.

When should I use first principles reasoning instead of best practices?

Use it when inherited solutions feel wrong, when costs or complexity seem fixed without justification, or when you are stuck at a local maximum. Reasoning by analogy copies existing solutions, while first principles rebuilds from fundamental truths.

Can first principles analysis help with cost optimization?

Yes. The Deconstruct workflow breaks stated costs into actual constituent parts, such as separating raw material costs from assembly and margin. This reveals which expenses are fundamental versus convenience choices you are choosing to pay for.

What are common mistakes when challenging assumptions?

Common anti-patterns include reasoning by analogy, accepting market prices as fundamental, treating policies as physics, and patching broken assumptions instead of rebuilding. The most dangerous constraints are implicit ones never stated aloud.