documentation
Documentation standards and writing guidelines
Discover blockchain technical docs skills, compare source repositories and read the instructions for each workflow.
Documentation standards and writing guidelines
Generate concise specifications for development tools, editors, and utilities. Use this when planning a new tool, editor plugin, or standalone utility to assist with game development.
JSDoc documentation standards for JavaScript following jsdoc.app conventions. WHEN: Writing JSDoc comments, documenting JavaScript functions/classes/modules, generating API docs with JSDoc, improving existing J...
Write Python docstrings following PEP 257 and popular formats (Google, NumPy, Sphinx). WHEN: Writing docstrings for Python functions/classes/modules, choosing docstring format, documenting parameters/returns/ex...
Write PHP DocBlocks following PSR-5 and PSR-19 PHPDoc standards. WHEN: Writing DocBlocks for PHP classes/methods/functions/properties, documenting @param/@return/@throws, type annotations in PHPDoc. WHEN NOT: P...
TSDoc documentation standards for TypeScript following tsdoc.org conventions. WHEN: Writing TSDoc comments, documenting TypeScript functions/classes/interfaces/types, generating docs with TypeDoc, improving exi...
Modern documentation management with MkDocs Material theme and GitHub Pages publishing. Use when users need to create, maintain, or publish professional documentation websites. Supports initialization of new do...
Guide systematic feature development with codebase exploration, architecture design, and implementation. Use this skill when the user wants to implement a new feature, add functionality, or build something new...
Documentation standards. Apply when completing full feature development, introducing new architecture patterns, or adding new public APIs.
Add new pages to docs.json navigation structure. Updates navigation groups based on user journey (Guides, API Reference, Recipes, etc.). Use when the user asks to add a page to navigation, update docs.json, add...
Expert in documentation structure, audience targeting, and information architecture. Covers technical docs for Software, Hardware, Robotics, and Data Science.
Autonomously analyzes a repository, detects architectural and coding patterns, and generates/updates a docs/ folder with a root CLAUDE.md as table of contents. Use when asked to generate documentation, create C...
Review and improve repository documentation including both human-readable docs (`docs/`), `README.md`, and AI agent memory context files (`CLAUDE.md`, `CODEX.md`, `AGENTS.md`, `.cursorrules`, etc.) for clarity,...
This skill should be used when the user asks to "create a README", "write a README", "generate a README", "improve my README", "make my README better", "README best practices", or mentions needing project docum...
Docs Guide Agent. 튜토리얼, 사용 가이드 작성을 담당합니다.
Docs API Agent. OpenAPI 스펙, API 레퍼런스 문서 작성을 담당합니다.
Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.
Guides implementation phase. Use when writing code, implementing features, or building functionality. Ensures code quality, testing, and documentation.
Intelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步, documentation, doc, 文件, 說明文件, 更新文檔, sync readme, 同步說明, 專案說明.
This skill should be used when the user asks about "UCP architecture", "protocol structure", "OpenAPI spec", "OpenRPC spec", "capability design", "method naming", or needs to understand how UCP works. Provides...
Provides guidance on HTML/CSS best practices for responsive web design, Bootstrap integration, accessibility, and performance optimization. Use when building web pages, styling components, or improving web desi...
Keep the structure of documentation clear and explicit.
Expert UI/UX design and frontend development guidance. Use when designing interfaces, creating design systems, improving user experience, implementing accessible components, or building responsive layouts. Cove...
Use when "codex", "use gpt", "gpt-5", "openai codex", "let openai", "full-auto", "autonomous code generation"
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.