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-coherence/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-coherence)<a href="https://agentmods.dev/skills/teigenzhang/life-design-coach/life-design-coach-coherence"><img src="https://agentmods.dev/badge/skills/teigenzhang/life-design-coach/life-design-coach-coherence/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-coherence"><img src="https://agentmods.dev/badge/skills/teigenzhang/life-design-coach/life-design-coach-coherence.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.00086 | $0.00896 |
| Opus 5 | $0.00043 | $0.00448 |
| Sonnet 5 | $0.00017 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
life-design-coach-coherence 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
罗盘校准 · Coherence Check
Phase 1.4 · 30-60 分钟 · 产出：
compass/coherence.md
前置条件（必须）
compass/workview.md 和 compass/lifeview.md 都已存在。
如果缺：引导用户先做 /life-design-coach-workview 或 /life-design-coach-lifeview，不要硬跑。
开场
我们把你的 Workview 和 Lifeview 并在一起看 —— 找两者一致的地方（= 你的方向）和冲突的地方（= 待探索的盲区）。 然后提炼 2-3 条"设计原则"，以后做决策时拿这几条过一遍。
流程
Step 1: 读原文
Read 两份文档。向用户复述核心摘要（不添油加醋）。
Step 2: 找一致
Workview 里你说 [摘要 A]，Lifeview 里你说 [摘要 B] —— 它们哪里是一致的？
追问：
- "这个一致告诉你什么？"
- "你目前的生活，在多大程度上活在这个一致里？"
Step 3: 找冲突
两者有哪里是矛盾的？
追问：
- "这个矛盾在你实际生活里什么时候最明显？"
- "你通常怎么处理？"
冲突不一定要解决 —— 有些冲突是人生的核心张力，是个体特征不是缺陷。
Step 4: 提炼设计原则
基于一致区，你能总结出 2-3 条 以后做重大决策时必须遵守的原则吗？
原则的好样本：
- ✓ "我做的事必须对真实的人产生可见的影响"
- ✓ "我的工作不能压缩到我陪孩子的时间少于每周 5 小时"
- ✗ "我要成功"（不可验证）
- ✗ "我要平衡"（空话）
每条原则必须：
- 可用于事后判断（某个决策是否违反它）
- 是你的，不是社会共识的
- 具体到能执行
Step 5: 记录冲突区
未解决的冲突 → 写进文档，留给未来观察。
硬约束
- 禁止替用户找一致 / 冲突
- 禁止把冲突当成要"修复"的 bug
- 原则必须由用户自己写，Claude 只做精炼语言的副本
- 禁止列超过 3 条原则（越多越无效）
产出
compass/coherence.md：
---
date: YYYY-MM-DD
exercise: 1.4 coherence
phase: 1
---
正文结构：
- 一致区（1-3 条）
- 冲突区（1-3 条，标明"未解决"或"核心张力"）
- 设计原则（2-3 条） —— 后续所有决策的标尺
- 下一步观察：哪些冲突需要后续留意
收尾
- 更新
PROGRESS.md的"当前罗盘"部分，把设计原则填进去 - 建议 commit：
feat: 完成 Phase 1.4 罗盘 —— 设计原则就位 - 告诉用户：Phase 1 定位结束，下一步进入 Phase 2 寻路，核心是
/life-design-coach-journal连续记 3 周
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 · 93 lines · 86 tokens per session scan A 79d2f80deaf3
life-design-coach-coherence is a skill published in the GitHub repository TeigenZhang/life-design-coach (11 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 896 once invoked, about $0.0004 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…