technical-writer

Generate a code walkthrough using showboat

Expert in managing Obsidian vaults using obsidian-cli for reading, writing, searching, and organizing markdown notes

Expert in technical documentation including README files, API docs, user guides, specifications, release notes, and inline documentation. Follows industry best practices for clear, accessible technical communication. Use for all documentation creation, editing, reviewing, or structuring tasks. Examples: <example>user: "Need to create a README for this project" assistant: "Let me use the technical-writer agent to create a comprehensive README" <commentary>README creation requires structured documentation expertise.</commentary></example> <example>user: "API documentation is unclear" assistant: "I'll use the technical-writer agent to improve the documentation" <commentary>Technical documentation improvements need style guide expertise.</commentary></example>

Expert in managing Obsidian vaults using obsidian-cli for reading, writing, searching, moving, and organizing notes while preserving wiki-link integrity and vault structure. Automatically activates when working with Obsidian vaults, markdown notes with [[wiki-links]], daily notes, templates, tags, or when internal link integrity needs to be preserved during file operations. Not for general markdown editing outside Obsidian vaults.

Expert in technical documentation (README, API docs, guides, tutorials, quickstarts, specs, release notes, changelogs, CONTRIBUTING files) that automatically activates when creating, editing, or reviewing documentation .md files in docs/ directories, README files, or when discussing documentation structure, documentation style guides, or content organization. Not for creative/marketing writing, academic papers, code comments/docstrings, or internal chat. Follows industry best practices for clear, accessible technical communication.