claudeskills.page

Collection · 10 skills

Docs That Get Read

Skills that make Claude write like a good staff engineer: READMEs that get someone running in five minutes, API references with working examples, design docs that surface the real tradeoffs, runbooks for 3 a.m., and an editing pass that cuts a third of the words.

Best for Maintainers, tech leads and anyone who owns documentation.

What's inside

Listed in the order we suggest adopting them. You don't call them by name: each skill loads on its own when a request matches it.

  1. Technical Writing Docs that get one reader to one goal Technical Writing technical-writing 172 lines
  2. README Writer From landing on the repo to a working result Technical Writing readme-writer 180 lines
  3. API Documentation First successful call in under five minutes Technical Writing api-documentation 246 lines
  4. Design Docs and RFCs Proposals that end in a recorded decision Technical Writing design-docs-rfc 167 lines
  5. ADR Records Decisions your team can still explain next year Architecture adr-records 157 lines
  6. Changelog and Release Notes Tell users what changed for them, not what you typed Technical Writing changelog-release-notes 198 lines
  7. Runbooks From page to mitigation without asking anyone Technical Writing runbooks 184 lines
  8. UX Microcopy Labels that say exactly what will happen Technical Writing ux-microcopy 197 lines
  9. Prose Editing Cut a third, keep the meaning and the voice Technical Writing prose-editing 174 lines
  10. Docs Site Docs people can navigate, search and trust Technical Writing docs-site 174 lines

Keep exploring

Other collections

All collections →
esc