菜单
Make an instruction line read cold: clarify it into plain words, then tighten it to one positive line. TRIGGER when: user says 'tighten/clarify this rule/fact', 'make this leaner/simpler/clearer', 'de-jargon this' in a skill, CLAUDE.md, agent prompt, or rule file.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | tighten-instruction |
| description | Make an instruction line read cold: clarify it into plain words, then tighten it to one positive line. TRIGGER when: user says 'tighten/clarify this rule/fact', 'make this leaner/simpler/clearer', 'de-jargon this' in a skill, CLAUDE.md, agent prompt, or rule file. |
Two passes in order: clarify the line into plain words, then tighten it to one line — clarity first, so tightening never compresses back into jargon.
State the goal in one sentence: what should the reader do or know after reading it?
Clarify — make every phrase read cold (clear on its own). Decompose the line into phrases; name each phrase's intended meaning and fix any that won't land:
Spend length here when it buys comprehension; preserve the meaning exactly.
Tighten — cut what the clear line doesn't need. Drop any line whose purpose is "restate the goal," "hedge," or "explain why"; collapse clauses the positive form already implies; rename a heading that misnames its content. Never trade a plain word back for jargon to save space.
Before: "Run tests after edits. Don't skip even for small changes — small changes break things too." After: "Run tests after every edit."
Land on one positive line — in the shape the content wants:
Test it cold. Read the final line without surrounding context — every phrase obvious, the whole line actionable. If not, redo.
Run the live testing phase after execute-plan ships a build — drive the spec's '### Post-ship verification' checklist (the human-gated ACs the diff can't prove) to pass/fail across three tiers: unit/frontend, real authenticated app, and server-log/DB. TRIGGER when: a shipped spec's Post-ship verification list needs behavioral testing; user says 'test the completed plan', 'run the testing phase', or 'verify the shipped spec'. SKIP for code review (use two-pass-review) or re-verifying code-gated ACs settled at the ship gate.
After finishing a coding task or plan, audit code comments and durable docs (CLAUDE.md, .claude/rules, ARCHITECTURE.md) for the changed files; propose scoped adds/updates/trims the user approves. Change-scoped, not a repo-wide doc sweep. TRIGGER when: user asks to update/sync durable docs, code comments, or CLAUDE.md after finishing work.
Implement a feature by executing its wave-grouped plan.md. TRIGGER when: user says 'run the plan', 'execute the plan', or 'implement it'; a plan.md has unchecked waves ready to build.
Keep a long execute-plan run alive across context windows: from a separate chat, watch the shared mailbox and respawn a fresh orchestrator whenever the run pauses at a wave boundary. TRIGGER when: user says 'supervise the plan run' or 'babysit the plan'.
Explain a feature, flow, or concept by grounding in source-of-truth, leading with the answer, and diagramming each load-bearing mental model. TRIGGER when: user says explain/walk me through/ELI5/help me understand; user wants to understand how a feature, flow, or system works. SKIP when: user wants a diagnosis/fix/action; user wants a one-line definition they can already apply; quick spot-check or confirmation.
Audit past Claude Code transcripts in a chosen scope and date window to extract reusable patterns, then walk through each one to promote it into a slash command, CLAUDE.md rule, memory entry, or new skill. Use when the user wants to retrospectively mine sessions for workflow improvements, recurring corrections, validated approaches, or repeated procedures worth capturing. Also counts how often a skill ran across past sessions.
