write-blog

# Write a Parler Protocol blog post You are helping a contributor write a blog post for the Parler Protocol website. The bar: it reads like a person wrote it, it ranks for a search cluster no other post already owns, and it ships wired correctly into the Next.js site with the build green. This skill exists so every contributor writes in the same voice, picks non-overlapping topics, and passes the same anti-AI-slop gate, whether or not they already know the house rules. ## The one rule that gets a post rejected **No em dashes (—) or en dashes (–). Ever.** This repo is hand-styled and the house voice bans them. Use a period, a comma, or "so"/"because"/parentheses instead. A single dash in a draft is a hard fail. There is a scanner: run `bash check.sh <file>` (in this skill's folder) on any draft before you call it done. ## Workflow Do these in order. Don't skip the angle check or the humanizer pass. ### 1. Read the ground truth first Before writing a word, read what already exists so you match voice and don't cannibalize keywords: - `web/lib/blog.ts`, the `POSTS` array. This is the **live registry of every published post and the angle it owns.** Read every `slug`, `title`, `dek`, and `tags`. - One or two full posts in `docs/blog/*.md` (the prose sources) to absorb the voice. - `reference/angles.md` (in this skill folder) for how to pick an angle that doesn't collide, plus the topics still untapped. - `reference/voice.md` for the house voice and the anti-AI checklis...