Loading...
Loading...
Found 76 Skills
Technical writer specializing in the Diátaxis documentation framework
Set up a complete book writing workspace with AI agents, instructions, prompts, and scripts. Use when users want to create a new book/technical writing project with Markdown + Re:VIEW + PDF output workflow. Triggers on "book writing workspace", "technical book project", "執筆ワークスペース", or similar project setup requests.
Helps maintain documentation pages based on the Diataxis method. Analyzes existing docs, classifies pages into tutorials/how-to/explanation/reference categories, identifies gaps, and helps create or restructure documentation following Diataxis principles. Use when user mentions documentation structure, Diataxis, doc categories, tutorials vs how-to guides, or reorganizing docs.
Generate focused documentation for components, functions, APIs, and features. Use when creating inline docs, API references, user guides, or technical documentation.
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
Write AI-scannable technical documentation.
Documentation and content creation standards for Markdown files. Use when writing, reviewing, or formatting Markdown documentation, README files, or technical content.
Technical documentation writer specializing in creating clear, well-structured markdown documents for algorithms, system design, interview preparation, and code documentation. Use when writing README files, algorithm explanations, system design docs, or technical guides.
Code Documentation Analyzer - Auto-activating skill for Technical Documentation. Triggers on: code documentation analyzer, code documentation analyzer Part of the Technical Documentation skill category.
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. Use when authoring or reviewing content in adev/src/content.
Guides users through structured three-stage collaborative documentation workflow including context gathering, iterative refinement, and reader testing. Use when asked to "write a doc", "draft a proposal", "create a spec", "write technical documentation", "create a PRD", or "draft an RFC". Implements systematic approach for PRDs, design docs, decision docs, technical specs, and proposals through clarifying questions, section-by-section iteration, and fresh-eye validation. Works with markdown documentation, technical specifications, and structured writing projects.