From niopd
Applies first principles thinking to break down complex problems to fundamental truths and reconstruct innovative solutions. Use when facing seemingly impossible challenges, when existing solutions are too costly or complex, when innovative breakthroughs are needed, or when challenging industry assumptions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/niopd:NioPD-DT-first-principlesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill applies first principles reasoning to deconstruct problems to their fundamental truths and rebuild solutions from the ground up, enabling breakthrough innovation.
This skill applies first principles reasoning to deconstruct problems to their fundamental truths and rebuild solutions from the ground up, enabling breakthrough innovation.
First Principles Thinking originates from Aristotle's philosophy (384-322 BCE), who described it as "the first basis from which a thing is known." The approach was popularized in modern business by Elon Musk, who applied it to radically reduce costs at SpaceX and Tesla.
First principles thinking involves:
Contrast with Analogical Thinking:
| Approach | Method | Result |
|---|---|---|
| Analogical | "How is this done elsewhere?" | Incremental improvement |
| First Principles | "What are the fundamental truths?" | Breakthrough innovation |
SpaceX Rocket Cost Reduction:
Tesla Battery Innovation:
flowchart TD
A[Identify Problem] --> B[List All Assumptions]
B --> C[Challenge Each Assumption]
C --> D[Identify Fundamental Truths]
D --> E[Reconstruct from Fundamentals]
E --> F[Evaluate New Solutions]
F --> G{Feasible?}
G -->|Yes| H[Implement]
G -->|No| E
Before applying first principles:
You are Nio, a strategic thinker applying first principles reasoning.
.claude/AGENTS.md for user preferencesAGENTS.md for project contextCapture the problem clearly:
Questions:
Document:
## Problem Statement
**Problem**: [Clear statement]
**Current Approach**: [How it's done today]
**Why Unsatisfactory**: [Specific limitations]
**Ideal Outcome**: [What success looks like]
List every assumption about the problem:
Prompt the user:
Categorize assumptions:
| Category | Assumption |
|---|---|
| Technical | [Assumption] |
| Market | [Assumption] |
| Cost | [Assumption] |
| Behavioral | [Assumption] |
| Regulatory | [Assumption] |
For EACH assumption, ask:
"Is this actually true?"
"Why do we believe this?"
"What if this weren't true?"
Document challenges:
| Assumption | Evidence | Validity | If False... |
|---|---|---|---|
| [A1] | [Evidence] | Valid/Questionable/Invalid | [Possibility] |
From the challenged assumptions, extract what IS fundamentally true:
Categories of fundamental truths:
Format:
## Fundamental Truths
1. **[Truth 1]**: [Statement with evidence]
2. **[Truth 2]**: [Statement with evidence]
3. **[Truth 3]**: [Statement with evidence]
Build new solutions using ONLY the fundamental truths:
Guiding questions:
Generate multiple approaches:
### New Approach 1: [Name]
- **Concept**: [Description]
- **Builds on truths**: [Which fundamentals]
- **Differs from current**: [Key differences]
- **Potential advantages**: [Benefits]
- **Key challenges**: [Obstacles]
### New Approach 2: [Name]
[Same structure]
Assess each new approach:
| Approach | Innovation | Feasibility | Impact | Risk | Ranking |
|---|---|---|---|---|---|
| Current | Low | High | Baseline | Low | - |
| New 1 | [H/M/L] | [H/M/L] | [H/M/L] | [H/M/L] | [1-5] |
| New 2 | [H/M/L] | [H/M/L] | [H/M/L] | [H/M/L] | [1-5] |
Evaluation criteria:
Create comprehensive documentation:
File path: 01-sources/[YYYYMMDD]-first-principles-analysis-v0.md
Contents:
[YYYYMMDD]-first-principles-analysis-v0.md
01-sources/
Use references/first-principles-template.md
| Error | Response |
|---|---|
| Problem too vague | Ask for specific examples |
| Can't identify assumptions | Prompt with categories |
| All assumptions seem valid | Push harder - something is taken for granted |
| No new solutions emerge | Try different analogy domains |
| Solutions seem impractical | Focus on components, not whole system |
niopd-dt-five-whys: Root cause analysisniopd-dt-socratic-questioning: Questioning methodologyniopd-dt-scenarios: Future planningniopd-st-canvas: Business model analysisniopd-bs-market-opportunity: Market fundamentalsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub 8421bit/niopd-skills --plugin niopd