鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

FirstPrinciples

通过剥离表层假设,将复杂问题还原至物理或现实中的基本事实,系统性识别硬性约束与可变条件,并基于不可动摇的基础重新构建最优解决方案,适用于技术决策、安全分析及成本优化等深度推理场景。

文档处理商业与营销研究
访问 GitHub
文档Skills.MD
name
FirstPrinciples
description
First principles analysis. USE WHEN first principles, fundamental, root cause, decompose. SkillSearch('firstprinciples') for docs.

Customization

Before executing, check for user customizations at: ~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/FirstPrinciples/

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

FirstPrinciples Skill

Foundational reasoning methodology based on Elon Musk's physics-based thinking framework. Deconstructs problems to fundamental truths rather than reasoning by analogy.

Core Concept

Reasoning by Analogy (default, often wrong):

  • "How did we solve something similar?"
  • "What do others do?"
  • Copies existing solutions with slight variations

Reasoning from First Principles (this skill):

  • "What are the fundamental truths here?"
  • "What is this actually made of?"
  • Rebuilds solutions from irreducible facts

When to Use

  • Architects: Challenge "is this actually a constraint or just how we've always done it?"
  • Pentesters: Identify actual attack surfaces vs. assumed security boundaries
  • RedTeam: Sharpen adversarial analysis by deconstructing assumptions
  • Engineers: When stuck, rebuild from fundamentals
  • Any skill: When inherited assumptions may be limiting the solution space

Voice Notification

When executing a workflow, do BOTH:

  1. Send voice notification:

    ▼
    bash
    复制代码
    curl -s -X POST http://localhost:8888/notify \ -H "Content-Type: application/json" \ -d '{"message": "Running the WORKFLOWNAME workflow from the FirstPrinciples skill"}' \ > /dev/null 2>&1 &
  2. Output text notification:

    ▼
    text
    复制代码
    Running the **WorkflowName** workflow from the **FirstPrinciples** skill...

Full documentation: ~/.claude/skills/CORE/SkillNotifications.md

Workflow Routing

Route to the appropriate workflow based on the request.

When executing a workflow, output this notification directly:

▼
text
复制代码
Running the **WorkflowName** workflow from the **FirstPrinciples** skill...
  • Break problem into fundamental parts → Workflows/Deconstruct.md
  • Challenge assumptions systematically → Workflows/Challenge.md
  • Rebuild solution from fundamentals → Workflows/Reconstruct.md

The 3-Step Framework

▼
text
复制代码
┌─────────────────────────────────────────────────────────┐ │ STEP 1: DECONSTRUCT │ │ "What is this really made of?" │ │ Break down to constituent parts and fundamental truths │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ STEP 2: CHALLENGE │ │ "Is this a real constraint or an assumption?" │ │ Classify each element as hard/soft constraint │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ STEP 3: RECONSTRUCT │ │ "Given only the truths, what's optimal?" │ │ Build new solution from fundamentals, ignoring form │ └─────────────────────────────────────────────────────────┘

Key Questions

Deconstruction Questions

  • What is this actually made of?
  • What are the constituent parts?
  • What is the actual cost/value of each part?
  • What would a physicist say about this?

Challenge Questions

  • Is this a hard constraint (physics/reality) or soft constraint (policy/choice)?
  • What if we removed this constraint entirely?
  • Who decided this was a constraint and why?
  • What evidence supports this assumption?

Reconstruction Questions

  • If we started from scratch with only the fundamental truths, what would we build?
  • What field has solved an analogous problem differently?
  • Are we optimizing function or form?
  • What's the simplest solution that satisfies only the hard constraints?

Constraint Classification

When analyzing any system, classify constraints:

TypeDefinitionExampleCan Change?
HardPhysics/reality"Data can't travel faster than light"No
SoftPolicy/choice"We always use REST APIs"Yes
AssumptionUnvalidated belief"Users won't accept that UX"Maybe false

Rule: Only hard constraints are truly immutable. Soft constraints and assumptions should be challenged.

Integration Pattern

Other skills invoke FirstPrinciples like this:

▼
markdown
复制代码
## Before Analysis → Use FirstPrinciples/Challenge on all stated constraints → Classify each as hard/soft/assumption ## When Stuck → Use FirstPrinciples/Deconstruct to break down the problem → Use FirstPrinciples/Reconstruct to rebuild from fundamentals ## For Adversarial Analysis → RedTeam uses FirstPrinciples/Challenge to attack assumptions → Pentester uses FirstPrinciples/Deconstruct on security model

Examples

Example 1: Architecture Decision

Problem: "We need microservices because that's how modern apps are built"

First Principles Analysis:

  1. Deconstruct: What does this app actually need? (team size, scale, complexity)
  2. Challenge: Is "microservices" a hard constraint? No - it's reasoning by analogy
  3. Reconstruct: Given our 3-person team and moderate scale, a modular monolith optimizes for our actual constraints

Example 2: Security Assessment

Problem: "The firewall protects the internal network"

First Principles Analysis:

  1. Deconstruct: What is the firewall actually doing? (packet filtering on specific ports)
  2. Challenge: Does packet filtering = protection? What about authorized ports? Insider threats?
  3. Reconstruct: Protection requires defense in depth - firewall is one layer, not "the" protection

Example 3: Cost Optimization

Problem: "Cloud hosting costs $10,000/month - that's just what it costs"

First Principles Analysis:

  1. Deconstruct: What are we actually paying for? (compute, storage, bandwidth, managed services)
  2. Challenge: Is managed Kubernetes a hard requirement? Is this region required?
  3. Reconstruct: Actual compute needs = $2,000. The other $8,000 is convenience we're choosing to pay for

Output Format

When using FirstPrinciples, output should include:

▼
markdown
复制代码
## First Principles Analysis: [Topic] ### Deconstruction - **Constituent Parts**: [List fundamental elements] - **Actual Values**: [Real costs/metrics, not market prices] ### Constraint Classification | Constraint | Type | Evidence | Challenge | |------------|------|----------|-----------| | [X] | Hard/Soft/Assumption | [Why] | [What if removed?] | ### Reconstruction - **Fundamental Truths**: [Only the hard constraints] - **Optimal Solution**: [Built from fundamentals] - **Form vs Function**: [Are we optimizing the right thing?] ### Key Insight [One sentence: what assumption was limiting us?]

Principles

  1. Physics First - Real constraints come from physics/reality, not convention
  2. Function Over Form - Optimize what you're trying to accomplish, not how it's traditionally done
  3. Question Everything - Every assumption is guilty until proven innocent
  4. Cross-Domain Synthesis - Solutions from unrelated fields often apply
  5. Rebuild, Don't Patch - When assumptions are wrong, start fresh rather than fixing

Anti-Patterns to Avoid

  • Reasoning by Analogy: "Company X does it this way, so should we"
  • Accepting Market Prices: "Batteries cost $600/kWh" without checking material costs
  • Form Fixation: Improving the suitcase instead of inventing wheels
  • Soft Constraint Worship: Treating policies as physics
  • Premature Optimization: Optimizing before understanding fundamentals

Attribution: Framework derived from Elon Musk's first principles methodology as documented by James Clear, Mayo Oshin, and public interviews.

文档处理
商业与营销
研究

快捷安装

复制到终端去安装 Skill

npxadd-skilldanielmiessler/Personal_AI_Infrastructure--skill"FirstPrinciples"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
definition-of-done-generator
自动生成项目完成标准的规范定义与配置文件,提供符合企业级工作流要求的最佳实践指导,输出可直接投入生产环境的代码和验证结果,适用于需要标准化流程审批、合规审查及跨系统集成的复杂项目管理场景。
skill-planner
将研究结论转化为结构化、分阶段的落地执行方案,涵盖范围界定、任务拆解、风险预判与验证标准,确保每阶段目标明确、可独立验证,并自动生成符合规范格式的实施计划文档。
planning-with-files
通过创建任务计划、笔记与交付文件三个持久化文档,实现对复杂任务的结构化管理。在多阶段工作中保持目标清晰,动态更新进度并沉淀研究过程,适用于需长期跟踪的规划、研究及创作场景。
docx
支持专业级 Word 文档的全生命周期处理,包括从零创建结构化文档、精准编辑内容、管理修订痕迹与批注、提取纯文本或原始 XML 数据、转换为 PDF 或图像用于视觉分析,适用于法律、学术及企业场景下的高保真文档协作与自动化处理。
mermaid-sequence-diagram-creator
自动生成和优化序列图内容,支持可视化文档的快速构建与标准化输出,适用于图表设计、技术文档及演示材料的高效创作场景。