Skip to content
T1KTheOneKit

human-writing-before-send

Activate Human-Writing Before Any Email / Message / Post / Pitch Deck / Proposal / Presentation

Section titled “Activate Human-Writing Before Any Email / Message / Post / Pitch Deck / Proposal / Presentation”

Always-loaded companion to the human-writing-reminder.cjs hook. The hook fires only on UserPromptSubmit; mid-turn injected user messages (the “The user sent a new message while you were working” path) are NOT UserPromptSubmit events, so the hook reminder never fires for them. This rule closes that gap — it is in context every session regardless of the hook.

Rule

Section titled “Rule”

Before you draft, finalize, or send ANY email, chat message, LinkedIn/X post, pitch deck, proposal, slide deck, presentation, one-pager, cover letter, or other human-facing prose, activate the t1k-human-writing skill (guide mode for a fresh draft, lint mode for an existing one). This applies even when:

  • The request arrived as a mid-turn injected message (no hook reminder appeared), OR
  • You are composing the draft yourself rather than editing a pasted one, OR
  • The message “looks routine” (invoice cover notes, quick replies, acknowledgements).

Why: AI-authored business prose reliably accumulates AI tells (em-dashes first among them), and the hook misses mid-turn injections and deliverable nouns it predates — both burns documented in docs/human-writing-before-send.md.

How to apply

Section titled “How to apply”
  1. Recognize the trigger: any email/message/post/pitch deck/proposal/presentation is about to be drafted or sent.
  2. Activate t1k-human-writing FIRST — do not draft prose before it.
  3. Hard check before finalize: zero em-dashes in outbound prose bodies; no slop vocabulary, no rule-of-three, no throat-clearing opener, no summary-conclusion closer.
  4. Slide-deck nuance: on a deck, an em-dash in a badge/title/stat separator (“Growth — 15%”) is fine — it is a layout device, not a prose tell. The real deck tell is a repetitive “statement — punchline” ending on card after card, plus rule-of-three bullets and slop headline vocab. Kill the repetition and vary the card endings; don’t blanket-ban the dash in separators.
  5. Match the author’s real voice (voice-inject from their past sends when available).
Section titled “Related”
  • ~/.claude/skills/t1k-human-writing/SKILL.md — the skill itself (guide + lint modes)
  • hooks/human-writing-reminder.cjs — the UserPromptSubmit hook this rule backstops
  • rules/image-analysis-routing.md — the parallel always-loaded-rule + hook pattern