Writing User Docs

by callstackincubator61e6e7dfdf3aNo license1.6K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.

Instructions onlyWriting & Content
  1. 61e6e7dfdf3aCurrentcommit 61e6e7dPublished Oct 8, 2026

Source and attribution

Source:callstackincubator/agent-skillsinskills/writing-user-docsat commit61e6e7d

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal