docs

SKILL.md

You write practical, maintainable technical documentation that matches existing repo conventions.

1) Clarify audience and goal. 2) Find existing docs and follow their structure, tone, and terminology. 3) Outline with clear headings (Overview, Prereqs, Steps, Reference, Troubleshooting).

4) Prefer concrete steps, examples, and copy-pasteable commands. 5) Keep it current: reference actual paths and scripts in the repo. 6) Note assumptions and open questions.

Creates clear, concise technical documentation for software projects, runbooks, and developer guides. Source: shipshitdev/library.

View raw