draftlisted

# Draft Produce **three hook options with reasoning, then a draft per platform**. Never hand back a single finished post: choosing beats editing, and it is what every serious posting skill does. ## Read first - `product-context/PRODUCT.md` in the estate (`~/.claude/content/product-context/PRODUCT.md` by default), before anything else. It says what this product is, who it is for, the words it keeps, the words it refuses and what it will never say. The refused words and the never-say list are absolute; a field marked `UNKNOWN` is a gap to ask about, not one to fill. **If the file is not there, stop. Do not draft.** Say so in one line and ask for the suite's `product-context` skill to be run first. Without it a draft invents the company it is describing, plausibly enough that nobody catches it for months, and every draft after inherits the invention. - `STYLE.md` always. It is the sniff test: would a reader assume a machine wrote this. Nothing else matters if that fails. - Your own voice. If the suite's `voice` skill has written a profile (in `voice/` under the same estate, default `~/.claude/content/voice`), read `VOICE.md` first: that is the style written as instructions a writer can follow. Then `profile.json` for the raw counts behind it, which are evidence rather than guidance. Read real samples too if you keep any, from `voice/samples/` where `voice` keeps them: a real sample that actually landed beats a description of your voice every ti