From 265aa46f63f67d6998f2e1b9695577622d2f12e2 Mon Sep 17 00:00:00 2001 From: uriah-dev Date: Sat, 14 Nov 2026 03:56:38 +0000 Subject: [PATCH] pstack/unslop: restrict dash overuse and add rule against underlines and underscores --- pstack/skills/unslop/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pstack/skills/unslop/SKILL.md b/pstack/skills/unslop/SKILL.md index 97f5b64121..ec4a161d53 100644 --- a/pstack/skills/unslop/SKILL.md +++ b/pstack/skills/unslop/SKILL.md @@ -28,13 +28,14 @@ Rule numbers are stable ids that other skills cite. A removed rule leaves a gap. ### Style -13. **Em dash overuse.** Avoid em dashes entirely. Use periods or commas only (no parentheses, no en dashes, no hyphen-as-dash substitutes). If a thought needs separation, end the sentence or use a comma. +13. **Dash overuse.** Avoid em dashes (—), en dashes (–), and hyphens used as thought connectors or dividers entirely. Use periods or commas only (no parentheses, no hyphen-as-dash substitutes). If a thought needs separation, end the sentence or use a comma. 14. **Colon overuse.** Colons are fine before a list or example, not as mid-sentence connectors. "If you're coming from traditional automation: instead of registering event handlers, you describe conditions" adds nothing with the colon. Rewrite to let the point stand on its own without comparison framing. "Describing when the scheduler should fire works best as plain English." Same meaning, no crutch punctuation. 15. **Boldface overuse.** Don't bold every proper noun or acronym. 16. **Inline-header lists.** The tell is a bold label and colon that restates the line: "**Performance:** Performance improved...". Convert those to prose. A bold lead-in that ends in a period, names the item, and is followed by genuinely new detail ("**Schema in TypeScript.** Tables live in one file.") is fine, not a tell. 17. **Title case headings.** Use sentence case. 18. **Decorative emojis.** Remove from headings and bullets. 19. **Curly quotes.** Use straight quotes. +34. **Underlines and underscores.** Do not use underlines (``), markdown underscores (`_text_`), or underline dividers (`---`). Use bold (`**`) or plain text for emphasis, and blank lines instead of horizontal rules. ### Communication artifacts