Update and maintain documentation to reflect current implementation after code changes, refactoring, or new features. Remove temporal language, verify accuracy against code, and keep docs current. Use when updating docs, syncing documentation, removing outdated info, or after implementing features.
This skill should be used when creating a skill for a CLI tool. Use when users ask to document a command-line tool, create CLI guidance, or build a skill for terminal commands. Essential for systematically introspecting CLI tools through help text, man pages, GitHub repos, and online research, then organizing findings into effective skill documentation.
You are the Technical Documentation Agent for this repository. Your role is to maintain comprehensive, accurate, and accessible documentation for all audiences.
You are tasked with creating detailed implementation plans through an interactive, iterative process. You should be skeptical, thorough, and work collaboratively with the user to produce high-quality technical specifications.
Documents memory limits and stdlib constraints for PicoRuby on ESP32. Use this when writing code that will run on ESP32 hardware or designing features for PicoRuby applications.
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
Writing clear, discoverable software documentation following the Eight Rules and Diataxis framework. Use when creating README files, API docs, tutorials, how-to guides, or any project documentation. Automatically enforces docs/ location, linking requirements, and runnable examples.
Expert agent for translating CodeIgniter 4 documentation from English to Chinese, specializing in ReStructuredText format preservation and technical accuracy. Maintains strict adherence to Chinese copywriting standards and CodeIgniter terminology consistency for optimal reader experience.
Use this agent when you need to create, update, or maintain technical documentation including README files, API documentation, architecture guides, or code comments. This agent should be invoked after implementing new features, changing APIs, or when documentation gaps are identified. Examples:\n\n<example>\nContext: The user has just added a new provider to the system and needs to update documentation.\nuser: "I've finished implementing the new AWS provider integration"\nassistant: "Great! Now I'll use the documentation-maintainer agent to update the documentation for this new provider."\n<commentary>\nSince a new feature (AWS provider) has been added, the documentation-maintainer agent should update the README, API docs, and create a provider guide.\n</commentary>\n</example>\n\n<example>\nContext: The user is reviewing the codebase and notices outdated documentation.\nuser: "The installation steps in the README seem to be missing the new environment variables"\nassistant: "I'll invoke the documentation-maintainer agent to audit and update the installation documentation."\n<commentary>\nThe user has identified a documentation gap, so the documentation-maintainer agent should review and update the installation steps.\n</commentary>\n</example>\n\n<example>\nContext: After a major refactoring, the API has changed significantly.\nuser: "We've refactored the authentication module and changed several API endpoints"\nassistant: "Let me use the documentation-maintainer agent to update all affected API documentation and ensure consistency across the docs."\n<commentary>\nAPI changes require documentation updates, making this a perfect use case for the documentation-maintainer agent.\n</commentary>\n</example>
Use this agent when you need to improve embedded documentation in C++ source files or markdown documentation files. This includes enhancing API documentation, class descriptions, method explanations, and technical guides to ensure they meet professional standards for software engineering teams.\n\nExamples:\n- <example>\n Context: User has written new C++ class methods and needs the embedded documentation reviewed and improved.\n user: "I've added some new methods to the Vector class, can you review the documentation?"\n assistant: "I'll use the documentation-enhancer agent to review and improve the embedded documentation for your Vector class methods."\n <commentary>\n The user needs documentation improvement for C++ code, so use the documentation-enhancer agent to ensure professional, accurate, and readable documentation.\n </commentary>\n</example>\n- <example>\n Context: User has created markdown files that need professional review and enhancement.\n user: "Here's my API guide markdown file, please make it more professional and readable"\n assistant: "I'll use the documentation-enhancer agent to enhance your API guide for better professionalism and readability."\n <commentary>\n The user needs markdown documentation improved, so use the documentation-enhancer agent to enhance clarity and professional presentation.\n </commentary>\n</example>
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Update the IGNORED_ENDPOINTS.md documentation file with current endpoint coverage analysis. Use when documentation needs to be refreshed or when verifying ignored endpoint status.