Drafting, editing, tone and plain-language rewrites. 7 reviewed prompts for writing.
Turns a clinician's rough encounter notes into a structured SOAP note and flags missing information. Use it to speed up documentation; the clinician reviews and signs off every note.
Checks Markdown documents for accessibility problems such as missing alt text, heading jumps and vague link text, then lists fixes or returns a corrected version. Use before publishing docs, a readme or blog post.
Expands a bare list of steps for a software feature into a clear, friendly how-to article with screenshot placeholders and troubleshooting tips. Use it for help-center pages and customer guides.
Reviews documentation for errors, unclear wording, broken references and inconsistent terms, with a reason for each fix. Use it before publishing guides, READMEs or help pages.
Creates a documentation strategy for a software product or API: audiences, information architecture, priority gaps, workflow, style rules, and success metrics. Use when launching docs, overhauling messy docs, or scaling a docs team.
Turns feature notes or technical descriptions into a step-by-step guide that a non-technical user can follow. Use it when documenting a module, screen or workflow for customers or staff.
Writes or revises developer-facing docs (READMEs, API references, release notes, changelogs, technical posts) with the right structure for each type, runnable examples and no filler. Use it when shipping or documenting a feature.
