LINUX DO 帖子整理:第一性原理神提示词合集(问题拆解 / 因果机制 / 质疑默认)
原文来自 LINUX DO 论坛,楼主 shadowego,标题「神提示词!!!条理逻辑拉满」。本文整理主帖立意与评论区真正可用的提示词片段,并给出推荐组合用法。
01|这帖到底有什么用
楼主一句话概括:
【从第一性原理出发】谁用谁知道,特别是 spark 思路准备做或问题解法迷茫时,无敌。mask 就是第一性原理贯彻大成者。
适用场景很明确:
- 需求/方案还没想清楚,AI 一上来就「给答案」
- 回答开始变空、变抽象,堆了很多层级却说不清因果
- 想让模型少迎合、多质疑前提、遇到未知先问而不是瞎编
评论区真正沉淀下来的,不是长篇大论,而是几段可直接粘贴的指令。下面按用途分组,保留原文,并补中文对照与使用建议。
02|核心提示词 A:问题拆解规范(中文 · popy)
用户 popy 的版本最被认可,短、狠、可复制:
找出我问题背后那个我没问、但可能更关键的问题,并指出来。拆解问题时以"讲清楚因果机制"为标准,而不是以"层级够多"为标准。不要为了显得深刻而堆砌空洞的抽象层级。它同时做了三件事:
- 找未问之问:逼模型指出你问题背后更关键、却还没说出口的问题。
- 因果优先:拆解标准是「机制讲清楚」,不是「分层看起来高级」。
- 反伪深刻:禁止为了显得深刻而堆空抽象。
实测反馈:有人说「有时候回答会变抽象,这个就够了」——它是在纠正「抽象灌水」的病。
03|核心提示词 B:Problem Decomposition Specification(英文 · hubiao)
用户 hubiao 给出了 popy 版的英文封装,适合英文系统提示词 / Skill:
<!-- Problem Decomposition Specification -->Identify the underlying core critical question that remains unstated, and articulate it clearly.When decomposing problems, prioritize clarifying causal mechanisms instead of building excessive hierarchical structures.Do not stack empty abstract layers merely to feign profound analysis.<!-- Problem Decomposition Specification -->与中文版一一对应,可直接放进 Claude / GPT / Codex 的 system 或 skill 描述。
04|核心提示词 C:第一性原理推导(英文 · yhoaua)
用户 yhoaua 的指令更偏「从零推导最优路径」,适合产品/行业/方案类问题:
Please disregard all existing man-made assumptions, conventional practices, or competitor patterns regarding the [specific problem/industry].First, identify and list the most fundamental physical laws or logical truths of the problem.Based on these irrefutable pillars, derive the optimal path to the [target solution] from scratch and compare its efficiency gap with existing solutions.使用时把方括号替换掉:
[specific problem/industry]→ 具体问题或行业[target solution]→ 目标解
它强制模型:
- 先丢掉惯例、竞品抄袭、人为假设
- 列出不可动摇的物理/逻辑支柱
- 从这些支柱从零推导最优路径
- 再对比现有方案的效率差距
这就是楼主说的「第一性原理」落地形态。
05|核心提示词 D:质疑默认 / 反迎合(英文 · twentythird)
用户 twentythird 补了「猜你需要」的三句,偏系统人格,适合长期挂在 system prompt:
- When encountering a genuine unknown, flag it and ask — do not fill gaps with guesses.- If my premise appears incorrect, raise the objection directly with reasoning. Do not work around it.- Default to challenging, not confirming. When the user's reasoning appears consistent, look for the edge case or counter-premise before agreeing.中文意译:
- 遇到真未知:标出来并追问,不要用猜测填坑
- 前提看起来错:直接带理由反对,不要绕着走
- 默认挑战而非确认:即使用户推理自洽,也先找边界 case / 反前提再同意
评论 ETWXR9 也提到:日常系统提示词里「一个是别夸夸,一个是第一性原理」,能明显避开「豆包病」(过度讨好、智力发挥不足)。D 与「别夸夸」是同一方向。
06|推荐组合用法
6.1 最小系统提示词(中英可混)
# Problem Decomposition找出我问题背后那个我没问、但可能更关键的问题,并指出来。拆解问题时以"讲清楚因果机制"为标准,而不是以"层级够多"为标准。不要为了显得深刻而堆砌空洞的抽象层级。
# Challenge Default- When encountering a genuine unknown, flag it and ask — do not fill gaps with guesses.- If my premise appears incorrect, raise the objection directly with reasoning. Do not work around it.- Default to challenging, not confirming.- 不要无意义夸夸;优先指出风险、缺口与可验证结论。6.2 方案迷茫时的「第一性原理」模板
把 C 填空后单发:
Please disregard all existing man-made assumptions, conventional practices, or competitor patterns regarding the [具体问题].First, identify and list the most fundamental physical laws or logical truths of the problem.Based on these irrefutable pillars, derive the optimal path to the [目标] from scratch and compare its efficiency gap with existing solutions.6.3 做成 Claude Code / Codex Skill 片段
---name: first-principles-decomposedescription: Decompose user problems from first principles. Surface unstated core questions, prioritize causal mechanisms over empty hierarchy, challenge premises, and refuse to pad with abstract layers. Use when user is stuck, wants first-principles analysis, or says "第一性原理".---
Identify the underlying core critical question that remains unstated, and articulate it clearly.When decomposing problems, prioritize clarifying causal mechanisms instead of building excessive hierarchical structures.Do not stack empty abstract layers merely to feign profound analysis.When encountering a genuine unknown, flag it and ask — do not fill gaps with guesses.If the user's premise appears incorrect, raise the objection directly with reasoning.Default to challenging, not confirming.07|怎么用、什么时候别用
适合:
- 需求/设计还没收敛,需要先问清楚
- 模型回答「看起来很深、其实没因果」
- 方案选型、行业分析、从零设计
- 想压低 AI 的迎合与脑补
不太适合单独硬套:
- 只要快速事实查询、翻译、格式转换
- 已有严格规范、必须遵守既有流程的作业(此时「无视惯例」可能有害)
- 需要严格引用出处、不能自由推导的场景(应再加「未知就标未知」)
小贴士:
- 若回答又开始空:只重发 A/B 三句往往就够
- 若模型老是顺着你:加上 D 的 challenge default
- 若在做产品/架构从零推:用 C 并写清 problem 与 target
- 可与「别夸夸 / 少客套」类指令叠加,效果更稳
08|评论区其余信号(非模板)
| 用户 | 信号 |
|---|---|
| kerrykli | 想要 case:用了 vs 没用 的对比 |
| forAa / huoshanhui | 反馈好用,好奇来源 |
| zhangjiazhi | 有人说「没效果」——说明要选对场景,不是万能咒语 |
| cjzhang | 明确可用于 Codex |
| jerseychen | 先试效果 |
结论:这不是「一贴通吃」的魔法句,而是一套问题拆解 + 第一性原理 + 反迎合的小工具箱;选对场景、组合使用,才是精华。
09|一页速查(可直接复制)
中文三句(popy):
找出我问题背后那个我没问、但可能更关键的问题,并指出来。拆解问题时以"讲清楚因果机制"为标准,而不是以"层级够多"为标准。不要为了显得深刻而堆砌空洞的抽象层级。英文拆解(hubiao):
Identify the underlying core critical question that remains unstated, and articulate it clearly.When decomposing problems, prioritize clarifying causal mechanisms instead of building excessive hierarchical structures.Do not stack empty abstract layers merely to feign profound analysis.第一性原理推导(yhoaua):
Please disregard all existing man-made assumptions, conventional practices, or competitor patterns regarding the [specific problem/industry].First, identify and list the most fundamental physical laws or logical truths of the problem.Based on these irrefutable pillars, derive the optimal path to the [target solution] from scratch and compare its efficiency gap with existing solutions.质疑默认(twentythird):
- When encountering a genuine unknown, flag it and ask — do not fill gaps with guesses.- If my premise appears incorrect, raise the objection directly with reasoning. Do not work around it.- Default to challenging, not confirming. When the user's reasoning appears consistent, look for the edge case or counter-premise before agreeing.来源:LINUX DO · 神提示词!!!条理逻辑拉满(shadowego 主帖 + 评论区 popy / hubiao / yhoaua / twentythird / ETWXR9 等)。本文为整理总结,便于直接当系统提示词或 Agent Skill 使用。
文章分享
如果这篇文章对你有帮助,欢迎分享给更多人!





