What problem does it solve? Writing consistent, accurate technical documentation is hard: READMEs, API docs, tutorials, and release notes each follow different conventions, and teams often produce unclear, poorly structured content. This Skill applies industry-standard content models and style rules so documentation is clear, accessible, and task-focused. ## Core Features & Use Cases - Structured Content Types: Guides creation of conceptual, referential, procedural, troubleshooting, quickstart, tutorial, and release notes content, each with its own rules for titles, intros, and structure. - Style Guide Enforcement: Applies rules for sentence case headings, active voice, code formatting, descriptive links, alert usage, and accessibility (alt text, heading hierarchy). - Markdown Validation: Includes a script that checks markdown files for skipped heading levels, missing code block language tags, unclosed code fences, and non-descriptive link text. - Use Case: Ask it to draft a README for a new project, write API reference docs with parameter tables, or review an existing docs/ directory for clarity and structural issues. ## Quick Start Ask the assistant to write a README for your project or review the markdown files in your docs folder for style and structure issues.
