technical-documentation
Write clear technical documentation, API references, user guides, tutorials, and architecture docs. Use when creating or updating documentation.
Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Write clear technical documentation, API references, user guides, tutorials, and architecture docs. Use when creating or updating documentation.
Write clear technical documentation, API references, user guides, tutorials, and architecture docs. Use when creating or updating documentation.
Create, update, and improve clear, accurate, and actionable documentation for developers and users.
Master REST API design principles to build intuitive, scalable, and maintainable APIs. Applicable for designing new APIs, reviewing API specifications, or establishing API design standards in Java Spring projec...
Create detailed implementation strategies and architecture documentation
Create detailed implementation strategies and architecture documentation
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, e...
Guidelines for writing effective Clojure docstrings with markdown formatting, wikilinks, code examples, and tables. Always use this skill when writing or reviewing docstrings in Clojure code, or when asked abou...
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and ve...
This skill should be used for all external AI collaboration - consulting, implementing, or reviewing with codex/copilot. Triggers include "pair with codex", "get a second opinion", "delegate this", "consult on"...
This skill should be used when the user asks to "audit AGENTS.md", "check agent docs", "verify documentation accuracy", "maintain agent instructions", "check for drift", or mentions documentation needs updating...
Technical documentation best practices and API documentation
Retrofit existing projects to DevDocs workflow, or migrate old DevDocs to new standards. Use when users want to adapt existing projects, migrate documentation, standardize documents, or upgrade DevDocs version....
Add new features to existing DevDocs projects. Use when users need to add new features, iterate on existing functionality, or mention keywords like "add feature", "new feature", "新功能", "迭代", "新增功能".
When fetching library documentation, API references, or technical docs for project dependencies via WebFetch, automatically save a copy to the docs/ folder. Also triggers when user pastes documentation or discu...
Create comprehensive technical documentation for code systems including data flow diagrams, architecture overviews, algorithm documentation, cheat sheets, and multi-file documentation sets. Use when documenting...
Fetch the latest, docs-grounded API details and best practices for a library/framework using Context7 MCP tools `resolve-library-id` and `get-library-docs`. Use when a user asks for “最新用法/最新寫法/最佳實務/...
Generate and maintain comprehensive documentation including Doxygen comments, progress reports, session notes, and API docs for Orpheus SDK.
Creates structured feature requirement documents for software features. Use when defining new features, writing requirements, specifying CLI commands, API endpoints, or when the user asks for feature documentat...
Creates lightweight documentation for chore tasks and maintenance work. Use when the user needs to document a chore, maintenance task, dependency update, refactoring, or minor fix that doesn't require full feat...
This skill is an expert in DokuWiki syntax, usage, and best practices.
This skill should be used when the user asks to "review documentation", "improve docs quality", "check markdown formatting", "fix documentation structure", "write better docs", "documentation best practices", o...
This skill should be used when the user asks to "document an API", "create API docs", "generate OpenAPI spec", "review API documentation", "document REST endpoints", "create Swagger docs", "document AsyncAPI",...
Use when starting a new project or setting up documentation structure - bootstraps docs/ folder with lifecycle documents and planning hierarchy
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.