User Guide Writing

When you need to ship a getting-started guide, tutorial, how-to article, or FAQ for actual product users, this skill keeps you honest about scope and structure. It forces you to pick one primary mode upfront (getting-started, tutorial, how-to, FAQ, or release-help-update), gather real UI evidence instead of guessing, and emit the smallest artifact that solves the problem. The routing boundaries are tight: API docs go to api-documentation, internal specs go to technical-writing, and release notes go to changelog-maintenance. The Step 6 writing rules are opinionated in a good way: lead with the task, name prerequisites early, prefer observable actions, and put troubleshooting near the task instead of burying it. If you write user docs that drift into architecture explanations or try to be five document types at once, this will pull you back.

Install to Claude Code

npx -y skills add akillness/oh-my-skills --skill user-guide-writing --agent claude-code