Borrowing it
Nothing to install: this file belongs to TeigenZhang/life-design-coach. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TeigenZhang/life-design-coach/main/.claude/skills/life-design-coach-mindmap/SKILL.mdgit clone --depth 1 https://github.com/TeigenZhang/life-design-coachWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/teigenzhang/life-design-coach/life-design-coach-mindmap)<a href="https://agentmods.dev/skills/teigenzhang/life-design-coach/life-design-coach-mindmap"><img src="https://agentmods.dev/badge/skills/teigenzhang/life-design-coach/life-design-coach-mindmap/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/teigenzhang/life-design-coach/life-design-coach-mindmap"><img src="https://agentmods.dev/badge/skills/teigenzhang/life-design-coach/life-design-coach-mindmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00090 | $0.01072 |
| Opus 5 | $0.00045 | $0.00536 |
| Sonnet 5 | $0.00018 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
life-design-coach-mindmap scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
思维导图 · Mind Mapping
Phase 3.1 · 45-60 分钟 · 产出:
odyssey/YYYY-MM_mindmap.md(为 Odyssey 打底)
前置条件(硬性)
journal/daily/≥ 3 周journal/aeiou_*.md存在compass/energy-map.md存在
缺任何一个就阻止,引导用户先完成前置。Odyssey 是本阶段终点,Mindmap 是它的原料,没有数据就没有 Mindmap。
开场
这是 Phase 3 探索的第一步。我们从你的高能量活动里选 1-2 个作为核心词,向外做 3 层联想,追求跨界和荒诞。 目的不是找答案,是拉宽你的想象边界。
流程
Step 1: 选核心词
读 compass/energy-map.md 和 journal/aeiou_*.md,列出用户的心流区 + 高能量活动。
问:
这些里面,哪 1-2 个词你最想拉宽看看? (建议挑用户反复提到的动作词或主题,不是职位)
Step 2: 第一层发散(每个核心词 5-7 个词)
说到 [核心词],你脑子里第一层跳出的词是什么?不做判断,说 5-7 个。
不要先给用户你的建议。沉默等用户。如果用户卡住 60 秒,给 1 个相邻但不偏的词破冰。
Step 3: 第二层(每个第一层 3-5 个)
从 [第一层的 X] 再往外扩,什么会让你想到?
鼓励跨界:允许跳到电影、食物、动物、历史人物、风景。
Step 4: 第三层(每个第二层 2-3 个)
再扩一层。现在可以荒诞 —— 职业、地点、生活方式、动作,都行。
Step 5: 找组合惊喜(关键)
扫最外层词,问:
这些最外层的词里,有没有两三个放在一起让你产生一丝好奇的组合? 不是"这很合理",是"哎这个组合有点意思"。
用户挑 2-3 个组合。
Step 6: 提炼 HMI 问题
每个有意思的组合,引导用户改写成 How Might I 问题:
"我怎样才能 [动作] + [领域] + [约束]?"
好样本:
- "我怎样才能在不辞职的情况下,用一个月测试下做产品经理是什么感觉?"
- "我怎样才能在一年内既做原职又做播客?"
坏样本:
- "我怎样才能变成一个成功的人?"(太空泛)
- "我要做 XXX"(不是问题,是宣言)
目标:3-5 个 HMI 问题。
硬约束
- 禁止 Claude 替用户发散(会污染用户自己的联想)
- 允许荒诞 —— 越跨界越好
- 发散时禁止用户自我批判("这太蠢了"不允许,拒绝筛选,先堆料)
- HMI 必须具体到能在 2 周内设计一个原型来验证
产出
odyssey/YYYY-MM_mindmap.md:
---
date: YYYY-MM-DD
exercise: 3.1 mindmap
phase: 3
---
正文:
- 核心词(1-2 个)
- 第一层 / 第二层 / 第三层(缩进或 bullet)
- 有意思的组合(2-3 组)
- HMI 问题(3-5 个) —— 后续 Odyssey 和 Prototype 的原料
收尾
- 不强更 PROGRESS.md
- 建议 commit:
chore: 完成 Phase 3.1 Mindmap —— HMI 问题就位 - 下一步:
/life-design-coach-odyssey基于这些 HMI 搭 3 个 5 年方案
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 103 lines · 90 tokens per session scan A 8c5457e73017
life-design-coach-mindmap is a skill published in the GitHub repository TeigenZhang/life-design-coach (11 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 1,072 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…