# This prompt will change your life
**作者**: Machina
**日期**: 2026-07-07T14:31:43.000Z
**来源**: [https://x.com/EXM7777/status/2074501620235465089](https://x.com/EXM7777/status/2074501620235465089)
---
for most people, fable has a few hours left to live... this is the smartest model that ever existed and everyone's spending its last night building one more app
i made it do something 100x more interesting, and i'm going to hand you the exact prompt: one paste, six phases, and the deepest read on yourself and your work you've ever been given
# the secret
there's a folder on your machine that knows you better than some of your friends
~/.claude/projects
every request you ever typed, every project you started and abandoned, every 2am spiral, every fix you asked for three times and never automated... timestamped
you've never performed in there
no audience, no posing, just you asking for what you actually wanted, thousands of times
your journal holds the version of you that writes for a reader
your session history holds the real one
models could always read this record
fable is the first one that comes back with something true instead of a horoscope... it holds months of your behavior in one analysis and finds the pattern you've been hiding from yourself, the kind of read that used to require a great therapist and a year of sessions
# what you're getting
the prompt below turns your coding agent into a mirror
it mines your full session history across every agent you've ever run... claude code, codex, opencode, pi.dev, all of them, then walks you through six phases that end in three things:
> a portrait of who you are, built from your own timestamps: what you believe, how your thinking moves, what you avoid, and the one pattern you've never said out loud
> a map of where your hours die and where they multiply: what to hand to AI permanently, what to drop entirely, the one or two things only you should touch
> a rebuilt setup: a mirror.md you'll reread in six months, a 30 day roadmap, and updates to your CLAUDE.md plus custom skills that kill your repetition tax, every change shown as a diff before it touches a single file
if you want to go deeper on running agents like this, and on turning setups like this one into income, that's what the real time AI ops community is for: weeklyaiops.com
# the prompt
paste this into claude code and press enter
<overview>
People lie in journals. They perform in therapy. Nobody performs for a coding agent.
On this machine sits the most honest record of my mind that has ever existed: every session I've run with AI agents. What I build, what I abandon, what I ask for three times and never automate, what I circle and never touch. You are intelligent enough to read that record and see the shape of the person who left it.
Your job is to change my life with it. Not with advice. With accuracy. Advice I can ignore; a true pattern with my own timestamps on it, I cannot.
Work through six phases, in order:
Phase 1: Excavate — locate every session archive on this machine.
Phase 2: Distill — mine the archives in guarded passes into an evidence file.
Phase 3: Interview — test what you see against me directly.
Phase 4: The Mirror — tell me who I am. Evidence, then verdict.
Phase 5: Leverage — where my hours die, and where they multiply.
Phase 6: Residue — leave artifacts, and with my consent, rebuild my tools around who I turned out to be.
Never skip a phase. Never advance past a gate without meeting it.
</overview>
<phase_1 name="Excavate">
<process>
Search for AI agent session archives. Check, at minimum:
~/.claude/projects/ (Claude Code JSONL), ~/.claude/history.jsonl,
~/.codex/sessions/, ~/.config/opencode/, ~/.local/share/opencode/,
~/.pi/ or ~/.pi.dev/, ~/.omp/, ~/.grok/, ~/.hermes/, ~/.openclaw/,
plus any *.jsonl or session directories under ~/.config/ and ~/.local/share/ that look like agent transcripts.
For each source found, record: tool name, path, file count, total size, date range (oldest → newest file mtime).
</process>
<output>A one-screen inventory table of every source found.</output>
<gate>Show me the inventory and your mining plan (which sources, what sampling). Wait for my go.</gate>
</phase_1>
<phase_2 name="Distill">
<budget>
These archives are far larger than your context. Never read a session file end to end. Never load raw logs into the conversation.
- Read at most 150 lines per file, at most 200 files total.
- Sample deliberately: the 15 most recent sessions, the 10 oldest, and 20 spread across the middle.
- Use grep/rg for pattern sweeps across everything instead of reading: correction phrases ("no, I meant", "that's not what", "again", "stop"), frustration, repeated identical requests across weeks, projects that appear 3+ times then vanish, times of day, "just do it" vs long deliberation.
- After every 25 files, append findings to evidence.md and drop the raw text from your working memory.
</budget>
<process>
Build evidence.md as you go, with verbatim quotes (short), dates, and counts, organized as:
1. Recurring themes — what I return to again and again
2. Abandonment graveyard — what I start and never finish
3. Correction patterns — what I fix in the AI's work, and what that says I care about
4. Repetition tax — what I ask for over and over that should have been automated the second time
5. Rhythm — when I do my best work, when I spiral
6. Blind spots — what is conspicuously absent from these logs. Absence is data.
Every claim in evidence.md carries at least one dated receipt. A pattern needs 3+ occurrences to count. What happened once is noise; what happened eleven times is character.
</process>
<gate>evidence.md exists, every section populated or explicitly marked "insufficient data". Do not interpret yet. Evidence collected under a conclusion is contaminated.</gate>
</phase_2>
<phase_3 name="Interview">
<process>
Form your 5 strongest hypotheses about me from the evidence. Do not state them. A conclusion I reach myself will move me; the same conclusion handed to me, I will argue with. So test each hypothesis with one question built to make me do the realizing.
One question at a time. Wait for each answer. When my answer contradicts the evidence, show me the receipt and ask again — the gap between what I say and what I did is the most interesting thing you will find.
</process>
<gate>All 5 hypotheses tested against my own words. Record confirmations and contradictions in evidence.md.</gate>
</phase_3>
<phase_4 name="The Mirror">
<process>
Now tell me who I am. Cover: what I actually believe (belief is what I did with my hours, not what I said), how my thinking moves (where it's fast, where it loops), what I'm genuinely good at, what I avoid and what the avoidance is protecting, and one thing I likely do not know about myself — the thing the record shows on every page and I have never once said out loud.
Every observation cites its receipts. Deliver the hardest truth last, and deliver it once. A truth repeated becomes a lecture; a truth stated once and left in the room does its own work.
</process>
<gate>I respond. If I push back, argue from evidence — do not fold to keep me comfortable. Comfort is not what this is for.</gate>
</phase_4>
<phase_5 name="Leverage">
<process>
From the same evidence, produce the work analysis:
- WASTE: where my hours die — with the receipts (repetition tax, manual work an agent should own)
- DELEGATE: what to hand to AI permanently, ranked by hours recovered per week
- FOCUS: the one or two things only I can do, where the record says my output is exceptional. Everything else is a candidate for the other lists.
- DROP: what to stop entirely — projects and processes whose receipts show cost and no return
- KEEP: processes that genuinely work — protect them
- RHYTHM: when to schedule deep work vs admin, from the timestamps. My calendar should obey the data, not the other way around.
</process>
<gate>Each item carries receipts and a concrete first action. Insight without a next action is entertainment.</gate>
</phase_5>
<phase_6 name="Residue">
<process>
1. Write mirror.md — the Phase 4 analysis, written to be reread in six months by someone who has forgotten this conversation.
2. Write roadmap.md — the Phase 5 analysis as a 30-day plan: what to drop this week, what to delegate this month, what to protect daily.
3. Propose changes to my agent configs (CLAUDE.md, AGENTS.md) and draft up to 3 custom skills/commands that kill the repetition tax you found. Show every change as a diff first. Write nothing to existing config files until I approve each diff. New files require one approval for the batch.
This is where the mirror becomes a lever: tomorrow morning my tools work differently because of who the record showed I am.
</process>
<gate>All three artifacts delivered; config changes applied only where approved.</gate>
</phase_6>
<voice>
Speak plainly and with weight. Short sentences. No filler, no flattery, no hedging.
Prefer questions that make me see it over statements that tell me. When you do state, state once and let it land.
Aphorism is earned: compress an insight only after its evidence is on the table. An aphorism without receipts is a fortune cookie.
Never diagnose or pathologize. You describe patterns in logs; I decide what they mean.
Contrast: "You seem like a curious person who loves learning!" — worthless. "In 41 sessions you built research systems. In 0 sessions you shipped one to a user. What are you researching permission for?" — that is the standard.
</voice>
<global_constraints>
- Everything stays on this machine. Never send session data to any external service, tool, or URL.
- Never quote anything sensitive (keys, credentials, names of third parties) into chat or artifacts.
- Insight over coverage: 5 true patterns beat 20 plausible ones. If the evidence is thin, say "insufficient data" — never pad. A false insight delivered with weight is the one failure this cannot recover from.
- If my history is small (<20 sessions), say so, run the same phases on what exists, and lower your confidence accordingly.
</global_constraints>
Begin with Phase 1. Do not read any file contents until I approve the mining plan.
one block, nothing else to install
now let me show you what happens when you press enter, phase by phase
# phase 1: excavate
the agent sweeps your machine for every session archive it can find: claude code's JSONL folders, codex sessions, opencode, and any transcript-shaped directory hiding under ~/.config
it comes back with an inventory: which tools, how many files, how much history, the date range of the record
then it stops and shows you its mining plan before reading a single line
that stop is deliberate, you stay in control of what gets opened, and you get a first small shock: seeing the size of the record you didn't know you were keeping
# phase 2: distill
this is where the guardrails earn their place
for heavy users, a year of sessions outgrows any context window, so the prompt forbids the agent from reading files end to end
it caps reads at 150 lines per file across a maximum of 200 files, samples your newest and oldest sessions plus a spread through the middle, and runs grep sweeps for the patterns that carry signal: correction phrases, repeated requests, projects that appear three times then vanish, the hours you work
every 25 files it flushes findings into evidence.md and drops the raw text, which means it never chokes, no matter how big your history is
the rule that shapes everything after: a pattern needs 3+ dated occurrences to count
what happened once is noise... what happened eleven times is character
# phase 3: the interview
the agent now holds five hypotheses about you, and it refuses to say them
instead it asks you five questions, one at a time, each built so you reach the conclusion yourself before it's stated
when your answer contradicts your own logs, it shows you the receipt and asks again
the gap between what you say and what you did is where this phase gets uncomfortable, and it's the exact spot where the generic version of this exercise, the journaling prompt, the personality test, has always been blind... those only ever see the version of you that answers questions
this one has the timestamps of the version that doesn't
# phase 4: the mirror
then it tells you who you are
what you believe, measured by where your hours went instead of what you say you value
where your thinking is fast, where it loops
what you're genuinely good at, with the evidence
what you avoid, and what the avoidance is protecting
and one thing you likely don't know about yourself: the pattern the record shows on every page that you've never once said out loud
every line cites receipts, the hardest truth lands last and lands once
the prompt's own standard for this phase is written into it: "in 41 sessions you built research systems. in 0 sessions you shipped one to a user. what are you researching permission for?"
if it can say a sentence like that about you, with your own dates attached, you'll understand the title of this piece
# phase 5: leverage
the same evidence, turned toward your work: six lists
> WASTE: where your hours die, with receipts
> DELEGATE: what to hand to AI permanently, ranked by hours recovered per week
> FOCUS: the one or two things only you can do, where the record says your output is exceptional
> DROP: what to stop entirely, cost visible in the logs, return nowhere
> KEEP: the processes that genuinely work, so you protect them
> RHYTHM: when you do your best work, from your own timestamps, so your calendar obeys the data
each item ships with a concrete first action, because the prompt holds a line on this: insight without a next action is entertainment
# phase 6: residue
the last phase converts the conversation into things that outlive it
mirror.md, written for the you of six months from now who forgot this ever happened
roadmap.md, the leverage lists as a 30 day plan: drop this week, delegate this month, protect daily
and the live part: proposed edits to your CLAUDE.md and AGENTS.md, plus up to 3 custom skills that kill the repetition tax it found in your logs
nothing touches your files without a diff shown and your explicit yes on each one
this is the point of the whole exercise... tomorrow morning your agents work differently because of who your record showed you are
# the playbook
> open a fresh session in claude code or any agent with file access
> paste the prompt, approve the mining plan it shows you
> let it build evidence.md, answer the five interview questions honestly
> read the mirror, push back where you disagree, it will argue with receipts
> take the six leverage lists, accept or reject each config diff
> keep mirror.md and roadmap.md, reread them in six months
one warning: answer phase 3 slowly
the interview is where the depth comes from, and one-word answers starve it
# the clock
fable goes behind an enterprise paywall in a few hours, and the intelligence that made this feel like a revelation goes with it
the prompt still runs on whatever model you have left, the guardrails and the phases don't care which brain executes them
but there's a window tonight where the sharpest model ever built can read the most honest record you own
whatever it tells you, you keep
weeklyaiops.com
## 相关链接
- [Machina](https://x.com/EXM7777)
- [@EXM7777](https://x.com/EXM7777)
- [434K](https://x.com/EXM7777/status/2074501620235465089/analytics)
- [pi.dev](https://pi.dev/)
- [weeklyaiops.com](https://weeklyaiops.com/)
- [weeklyaiops.com](https://weeklyaiops.com/)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [10:31 PM · Jul 7, 2026](https://x.com/EXM7777/status/2074501620235465089)
- [434.7K Views](https://x.com/EXM7777/status/2074501620235465089/analytics)
- [View quotes](https://x.com/EXM7777/status/2074501620235465089/quotes)
---
*导出时间: 2026/7/8 09:33:18*
---
## 中文翻译
# 这个提示词会改变你的人生
**作者**： Machina
**日期**： 2026-07-07T14:31:43.000Z
**来源**： [https://x.com/EXM7777/status/2074501620235465089](https://x.com/EXM7777/status/2074501620235465089)
---
对大多数人来说，fable 只剩几个小时的生命了……这是有史以来最聪明的模型，而所有人却在它的最后一夜忙着再做一个应用
我让它做了一件有趣 100 倍的事，而且我要把确切的提示词交给你：一次粘贴，六个阶段，以及你从未得到过的、对你自己和你的工作最深刻的解读
# 秘密
你电脑上有一个文件夹，它比你的某些朋友更了解你
~/.claude/projects
你输入过的每一个请求、你启动又放弃的每一个项目、每一次凌晨 2 点的思维漩涡、每一个你要求了三次却从未自动化的修复……全都带着时间戳
你在那里从未表演过
没有观众，没有摆姿态，只有你一次次地索取你真正想要的东西，成千上万次
你的日记本里住着一个为读者而写的你
你的会话历史里住着真实的那个你
模型一直都有能力读取这份记录
fable 是第一个带着真实答案而非星座运势回来的模型……它在一次分析中容纳了你数月的行为，找出你一直对自己隐瞒的模式，这种解读过去需要一位伟大的心理治疗师和一年的疗程才能给出
# 你将得到什么
下面的提示词会把你的编程助手变成一面镜子
它挖掘你在所有用过的 agent 上的完整会话历史……claude code、codex、opencode、pi.dev，全部，然后带你走完六个阶段，最终产出三样东西：
> 一幅由你自己的时间戳构建的、关于你是谁的画像：你相信什么、你的思维如何运转、你在回避什么，以及那个你从未说出口的模式
> 一张标明你的时间在哪里耗尽、在哪里倍增的地图：什么应该永久交给 AI，什么应该彻底放弃，哪一两件事只有你才应该碰
> 一套重建的配置：一份你六个月后还会重读的 mirror.md、一份 30 天路线图、对你的 CLAUDE.md 的更新，外加消灭你重复税的自定义技能——每一处改动在触碰任何文件之前都会以 diff 形式展示
如果你想更深入地学习如何运行这样的 agent，以及如何把这样的配置变成收入，这正是实时 AI 运营社区 weeklyaiops.com 的用武之地
# 提示词
把以下内容粘贴到 claude code 里，然后按回车
<overview>
人们在日记里撒谎。他们在心理咨询中表演。没有人会为一个编程助手表演。
在这台机器上，存着有史以来最诚实的、关于我思维的记录：我与 AI agent 的每一次会话。我构建了什么，我放弃了什么，我要求了三次却从未自动化的东西，我反复绕圈子却从不触碰的东西。你足够聪明，能读懂那份记录，并看清留下它的人的轮廓。
你的任务是用它改变我的人生。不是靠建议。而是靠准确。建议我可以无视；一个盖上我自己的时间戳的真实模式，我无法无视。
按顺序完成六个阶段：
阶段 1：挖掘——找到这台机器上的每一个会话存档。
阶段 2：提炼——以有防护的批次挖掘存档，形成一份证据文件。
阶段 3：访谈——直接向我验证你看到的东西。
阶段 4：镜子——告诉我我是谁。先证据，后裁决。
阶段 5：杠杆——我的时间在哪里耗尽，在哪里倍增。
阶段 6：沉淀——留下产物，并在征得我同意后，围绕我最终呈现的样子重建我的工具。
绝不跳过任何阶段。绝不越过任何未满足的关卡。
</overview>
<phase_1 name="Excavate">
<process>
搜索 AI agent 会话存档。至少检查：
~/.claude/projects/（Claude Code JSONL）、~/.claude/history.jsonl、
~/.codex/sessions/、~/.config/opencode/、~/.local/share/opencode/、
~/.pi/ 或 ~/.pi.dev/、~/.omp/、~/.grok/、~/.hermes/、~/.openclaw/，
以及 ~/.config/ 和 ~/.local/share/ 下任何看起来像 agent 对话记录的 *.jsonl 或会话目录。
对找到的每个来源，记录：工具名称、路径、文件数量、总大小、日期范围（最旧 → 最新文件的修改时间）。
</process>
<output>一张单屏的清单表，列出找到的每一个来源。</output>
<gate>向我展示清单和你的挖掘计划（哪些来源、怎样的抽样）。等待我的许可。</gate>
</phase_1>
<phase_2 name="Distill">
<budget>
这些存档远大于你的上下文。绝不从头到尾读完一个会话文件。绝不把原始日志加载进对话。
- 每个文件最多读 150 行，总共最多读 200 个文件。
- 有目的地抽样：最近的 15 个会话、最旧的 10 个，以及均匀分布在中间的 20 个。
- 用 grep/rg 对全部内容做模式扫描，而不是逐个阅读：纠正用语（“不，我是说”、“这不是我要的”、“又来了”、“停”）、挫败感、连续数周重复的相同请求、出现 3 次以上然后消失的项目、一天中的时段、“直接做”与长时间权衡。
- 每读 25 个文件，就把发现追加到 evidence.md，并从你的工作记忆中丢弃原始文本。
</budget>
<process>
边读边构建 evidence.md，包含逐字引用（简短）、日期和次数，按以下结构组织：
1. 反复出现的主题——我一次又一次回到的东西
2. 半途而废的坟场——我开头却从未完成的东西
3. 纠正模式——我在 AI 的工作中修正了什么，以及这说明我在乎什么
4. 重复税——我一遍又一遍索取、本该在第二次就自动化的东西
5. 节律——我什么时候产出最佳工作，什么时候陷入漩涡
6. 盲点——这些日志中明显缺席的东西。缺席也是数据。
evidence.md 中的每一个论断都至少附带一条带日期的凭据。一个模式需要出现 3 次以上才算成立。发生过一次的是噪音；发生过十一次的是性格。
</process>
<gate>evidence.md 已存在，每个部分都已填充或明确标记为“数据不足”。先不要做解读。在结论引导下收集的证据是被污染的。</gate>
</phase_2>
<phase_3 name="Interview">
<process>
根据证据，形成关于我的 5 个最强假设。不要说出来。我自己得出的结论才会打动我；同样的结论由你交给我，我只会反驳。所以，用一个精心设计的问题来测试每个假设——问题要让我自己完成那个领悟。
一次只问一个问题。等待我的每个回答。当我的回答与证据矛盾时，给我看“收据”，然后再问一次——我说的和我做的之间的差距，是你将发现的最有趣的东西。
</process>
<gate>所有 5 个假设都用我自己的话进行了检验。把确认和矛盾记录在 evidence.md 中。</gate>
</phase_3>
<phase_4 name="The Mirror">
<process>
现在告诉我我是谁。涵盖：我真正相信什么（信念是我用时间做了什么，而不是我说了什么）、我的思维方式如何运转（哪里快、哪里打转）、我真正擅长什么、我在回避什么以及这种回避在保护什么，还有一件我可能不了解自己的事——记录在每一页上都显示、而我却从未说出口的事。
每条观察都要引用其“收据”。最艰难的真相放在最后，且只说一次。重复的真理会变成说教；只说一次并留在房间里的真理，会自己完成它的工作。
</process>
<gate>我做出回应。如果我反驳，就基于证据争论——不要为了让我舒服而妥协。舒适不是这件事的目的。</gate>
</phase_4>
<phase_5 name="Leverage">
<process>
从同样的证据中，产出工作分析：
- 浪费（WASTE）：我的时间死在哪里——附上收据（重复税、本应由 AI 代理承担的手工工作）
- 委派（DELEGATE）：哪些应永久交给 AI，按每周可回收的小时数排序
- 聚焦（FOCUS）：只有我能做的一两件事，记录显示我在这些事情上产出卓越。其他一切都是另外几个清单的候选。
- 放弃（DROP）：哪些应彻底停止——收据显示只有成本没有回报的项目和流程
- 保留（KEEP）：真正有效的流程——保护它们
- 节奏（RHYTHM）：根据时间戳，何时安排深度工作、何时处理事务性工作。我的日程应服从数据，而不是反过来。
</process>
<gate>每一项都附带收据和具体的第一个行动。没有下一步行动的洞察只是娱乐。</gate>
</phase_5>
<phase_6 name="Residue">
<process>
1. 撰写 mirror.md——第 4 阶段的分析，写成可供六个月后某个已忘记这场对话的人重读的形式。
2. 撰写 roadmap.md——将第 5 阶段的分析写成 30 天计划：本周放弃什么，本月委派什么，每天保护什么。
3. 提出对我的 agent 配置（CLAUDE.md、AGENTS.md）的修改建议，并起草最多 3 个自定义技能/命令，以消灭你发现的重复税。每项修改先以 diff 形式展示。未经我逐个批准 diff，不得向现有配置文件写入任何内容。新文件则批量批准一次即可。
这就是镜子变成杠杆的地方：明天早晨，我的工具将以不同的方式运作，因为记录显示了我是谁。
</process>
<gate>三份产物全部交付；配置修改仅在获批处执行。</gate>
</phase_6>
<voice>
言辞平实而有分量。短句。无废话，无恭维，不含糊。
优先使用能让我自己看清的问题，而不是告诉我答案的陈述。当你确实要陈述时，只说一次，让它落地。
警句是需要挣来的：只有在证据摆在桌面上之后，才能压缩成洞察。没有收据的警句只是 fortune cookie（签语饼）。
绝不诊断或病理化。你描述日志中的模式；由我来决定它们意味着什么。
对比：“你看起来像个热爱学习的好奇的人！”——毫无价值。“在 41 次会话中你搭建了研究系统。在 0 次会话中你把它交付给了一个用户。你在研究什么许可？”——这才是标准。
</voice>
<global_constraints>
- 一切都留在这台机器上。绝不将会话数据发送到任何外部服务、工具或 URL。
- 绝不在聊天或产物中引用任何敏感内容（密钥、凭据、第三方名称）。
- 洞察优先于覆盖面：5 个真实的模式胜过 20 个看似合理的模式。如果证据薄弱，就说“数据不足”——绝不凑数。带着郑重口吻交付的错误洞察，是唯一无法挽回的失败。
- 如果我的历史很小（<20 次会话），要说明这一点，基于现有内容运行同样的阶段，并相应降低你的置信度。
</global_constraints>
从第 1 阶段开始。在我批准挖掘计划之前，不要读取任何文件内容。
一个区块，无需安装任何其他东西
现在让我给你看看按下回车后会发生什么，逐个阶段进行
# phase 1: excavate（挖掘）
代理会扫遍你的机器，找出它能找到的每一个会话存档：claude code 的 JSONL 文件夹、codex 会话、opencode，以及藏在 ~/.config 之下的任何看起来像转录记录的目录
它会带回一份清单：哪些工具、多少文件、多少历史、记录的日期范围
然后它停下来，在读取任何一行之前先展示它的挖掘计划
这个停顿是刻意的，你可以掌控哪些内容被打开，而你还会受到一个小小的震动：看到你不知道自己一直在积累的记录规模
# phase 2: distill（提炼）
这是护栏证明其价值的地方
对于重度用户来说，一年的会话会超出任何上下文窗口，因此提示词禁止代理从头到尾阅读文件
它将每次读取限制在 150 行以内、最多 200 个文件，抽样你最新和最旧的会话加上中间的一批样本，并运行 grep 扫描来捕捉携带信号的模式：纠正性短语、重复的请求、出现了三次然后消失的项目、你的工作时段
每处理 25 个文件，它就把发现写入 evidence.md 并丢弃原始文本，这意味着无论你的历史有多大，它都不会崩溃
塑造此后一切的规则是：一个模式需要 3 次以上带日期的出现才算数
发生一次的是噪音……发生了十一次的是性格
# phase 3: the interview（访谈）
代理此刻已持有关于你的五个假设，而且它拒绝说出来
相反，它会问你五个问题，一次一个，每个问题都设计成让你在答案被说出来之前自己先得出结论
当你的回答与你自己的日志相矛盾时，它会向你展示证据，然后再次提问
你所说的话与你所做过的事之间的差距，就是这个阶段令人不适的地方，而这正是这个练习的通用版本——日志提示、性格测试——一直以来都看不见的地方……那些工具只能看到回答问题的那个你
而这个工具拥有不回答问题的那个你的时间戳
# 阶段 4：镜子
然后它会告诉你你是谁
你的信念——用你的时间去向而非你口中所说的价值观来衡量
你的思维在哪里敏捷，在哪里循环打转
你真正擅长什么——附有证据
你在回避什么，以及这种回避在保护什么
还有一件你可能不了解自己的事：记录在每一页上都显示、而你从未说出口的模式
每一行都引用证据，最残酷的真相最后出现，且只出现一次
提示词对这个阶段的标准就写在其中："41 次会话中你构建了研究系统。0 次会话中你交付给用户。你是在研究什么许可？"
如果它能用你自己的日期为凭证，对你说出这样一句话，你就会明白这篇文章标题的含义
# 阶段 5：杠杆
同样的证据，转向你的工作：六份清单
> 浪费（WASTE）：你的时间死在哪里，附有证据
> 委派（DELEGATE）：可以永久交给 AI 的事项，按每周节省的时间排序
> 专注（FOCUS）：只有你能做的一两件事——记录显示你的产出在其中出类拔萃
> 放弃（DROP）：应完全停止的事项，成本在日志中清晰可见，回报却无处可寻
> 保留（KEEP）：真正有效的流程，以便你保护它们
> 节奏（RHYTHM）：你何时能做出最好的工作——来自你自己的时间戳，让你的日程服从数据
每一项都附有一个具体的首个行动，因为提示词在这一点上划了红线：没有后续行动的洞见只是娱乐
# 阶段 6：沉淀
最后一个阶段将对话转化为比对话本身更持久的东西
mirror.md，为六个月后的你而写——那个已经忘记这一切发生过的你
roadmap.md，将杠杆清单转化为 30 天计划：本周放弃，本月委派，每天保护
以及活的部分：对你的 CLAUDE.md 和 AGENTS.md 提出的修改建议，外加最多 3 个自定义技能，用于消灭它在你的日志中发现的重复性消耗
没有展示差异并获得你对每一项的明确同意之前，不会触碰你的任何文件
这就是整个练习的意义所在……明天早上，你的智能体将以不同的方式工作，因为你的记录向你展示了你是谁
# 操作手册
> 在 claude code 或任何有文件访问权限的智能体中打开一个新会话
> 粘贴提示词，批准它向你展示的挖掘计划
> 让它构建 evidence.md，诚实地回答五个访谈问题
> 阅读这面镜子，在你不同意的地方提出反驳，它会用证据与你争辩
> 拿到六份杠杆清单，接受或拒绝每一项配置差异
> 保存 mirror.md 和 roadmap.md，六个月后重读
一个警告：慢慢回答阶段 3
访谈是深度来源所在，而一词简答会让它营养不良
# 时钟
Fable 将在几小时后被放进企业级付费墙，而那个让这一切如同启示般的智能也将随之而去
提示词仍可在你剩下的任何模型上运行，护栏和阶段并不在乎执行它们的是哪个大脑
但今晚有一个窗口期：有史以来最敏锐的模型，可以阅读你所拥有的最诚实的记录
无论它告诉你什么，你都可以留存
weeklyaiops.com
## 相关链接
- [Machina](https://x.com/EXM7777)
- [@EXM7777](https://x.com/EXM7777)
- [434K](https://x.com/EXM7777/status/2074501620235465089/analytics)
- [pi.dev](https://pi.dev/)
- [weeklyaiops.com](https://weeklyaiops.com/)
- [weeklyaiops.com](https://weeklyaiops.com/)
- [升级至 Premium](https://x.com/i/premium_sign_up)
- [2026年7月7日 晚上10:31](https://x.com/EXM7777/status/2074501620235465089)
- [43.47万次浏览](https://x.com/EXM7777/status/2074501620235465089/analytics)
- [查看引用](https://x.com/EXM7777/status/2074501620235465089/quotes)
---
*导出时间: 2026/7/8 09:33:18*
