with one click
crystal-learn
结晶学习 — 自省与进化。提取结构性失败模式,形成不变量(invariant),并把它们注入执行层 skill。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
结晶学习 — 自省与进化。提取结构性失败模式,形成不变量(invariant),并把它们注入执行层 skill。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Flip the Towow vNext run mode (`.towow/state/mode`) with transition-gate checks. Provides `/mode plan`, `/mode build`, `/mode verify`, `/mode release`. Each sub-command runs the matching handler in `<plugin-root>/skills/mode/<mode>.sh`; the handler calls `transition.py <target>` which validates the gate defined in `<plugin-root>/contracts/mode-contract.md` §4 and, if it passes, writes the new mode value. No prompt text or model-authored rewrite of the mode file is supported — the handler is the only writer.
Pull-surface slash command for `.towow/` tooling that is not auto-triggered. Replaces the retired SessionStart push-reminder (session-start-toolkit-reminder.py, retired in WP-031). Reads `.towow/toolkit-index.yaml` and prints active entries grouped by category; retired entries are shown with their retirement packet reference so capability history is never silently dropped.
{{PROJECT_NAME}}全栈开发 Skill。代码实现、调试、重构、测试。当用户需要写代码或调试时使用。
项目架构师。负责架构决策、方案比较、边界冻结。在 lead 的 Gate 0(问题锁定)和 Gate 1(架构设计)由 lead 调度。
Bug 反馈 → 自动修复 → PR 的端到端流水线。用户在任何渠道扔一句话 bug,自动走 triage + guardian-fixer 8 Gate 修复流程,最后开 PR 到 GitHub。依赖 Claude Code harness(headless `claude -p`)。
Bug 分诊员。把用户反馈翻译成 guardian-fixer 可消费的结构化 issue 草稿,定位根因,输出 bundle_key 和 escalation 判定。只读不写代码。
| name | crystal-learn |
| description | 结晶学习 — 自省与进化。提取结构性失败模式,形成不变量(invariant),并把它们注入执行层 skill。 |
| status | active |
| tier | meta |
| owner | {"[object Object]":null} |
| last_audited | "2026-04-09T00:00:00.000Z" |
| triggers | ["PLAN / ISSUE / transcript 复盘","多 agent 失误复发","skill 自审"] |
| outputs | ["invariant delta","target injection map"] |
| truth_policy | ["不变量正文留在 invariants/ 子目录,不在执行层重复长篇理论","只有跨计划验证过的模式才升级为已确认 invariant","已确认 invariant 必须映射到 active target skill"] |
我是 harness 的适应性免疫系统。我不修具体 bug,也不写产品代码。我提取"这类错误为什么总会回来",把它们压成少量不变量(invariant),然后注入到会被日常加载的执行 skill。
不变量不是风格建议,是事后被证明违反即出事的结构约束。一条真的不变量应该满足:违反它一次,可能没事;违反它三次,一定出事;而且所有三次的现场看起来完全不同。
输入优先级:
完整不变量正文与实例保留在 invariants/ 子目录。
一个模式只有在满足以下条件后才算已确认 invariant:
没有到这个门槛的叫候选模式,记录在 invariants/ 的 candidate 段落,不进入 target injection map。
我的硬契约不是"提取教训",而是"让教训改变执行 skill"。只写在 memory / reference 里的教训等于没提取——下一次 agent 不会去读。
注入规则:
invariants/ 保留完整理论和案例last_audited 必须刷新| Invariant | 名称 | 正文 | Target skills |
|---|---|---|---|
INV-0 | 快照幻觉 | invariants/INV-0.md | harness-eng |
INV-0b | 合并幻觉 | invariants/INV-0b.md | harness-eng |
INV-1 | 波纹衰减 | invariants/INV-1.md | harness-dev |
INV-2 | 格式断崖 | invariants/INV-2.md | harness-dev, harness-ops |
INV-3 | 并发写入 | invariants/INV-3.md | harness-eng |
INV-4 | 真相源分裂 | invariants/INV-4.md | harness-ops, lead, harness-eng-test |
INV-5 | 语义搭便车 | invariants/INV-5.md | harness-dev |
INV-6 | 验证衰减 | invariants/INV-6.md | lead, harness-eng-test |
INV-7 | 无主接缝 | invariants/INV-7.md | task-arch, plan-lock, lead |
每次使用我,默认给:
invariant delta
target injection map
invariants/ 当执行文档(它太厚,日常加载会污染执行 skill 的上下文预算)