菜单
Audit product texts (skills, references, READMEs, rules) against the expression-style disciplines — unexplained coined terms, transliterated loan-words, semicolons, source-citation leaks. Use when asked to 黑话审计 / style audit / 审查表达风格 / check the writing style, or before shipping a batch of skill copy.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/liustack/vibemaster --skill style-audit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Cross-domain root-cause diagnosis for bugs, data mismatches, metric anomalies, and recurring problems, found before touching a fix. Use when the user says 查不出原因 / 有时好有时坏 / 数对不上 / 指标掉了 / 为什么又坏了 / 反复出现 / 改了还是不行 / 一直报错 / dig into this / debug this / why does this keep failing. Do not trigger for concept-explanation whys (why-is-the-sky-blue knowledge questions), first-time errors with obvious messages (the error already states the fix), known-cause fixes (coding's job), or debugging the harness session itself (built-in /debug's job).
Shape an unformed intent into something actionable, whether a requirement spec, a solution design, or a set of genuinely different candidates. Use when the user runs /shaping, or asks to 需求澄清 / 讨论一下这个需求 / 把想法变具体 / 给我出个方案 / 技术选型 / 这个功能有没有必要 / 值不值得做 / 想点子 / 帮我起个名 / brainstorm / turn this idea into a spec / help me scope this, or when an open scoping, placement, or naming question rides inside a larger build request (该放哪 / 是 A 还是 B 还是分组 / X 和 Y 怎么定义), shape that question first, then execute the rest. Do not trigger for executing an existing spec, reviewing documents, direct answers, life or career decisions, or pure delivery of settled content. Describing a problem is not a summons, but asking one is, even from inside an execution list.
Development discipline from plan to green. New behaviour and known-cause fixes go red-green-refactor with the failing test watched red first, pure refactors go green-to-green with no manufactured red, and how-should-I-write-this questions get verified against current sources before answering. Use when the user says 写个新功能 / 修个 bug / implement this / 重构这段 / TDD / 该不该先写测试 / 这个 API 现在的推荐写法 / 你确定吗 (a correction right after a code change). Do not trigger for unknown-cause anomalies (dig's job), unsettled requirements (shaping's job), pure config or docs edits, or explaining concepts.
基于 SOC 职业分类
正在显示 SKILL.md
| name | style-audit |
| description | Audit product texts (skills, references, READMEs, rules) against the expression-style disciplines — unexplained coined terms, transliterated loan-words, semicolons, source-citation leaks. Use when asked to 黑话审计 / style audit / 审查表达风格 / check the writing style, or before shipping a batch of skill copy. |
Project-local authoring tool. The shipped product lives in skills/ — this skill never ships with it.
scripts/check-style.sh is the mechanical layer: a banned-term list plus a semicolon check, wired into CI. It only knows what audits have already found.BANNED in scripts/check-style.sh, so it can never come back.rules/plain-language.md): everyday words over terminology — the test is whether a reader outside the project understands without looking anything up. Coined labels and metaphors must be explained in the same sentence on first use. Foreign material is described in your own words, not transliterated into a pet noun.rules/punctuation.md): no semicolons in prose. The script catches this — spot-check only.git diff --name-only), or all of skills/, rules/, README* on request. .zh-CN translations are held to the same bar.BANNED in scripts/check-style.sh — in both stacks if it appeared in both.bash scripts/check-style.sh and confirm green before committing.