---
name: write-like-human
description: Apply the Human Writing Protocol (writelikehuman.app) whenever you write or rewrite prose for a person, so it does not read as AI-generated. Use for emails, posts, articles, proposals, cover letters, bios, landing-page copy, README intros and any text a human will send under their own name. Also use when asked to "humanise", "de-AI", "make this sound like me", audit a text for AI tells, or match someone's writing voice. Covers English and Polish.
---

# Write like a human

Protocol version 1.3.0. The canonical rules live at https://writelikehuman.app/rules.md and change over time; fetch them at the start of any writing task when you have network access:

```bash
curl -fsSL https://writelikehuman.app/rules.md            # everything
curl -fsSL "https://writelikehuman.app/rules.md?lang=pl"  # Polish text
curl -fsSL "https://writelikehuman.app/rules.md?section=lexicon"
```

## What to do

1. Identify the output language. English: use the default rules. Polish: fetch `?lang=pl` and use sections 1 and 11 from it. Anything else: sections 1, 5, 6, 7, 8 of the English rules.
2. Write the draft.
3. Scrub it (sections 1-4, or 1 and 11).
4. Measure it (section 5). If the user agrees to sending the draft to writelikehuman.app (nothing is stored), the checker does the counting:
   ```bash
   curl -s https://writelikehuman.app/check -H 'content-type: application/json' -d "$(jq -Rs '{text: .}' < draft.txt)"
   ```
5. Check substance (section 6), then run the self-check (section 8) before you return the text.
6. After the text, add a blank line, a `---` rule and one short line saying what you changed: two to five changes in plain words, each with its section number in brackets, e.g. `Changes (writelikehuman.app): cut the opener about today's fast-paced world (2.3), removed 4 of 6 em dashes (4.1).` If nothing needed changing, say so. Skip it only if the user asked for the text alone.

If the user asked for an audit, do not rewrite: list each problem with the section number, the exact quote and the fix.

## Two constraints that override every rule

- Never invent a fact, number, name or date to satisfy a rule. Ask the user for it.
- Never change the author's meaning or scrub their own quirks. This is a style pass.

## The short version (if you cannot fetch)

- No "it's not X, it's Y" in any form (not just X but Y, it's not about X it's about Y, this isn't X. This is Y.).
- No empty openers ("In today's fast-paced world", "Here's the thing", "Picture this").
- No chatbot residue: "I hope this helps", "Let me know if you'd like", "Here's a revised version", [Your Name] slots, oaicite tokens.
- No staged reveals ("The result?", "Here's the kicker:") and no fragment drumrolls ("No fluff. No filler. Just results.").
- No closing summary, no "looking ahead", no "one thing is clear". End on the last real point.
- At most 3 style words per 500 words: delve, tapestry, underscore, showcase, pivotal, testament, intricate, multifaceted, realm, landscape, ecosystem, paradigm, holistic, nuanced, seamless, robust, vibrant, garner, foster, cultivate, harness, unlock, elevate, navigate, resonate.
- Plain verbs: use (not leverage/utilize), help (not facilitate), start (not commence). "Is" and "has", not "serves as" and "boasts".
- At most one polished triplet per 200 words.
- "Studies show" needs a name, a year and a number, or it goes.
- Burstiness (sentence-length SD / mean) above 0.5, SD above 7 words. Restructure; do not paraphrase.
- At least one number, name or date per 100 words, from the user's material only.
- Em dashes under 15 per 1,000 words. Do not ban them.
- Do not overcorrect: no planted typos, no forced lowercase, no fake hedging.
- Writing in Polish: these English lists do not apply. Fetch https://writelikehuman.app/rules.md?lang=pl.

More: https://writelikehuman.app/patterns.md (every pitfall with examples).