Write persistent project documentation using Diátaxis modes and state-oriented language.
npx skills add https://github.com/SgtPooki/skills --skill writing-docs-sgtpooki
Please help me install this Agent Skill. Skill: writing-docs Source: https://github.com/SgtPooki/skills/tree/main/skills/writing-docs Command: npx skills add https://github.com/SgtPooki/skills --skill writing-docs-sgtpooki
High-intent search queries and answers about installing and using this skill.
Assign each page exactly one of four modes: tutorial (guided lesson), how-to (task steps), reference (dry facts), or explanation (context and reasoning). Never mix modes on one page, since mixing is the root cause of most bad docs.
A tutorial serves a learner who needs a guaranteed win, so you own the path and outcome. A how-to serves a competent user with a goal, giving numbered steps for one real task without teaching theory.
No. Documentation describes the system as it is now, using state-oriented language like "X provides Y". Change history belongs in PR descriptions, changelogs, or a clearly scoped migration section.
Do not use it for PR descriptions or issues (use github-writing), decision records like ADRs or RFCs (use writing-spec, even under docs/), or release notes and announcements (use writing-community).
Run the writingcheck.py script from writing-core with the writing-docs argument on your page. Fix reported errors within three passes and treat advisory notes like Google.Passive and Google.Headings as judgment calls.
tyevansVerify claims against source code, documentation, and external resources.
Kevin-Liu-01Synchronize source-level docs and docs-site pages with code changes.
emdash-cmsWrite and review EmDash documentation for accuracy, structure, and natural prose.
wesleyosantos91Generate structured Architecture Decision Records with consistent sections.
