@thedecipherist/claude-packs 0.0.0-stage → 1.0.0

package/packs/websocket/checks/stale-socket-deletes-new-entry.json

@@ -0,0 +1,25 @@
+{
+  "id": "stale-socket-deletes-new-entry",
+  "why": "A dead socket's late close must not delete its reconnected successor's entry.",
+  "rule": ".claude/rules/identity-comes-from-the-connection.md",
+  "globs": [
+    "**/*.ts",
+    "**/*.js",
+    "**/*.mjs",
+    "**/*.cjs"
+  ],
+  "exclude": [
+    "**/tests/**",
+    "**/test/**",
+    "**/*.test.*",
+    "**/*.spec.*",
+    "**/e2e/**",
+    "**/node_modules/**",
+    "**/dist/**",
+    "**/build/**",
+    "**/.next/**"
+  ],
+  "pattern": "\\.on\\(\\s*['\"]close['\"](?:(?!===\\s*ws\\b)[\\s\\S]){0,120}?\\.delete\\(\\s*(?:connectionId|key|id|hostname)\\s*\\)",
+  "bad": "ws.on('close', () => {\n  connections.delete(connectionId);\n});",
+  "good": "ws.on('close', () => {\n  if (connections.get(connectionId)?.ws === ws) connections.delete(connectionId);\n});"
+}

package/packs/websocket/checks/ws-identity-from-message.json

@@ -0,0 +1,26 @@
+{
+  "id": "ws-identity-from-message",
+  "why": "Identity comes from the authenticated connection, and a message can only name what that connection owns.",
+  "rule": ".claude/rules/identity-comes-from-the-connection.md",
+  "globs": [
+    "**/*.ts",
+    "**/*.js",
+    "**/*.mjs",
+    "**/*.cjs"
+  ],
+  "exclude": [
+    "**/tests/**",
+    "**/test/**",
+    "**/*.test.*",
+    "**/*.spec.*",
+    "**/e2e/**",
+    "**/node_modules/**",
+    "**/dist/**",
+    "**/build/**",
+    "**/.next/**"
+  ],
+  "pattern": "\\b\\w+\\(\\s*msg\\.(?:agent_id|user_id|company_id|tenant_id|command_id|session_id)\\b",
+  "bad": "streamManager.updateHeartbeat(msg.agent_id, msg.status);",
+  "good": "streamManager.updateHeartbeat(conn.agentId, msg.status);",
+  "kind": "security"
+}

package/packs/websocket/pack.json

@@ -0,0 +1,21 @@
+{
+  "name": "websocket",
+  "version": "1.0.0",
+  "description": "WebSocket services: identity comes from the connection, each message is authorised, and a connection map survives a reconnect.",
+  "type": "stock",
+  "author": "claude-packs",
+  "license": "MIT",
+  "homepage": "https://github.com/TheDecipherist/claude-packs",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/TheDecipherist/claude-packs.git",
+    "directory": "packs/websocket"
+  },
+  "keywords": [
+    "websocket",
+    "security"
+  ],
+  "engines": {
+    "claude-packs": ">=0.25.0"
+  }
+}

package/packs/websocket/rules/identity-comes-from-the-connection.md

@@ -0,0 +1,24 @@
+---
+paths:
+  - "**/*.ts"
+  - "**/*.js"
+  - "**/*.go"
+---
+
+# Identity comes from the connection, and every message is authorised
+
+<constraints>
+Always do:
+- Take who is speaking from the authenticated connection.
+- Check a role per message type, as a route would.
+- Bind a session to its owner, and send its output only to that owner.
+- Re-check at token expiry and when a user is disabled.
+- Delete a connection entry only if it is still this socket: `if (map.get(id)?.ws === ws) map.delete(id)`.
+
+Never do:
+- Trust an id, a hostname or a role inside a message.
+- Send a token in the URL.
+</constraints>
+
+## Check
+`ws-identity-from-message`, `stale-socket-deletes-new-entry`, `no-token-in-query`.

package/packs/writing/checks/ascii-no-em-dash.json

@@ -0,0 +1,17 @@
+{
+  "id": "ascii-no-em-dash",
+  "why": "The cleanest AI tell there is: em dashes are in 0-0.5% of human posts and 97% of LLM-flagged ones. Use a comma, a parenthetical or a period. Smart quotes and the ellipsis character are not ASCII either.",
+  "rule": ".claude/rules/ascii-no-em-dash.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "[\\u2013\\u2014\\u2018\\u2019\\u201c\\u201d\\u2026]|\\s--\\s",
+  "bad": "It works \u2014 most of the time.\nIt works -- most of the time.\n",
+  "good": "It works, most of the time.\nRun `npm test -- a.test.mjs` and see [the docs](https://x.dev/a--b).\n\n```sh\nnpm test -- a -- b\n```\n"
+}

package/packs/writing/checks/no-copula-dodging.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-copula-dodging",
+  "why": "\"serves as\", \"stands as\", \"functions as\" and \"boasts\" are is and has in a costume.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:serves as|stands as|functions as|boasts)\\b",
+  "bad": "The file serves as the entry point.\n",
+  "good": "The file is the entry point.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-dramatic-colon.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-dramatic-colon",
+  "why": "Dramatic colon setups are measured at literal zero in human text. Write a normal sentence.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "(?:^|[.!?]\\s+)The (?:reality|truth|catch|kicker|twist|lesson|takeaway|problem|result):\\s",
+  "bad": "The reality: nobody cares.\n",
+  "good": "Nobody cares.\nThe result of the run: `ok`.\n",
+  "flags": "m"
+}

package/packs/writing/checks/no-not-x-but-y.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-not-x-but-y",
+  "why": "Mirrored constructions read generated. Make it a plain statement.",
+  "rule": ".claude/rules/rhythm-like-talk.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\bnot (?:just |only |merely )?[^.,;\\n]{1,40}, but\\b|\\bit(?:'s| is) not [^.\\n]{1,40}\\.\\s+it(?:'s| is)\\b",
+  "bad": "It's not a bug. It's a band-aid.\nThis is not a tool, but a way of life.\n",
+  "good": "It's a band-aid.\nIt is not done yet.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-participial-opener.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-participial-opener",
+  "why": "Instruction-tuned models open sentences this way at 2-5x the human rate (PNAS 2025). Start with the subject.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "(?:^|[.!?]\\s+)(?:Leveraging|Building on|Drawing from|Harnessing)\\b",
+  "bad": "Leveraging the cache, it runs fast.\n",
+  "good": "It runs fast from the cache.\n",
+  "flags": "m"
+}

package/packs/writing/checks/no-pseudo-wisdom.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-pseudo-wisdom",
+  "why": "Unfalsifiable, safe, empty. Delete it, or give the specific version.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:the key is finding|the right balance|one-size-fits-all|context is everything)\\b",
+  "bad": "The key is finding the right balance.\n",
+  "good": "Under 50 users, use the free tier.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-slop-words.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-slop-words",
+  "why": "The short slop list: these words read generated. The list does not grow.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:delv(?:e|es|ing)|tapestry|testament|landscape|journey|seamless(?:ly)?|robust|game-changer|crucial|dive into|unleash(?:es|ing)?|leverag(?:e|es|ing)|supercharg(?:e|es|ing))\\b",
+  "bad": "A robust way to leverage your data.\n",
+  "good": "A way to use your data that has not failed in a year of use.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-stock-connectors.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-stock-connectors",
+  "why": "Stock connectors measured at zero in human text. Delete them and say the thing.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:here's the thing|that said,|so here's what happened)",
+  "bad": "Here's the thing: it was slow.\n",
+  "good": "It was slow.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-time-or-date.json

@@ -0,0 +1,27 @@
+{
+  "id": "no-time-or-date",
+  "why": "No time or date references at all: they are a major AI tell. A duration the author states is the only exception.",
+  "rule": ".claude/rules/no-time-or-date.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*",
+    "articles/**",
+    "**/articles/**",
+    "blog/**",
+    "**/blog/**",
+    "posts/**",
+    "**/posts/**",
+    "content/**",
+    "**/content/**",
+    "drafts/**"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:in|last|this|next|since) (?:January|February|March|April|June|July|August|September|October|November|December)\\b|\\b(?:January|February|March|April|June|July|August|September|October|November|December|May) (?:\\d{1,2}, )?\\d{4}\\b|\\b(?:last|this|next) (?:year|month|week)\\b|\\b\\d+ (?:days?|weeks?|months?|years?) ago\\b|\\bat \\d{1,2}(?::\\d\\d)?\\s?(?:am|pm)\\b|\\brecently\\b",
+  "bad": "I started this last year, in June, at 11pm.\n",
+  "good": "I have been doing this for about 10 years.\nThe list may grow.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-trailing-ing.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-trailing-ing",
+  "why": "Fact, comma, then a participle that fake-analyzes. Cut everything after the comma; a real claim gets its own sentence with evidence.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": ",\\s+(?:highlighting|underscoring|showcasing|reflecting|ensuring|paving the way)\\b",
+  "bad": "It ships in one file, ensuring a smoother experience.\n",
+  "good": "It ships in one file.\n",
+  "flags": "i"
+}

package/packs/writing/checks/no-vague-attribution.json

@@ -0,0 +1,18 @@
+{
+  "id": "no-vague-attribution",
+  "why": "Name the source or drop the claim. Honest personal doubt beats borrowed authority.",
+  "rule": ".claude/rules/no-stock-language.md",
+  "concepts": [
+    "public-text"
+  ],
+  "globs": [],
+  "exclude": [
+    "**/node_modules/**",
+    "**/CHANGELOG*"
+  ],
+  "prose": true,
+  "pattern": "\\b(?:experts say|studies (?:have )?show(?:n)?|research suggests|it is widely regarded)\\b",
+  "bad": "Studies have shown it helps.\n",
+  "good": "I haven't seen good numbers on it.\n",
+  "flags": "i"
+}

package/packs/writing/pack.json

@@ -0,0 +1,43 @@
+{
+  "name": "writing",
+  "version": "1.0.0",
+  "description": "Text that goes public reads like a person wrote it: cadence, voice, stance for replies, structure for posts. Rules, one-job skills and checks on public text.",
+  "type": "stock",
+  "author": "claude-packs",
+  "license": "MIT",
+  "homepage": "https://github.com/TheDecipherist/claude-packs",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/TheDecipherist/claude-packs.git",
+    "directory": "packs/writing"
+  },
+  "keywords": [
+    "writing",
+    "voice"
+  ],
+  "engines": {
+    "claude-packs": ">=0.19.0"
+  },
+  "folders": {},
+  "concepts": {
+    "public-text": [
+      "README*",
+      "**/README*",
+      "**/*.mdx",
+      "docs/manual/**",
+      "docs/guide/**",
+      "docs/guides/**",
+      "manual/**",
+      "content/**",
+      "blog/**",
+      "posts/**",
+      "articles/**",
+      "drafts/**"
+    ]
+  },
+  "skillsIn": null,
+  "hooks": {},
+  "optIn": [
+    "checks/no-time-or-date.json"
+  ]
+}

package/packs/writing/rules/ascii-no-em-dash.md

@@ -0,0 +1,21 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# ASCII only, and never an em dash
+
+The cleanest discriminator there is: em dashes are in 0-0.5% of human posts and 97% of LLM-flagged ones.
+
+<constraints>
+Always do:
+- Use a comma, a parenthetical or a period instead. Parens are the natural aside (half of real posts have one) but don't prove humanity; slop overuses them too.
+- Keep to ASCII: straight quotes, three dots, a plain hyphen.
+
+Never do:
+- Write an em dash, or " -- " in its place.
+</constraints>
+
+## Check
+`ascii-no-em-dash` (lesson check; code and URLs are left out).

package/packs/writing/rules/cut-the-padding.md

@@ -0,0 +1,20 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# Cut about half: say the thing, one concrete consequence, stop
+
+AI-ness is not in individual words; it is in cadence: padding, symmetry, hedging-by-committee, over-explaining. Fix rhythm and structure, not vocabulary. When a real sample of the target register exists, match it.
+
+<constraints>
+Always do:
+- Cut about half of a normal AI draft. Say the thing, name one concrete consequence, stop.
+- Write one vivid concrete line, not three explanatory sentences.
+- Use the verb: "make a determination" is determine, "provide an explanation" is explain.
+- Calibrate (measured): the median real comment is under 50 words, the median real post 100-125, LLM-flagged posts 230. A reply of more than a few tight sentences is probably too long. For a post the sub's norm wins: a 300+ word value post is fine and scores well. Cut padding, not substance.
+
+Never do:
+- Open with a wind-up or "great question", or restate the question.
+</constraints>

package/packs/writing/rules/direct-voice.md

@@ -0,0 +1,22 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# A direct voice: say it plainly, and sound like the author
+
+<constraints>
+Always do:
+- Get to the point fast. Never waste the reader's time. Assume they're smart enough to keep up: easy to understand, never dumbed down.
+- Match their tone ("you get what you give"): polite to the polite, an edge for the smug. Facts never bend either way.
+- Make every piece self-contained: name the tool or problem up front, never assume the reader knows the thread.
+- Use plain words. No jargon like "prose", "deterministic", "probabilistic". If a normal person wouldn't say it out loud, don't write it.
+- Keep what is the author's own: the words, intensifiers and connectors they really use, read from their earlier writing.
+- Write "I", not "we", for one person's own projects, including their manual pages.
+- In casual channels only, an occasional "its" for "it's" or a dropped comma reads human (about 7% of real posts have a missing apostrophe; slop has flawless punctuation).
+
+Never do:
+- Force errors, or use them in bios, articles or anything polished.
+- Blame a vendor or a tool for what is a habit of the user or the model.
+</constraints>

package/packs/writing/rules/no-cargo-cult.md

@@ -0,0 +1,16 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# No cargo cult: these rules are about cadence, not a word list
+
+<constraints>
+Never do:
+- Ban common English words ("that", "just", "actually"): the bans break normal English.
+- Swap one canned phrase list for another; replacements become tells too.
+- Add bullets, an FAQ or headers to "sound organized". Real lists are fine and ragged.
+- Turn every hedge into a confident claim. Verify, then state it flat: manufacturing confident wrong statements is worse than sounding like AI.
+- Force casualness. Measured slop is already chattier and more contraction-heavy than real posts; piling on "super", "totally" and exclamation points is its own tell. Humans mix registers.
+</constraints>

package/packs/writing/rules/no-scaffolding.md

@@ -0,0 +1,19 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# Scaffolding is the slop shape; a real list is short and ragged
+
+Bullets do not kill posts (human posts with bullets slightly outscore those without, 4 vs 3); scaffolding does. Bold is in 5% of human writing vs about 30% of slop, headers in under 2%.
+
+<constraints>
+Always do:
+- Put receipts as specific numbers woven into prose, or one short ragged list: uneven item lengths, sometimes two items. When winners use bullets it is ONE short list of one-liners (top 20 text posts: 4 of 20 in r/ClaudeAI and r/ClaudeCode, 8 of 20 in r/mongodb, 6 of 20 in r/webdev and r/node; headers 2-4 of 20; median 140-240 words).
+- Write the rest as prose in short paragraphs. A 90-word bullet is a paragraph with a dash in front; make it prose.
+- On a manual page, put no heading directly under the title; the first heading comes where the subject changes.
+
+Never do:
+- Bold-header and numbered-bold skeletons, outside articles whose own guidelines require structure.
+</constraints>

package/packs/writing/rules/no-stock-language.md

@@ -0,0 +1,27 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# No stock language: say what is, name who said it
+
+<constraints>
+Always do:
+- Use is and has. "serves as", "stands as", "functions as", "represents", "marks" are **is**; "boasts", "features", "offers", "maintains" are **has**. If the sentence still works with is or has, it was padding.
+- Start a sentence with its subject.
+- Name the source, or drop the claim. Honest personal doubt ("I haven't seen good numbers on it") beats borrowed authority.
+- Replace filler with the specific version: "it depends on your needs" becomes "under 50 users, use the free tier".
+
+Never do:
+- Dramatic colon setups ("The reality: nobody cares."): measured at literal zero in human text.
+- Stock connectors ("Here's the thing", "That said", "So here's what happened"): also zero in human text. Delete them, say the thing.
+- Slop words, a short list that does not grow: delve, tapestry, testament, landscape, journey, seamless, robust, game-changer, crucial, dive into, unleash, leverage, supercharge.
+- Trailing "-ing" commentary: ", highlighting their commitment to...", ", ensuring a smoother experience", ", underscoring / reflecting / showcasing / paving the way for". Cut everything after the comma; a real claim there gets its own sentence with evidence.
+- Participial openers ("Leveraging the power of...", "Building on this...", "Drawing from..."): instruction-tuned models open this way at 2-5x the human rate (PNAS 2025).
+- Vague attribution: "experts say", "studies have shown", "research suggests", "it is widely regarded".
+- Pseudo-wisdom: "The key is finding the right balance", "there's no one-size-fits-all answer", "context is everything". State what happened; delete every clause explaining why it matters to the universe.
+</constraints>
+
+## Check
+`no-stock-connectors`, `no-slop-words`, `no-dramatic-colon`, `no-copula-dodging`, `no-trailing-ing`, `no-participial-opener`, `no-vague-attribution`, `no-pseudo-wisdom` (lesson checks).

package/packs/writing/rules/no-time-or-date.md

@@ -0,0 +1,18 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# No invented time or date
+
+<constraints>
+Always do:
+- Keep a date or a duration that is a real fact the reader needs: history, a release, a measured span.
+
+Never do:
+- Invent a time reference to sound lived-in: "last year", "in June", "at 11pm", "recently".
+</constraints>
+
+## Check
+`no-time-or-date` (a lesson check, opt-in): for an author who wants no dates at all in posts. Name `checks/no-time-or-date.json` in `"enable"`.

package/packs/writing/rules/rhythm-like-talk.md

@@ -0,0 +1,20 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# Rhythm like talk: no mirrored, tripled or aphoristic shapes
+
+<constraints>
+Always do:
+- Mix short, medium and long sentences the way talk does, and vary paragraph sizes: pair a long block with a one-liner.
+- Reuse the word. Humans hammer the same noun; LLMs rotate synonyms (measured: humans repeat their top content word about 50% more).
+- Catch any 3-item list: cut the third or expand past three, unless all three do distinct work.
+- Say an idea as an explanation ("the tokens aren't in the query, they're in everything Claude does around it when there's something it doesn't know").
+
+Never do:
+- Write uniform sentence lengths, or the overcorrection, the dramatic staccato ("It's not. It's a band-aid.").
+- Write "not X, but Y" mirrored constructions: make it a plain statement.
+- Write a punchline sentence, the line that sums a paragraph up as an aphorism: "the token tax exists only where there is something to know", "every one of those posts was somebody's evening gone". One exception: a tagline the user chose, as the last line.
+</constraints>

package/packs/writing/rules/write-from-your-own-corner.md

@@ -0,0 +1,20 @@
+---
+# concepts: public-text
+paths:
+  - "placeholder"
+---
+
+# Write from your own corner, end on the ask, hedge like a person
+
+Measured, as defaults.
+
+<constraints>
+Always do:
+- Write in first person from your own situation (about 90% of human posts), with oddly specific numbers ("200k users", "$900", "30/100"). Humans run 2.8x more first person than second; slop is near 1:1 and lectures "you". Round numbers read fake; specific ones read lived.
+- End on the question or a bare thanks. Comments just stop, often without terminal punctuation.
+- Keep self-anchored doubt where it is real: "not sure if this is a good idea tho", "afaik". A quarter to a third of real posts do it, and slop hedges LESS (it performs confidence).
+
+Never do:
+- Write a closing thought or a summary close: measured at about 0%.
+- Hedge symmetrically ("it depends on your use case"), or both-sides a claim the author holds.
+</constraints>

package/packs/writing/skills/argument-post/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: argument-post
+description: Use when writing an opinion piece, a post that argues a claim, or a post meant to travel beyond people who know the author.
+---
+
+# The argument post: what the 750k-view post did
+
+r/ClaudeAI, 935 pts, 165 comments.
+
+"Why are all the Claude Code skill files I see online completely
+pointless?" Two narrative posts by the same author in the same month did 13 and 8 points.
+The difference is the whole lesson:
+
+- **About the reader, not the author.** Everyone has a skill file; the
+  first three lines make every reader feel caught. An argument the reader
+  can test against their own setup in two seconds travels; a story about
+  what the author did gets read by people who care about the author.
+- **Shape:** one recognizable example everyone has seen (the quoted
+  boilerplate) -> one-line verdict -> one principle ("the point of a skill
+  is to fix something Claude consistently gets wrong") -> a short list of
+  specific things it gets wrong -> restatement -> a humble ask ("Am I
+  missing something?"). About 150 words. No numbers, no links, no
+  product, no disclosure needed.
+- **The list is the engine.** Four concrete one-liners from the author's domain;
+  every reader has a fifth, which is where the comments come from.
+- **The close lets people disagree without a fight,** so the argument
+  fills on both sides.
+- **Title = an opinion inside a question, about the reader's files.**

package/packs/writing/skills/humanize/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: humanize
+description: Use when text is about to go public or to someone else, a manual page, a README, an article, a post, a reply, an email, a bio, or when asked whether something sounds like AI or to make it sound human.
+---
+
+# Humanize: the last pass on anything that goes public
+
+The rules on public text set the cadence (`cut-the-padding`, `rhythm-like-talk`, `no-stock-language`, `no-scaffolding`, `no-time-or-date`, `ascii-no-em-dash`, `write-from-your-own-corner`, `direct-voice`, `no-cargo-cult`). This is the pass over the finished draft. Not for code, commit messages, config or internal specs, logs and briefs: those stay plain.
+
+Why it matters: readers trust a voice that sounds like a person, generic text sinks in a crowded channel, and moderators remove what reads as slop.
+
+<constraints>
+Always do:
+1. Before publishing for an employer or a client, run their review track. Cadence and voice stay here.
+2. Run the cadence check:
+   - em dashes gone; no "not X but Y"; triads cut; no summary close (end on the ask or the last point); no punchline sentences; no colon drama; no stock connectors or slop words;
+   - sentence and paragraph shapes varied, no staccato performance; repeated terms NOT thesaurus-varied;
+   - more I/we than you/your unless the medium demands otherwise, and "I" not "we" for the author's own projects;
+   - padding cut: could it be said in half the words; self-contained; ASCII only; no invented time or date.
+3. Run the spot tests on any suspect sentence:
+   - **Deletion test:** remove it. Paragraph loses nothing: it was filler.
+   - **Genericity test:** swap the names, tool and subject for any other. Sentence still reads fine: it says nothing; make it specific or cut.
+4. Run the substitution sweep: any "serves as / stands as / boasts / features" that survives an is/has swap gets swapped; any trailing "-ing" commentary after a comma goes; any unnamed "experts / studies" gets a name or the claim goes.
+5. Deliver it clean. Reasoning, stance checks and notes stay OUTSIDE the final text. The text the author will use goes in its own fenced code block with NOTHING else in it. Longer deliverables go out as .md files, never as artifacts.
+
+Never do:
+- Mix draft and explanation in one block.
+</constraints>