菜单
forge skill yaml description fields for claude code routing. use when drafting, shortening, or auditing metadata that must distinguish a skill from nearby skills, remove filler or duplicated trigger language, prevent overbroad activation, and return a revised description with a deletion note.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
The review lens for judging any code, seal, or story against the storage architecture's caliber — not "did it pass the meter" but "is this the best it can be." Use when QA'ing a sealed task, assessing a story, or judging whether built code rises to decisions.md and the storage architecture. Not a checklist pass; a wisdom pass.
Ideal target-state file map for KyzoDB — where each seat lives and what it owns. Use before placing a construct, naming a file, choosing a zone, or judging whether code sits in the wrong place. Not current-tree inventory (read the tree) and not per-construct coding law (rust-* skills).
Create precise, high-context direction for LLMs as Q/A/E triplets — the hardest question, the ruled answer, the enforcement that makes it stick. Use when writing specs, rulings, migration destinies, agent priming, review standards, or any context where an LLM must make a choice exactly the way you would.
Gate whether a working set of atoms/clusters is closed under dependency edges (OPEN lists crossings). Use after organize-work when the border must be a real min-cut. Not organize-work. Not architecture-design.
Hoist all reads to session entry and sink all writes to session exit around a pure Decision middle. Use when a host/session path mixes IO with meaning. Not name-and-seat-construct. Not organize-work.
Name a construct's kind of truth and seat it in exactly one zone (KEEP or SPLIT). Use when placing or splitting a type/module/bag under zone law and future pressure. Not io-inversion. Not architecture-design. Not organize-work.
| name | description-forger |
| description | forge skill yaml description fields for claude code routing. use when drafting, shortening, or auditing metadata that must distinguish a skill from nearby skills, remove filler or duplicated trigger language, prevent overbroad activation, and return a revised description with a deletion note. |
Write skill YAML description fields as discriminators, not summaries.
Find the routing difference first. Write only that.
A description exists to make Claude choose this skill instead of nearby skills. It should capture owned requests and reject adjacent ones through precise artifact, intent, output, and situation language.
Before drafting, identify:
Then write the shortest description that preserves those distinctions.
Delete any word or phrase that does not do routing work.
Remove:
Do not replace deleted language with new language unless it fixes a real routing miss.
A description passes only when each phrase answers one of these:
If two phrases answer the same question, keep the sharper one.
When revising, return the description and a short deletion note.
When analyzing only, identify filler, duplication, collision risk, and missing discriminants without rewriting.
