writinglisted
Install: claude install-skill viettdann/arclight-kit
# Writing
Say what the reader needs, in the plainest words that carry it, in the writer's voice. The patterns here mark autopilot writing, by a model or a person; fixing them makes text clearer. They are signals, not proof of who wrote something.
## 1. Mode and register
- **write**: draft new text with these rules applied, then run the check on the draft before delivering it.
- **check**: report findings and change nothing. The default for text that belongs to someone else or is already published.
- **edit**: change a named file in place with minimal edits to the flagged spans. Leave clean paragraphs untouched. For a long file, edit the section the request names; when it names none, ask which section first.
Pick the register from the request or the text; it sets the tolerances in section 4: **docs** (README, guide, reference), **design doc** (plan, spec, handoff), **message** (chat, email, reply, issue comment), **release notes** (changelog, commit body), **long-form** (article, post).
## 2. Content
- Lead with the point. No warm-up context ("In today's fast-moving…"), no restating the question, no recap of what the reader already did.
- Every paragraph adds one fact, claim, or step. If cutting a third of the text loses nothing, it was padding.
- Name things: the number, the version, the file, the exact error, the source. "Studies show", "experts agree", and "industry-leading" get a named source or are cut.
- Docs describe what is. History belongs in the changelog or th