Writing principles for manifest-dev: how its maintainer wants the text people read — READMEs, guides, decision records, the site and pull request descriptions — written, and why. Use before planning, writing or reviewing such text in this project.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Writing Principles?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/doodledood-writing-principles)
---
name: writing-principles
description: 'Writing principles for manifest-dev: how its maintainer wants the text people read — READMEs, guides, decision records, the site and pull request descriptions — written, and why. Use before planning, writing or reviewing such text in this project.'
---
Edit rule: each line is a principle with its reason and when it yields. Decisions go to the
decision records, rules a check can hold go to the check, and a line is added only on a person's
yes, after sharpening an existing line is ruled out.
- A document, comment or description changes in the same change as the thing it describes — a stale description is believed, and it misleads whoever believes it. Yields for a decision record, which keeps what was decided at the time and is superseded rather than edited.
- One thing goes by one term throughout the text the project shows and writes — a second word for the same thing reads as a second thing. Yields when quoting another source's term, marked as theirs.
- Text uses words its intended reader already knows — a word the reader must look up stops them at that word. Yields for a term the project coins, which is defined once where a reader first meets it.
- A how-to lets a reader new to the task complete it from the page alone, shown by such a reader having done so — the writer cannot see the step they kept in their head. Yields where the page links to the single home of a fact rather than copying it.
Before calling writing work done, check it against these principles from a fresh start — a new
session, or a reviewer who did not do the work. Fix what departs unless the person chose the
departure, and check again only after a fix, until a check finds none. Name each departure kept,
with the principle and why.