docs-creatorlisted

Create or improve documentation files with Diataxis-aware placement and consistent naming. Use when the user wants to create any new documentation, improve existing docs, write a README, or restructure documentation. Also use when asked to "write docs", "improve this doc", "add a tutorial", "update the readme", or any request involving markdown documentation authoring, even if they don't explicitly say "create documentation".
y-miyazaki/config · ★ 1 · Data & Documents · score 68

Install: claude install-skill y-miyazaki/config

**UTILITY SKILL** — creates and improves documentation content. ## Input - Natural language request describing what to document (required) - `target_file`: explicit path if updating an existing file (optional) ## Output Specification Return structured report per [references/common-output-format.md](references/common-output-format.md). ## Execution Scope ### USE FOR: - Create new documentation files (README, specs, architecture, tutorials, how-to guides) - Improve or rewrite existing documentation content - Apply consistent structure to unstructured docs ### DO NOT USE FOR: - Syncing docs after code changes (use docs-updater skill) - Source code comments or docstrings - Markdown linting (use markdown-validation skill) - Auto-generated references (godoc, terraform-docs output) ## Reference Files Guide - [category-diataxis-mapping.md](references/category-diataxis-mapping.md) (always read) - [common-checklist.md](references/common-checklist.md) (always read) - [common-output-format.md](references/common-output-format.md) (always read) ## Workflow 1. **Determine intent**: new document or improvement to existing one? 2. **Resolve placement** per [category-diataxis-mapping.md](references/category-diataxis-mapping.md). README → repository root. 3. **Resolve filename**: kebab-case, lowercase, `.md`. No version numbers. If `target_file` provided and exists, use as-is. 4. **Gather context**: read relevant source files to populate with project-specific content. The docume