skills/samber_cc-skills-golang
1
0
Fork 0
mirror of https://github.com/samber/cc-skills-golang.git synced 2026-09-11 19:46:44 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: invoke writing-clearly-and-concisely before skill prose edits

Browse Source 
Mirrors the rule added to the global CLAUDE.md so skill body prose gets Strunk's clarity pass before it lands.
This commit is contained in:
Samuel Berthe
2026-09-05 02:58:40 +02:00
parent bac46b0bed
commit 22c58a55a0
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+1
View File
@@ -238,6 +238,7 @@ Polanyi's paradox: most operational knowledge is tacit and resists explicit desc
### Body writing style ### Body writing style
- **Invoke `/writing-clearly-and-concisely` before writing or editing skill body prose** — Strunk's clarity rules (active voice, concrete language, omit needless words) catch what the checklist below doesn't.
- **Write imperatively, verb first** — `Run`, `Reject`, `Validate`. (→ See [Format 5: Imperative Prose](#format-5-imperative-prose).) - **Write imperatively, verb first** — `Run`, `Reject`, `Validate`. (→ See [Format 5: Imperative Prose](#format-5-imperative-prose).)
- **Explain why, not just what** — reasoning-based instructions let the model handle edge cases you did not foresee. (→ See [Teach reasoning, not only rules](#teach-reasoning-not-only-rules), which also rules on caps-lock imperatives.) - **Explain why, not just what** — reasoning-based instructions let the model handle edge cases you did not foresee. (→ See [Teach reasoning, not only rules](#teach-reasoning-not-only-rules), which also rules on caps-lock imperatives.)
- **Use one term per concept** — mixing "field"/"box"/"element" for the same thing costs accuracy. - **Use one term per concept** — mixing "field"/"box"/"element" for the same thing costs accuracy.