TSDoc documentation standards for TypeScript following tsdoc.org conventions. WHEN: Writing TSDoc comments, documenting TypeScript functions/classes/interfaces/types, generating docs with TypeDoc, improving existing TS documentation. WHEN NOT: JavaScript code (use js-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs
Auto-activating documentation cache with fresh API docs. Fetches and automatically consults cached documentation when user works with libraries/frameworks.
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
Generate comprehensive documentation including API docs, comments, and README
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 verification steps assuming engineer has minimal domain knowledge
Scaffold new RSPress documentation pages with proper structure and templates. Use when creating new docs pages, adding package documentation, writing guides, or setting up API reference pages.
Write self-documenting code with minimal, helpful comments that explain large sections of logic without cluttering the codebase. Use this skill when writing code comments, documenting complex logic, reviewing whether comments are needed, writing function documentation, explaining non-obvious code sections, ensuring code clarity through naming and structure, avoiding temporary or change-related comments, keeping comments evergreen and future-relevant, or deciding between adding comments versus refactoring for clarity. Apply this skill when writing or reviewing any code file to ensure comments add value without creating noise, and that code is primarily self-explanatory through clear naming and structure.
Generate comprehensive handoff documentation optimized for AI agent takeover by analyzing project structure, design docs, and codebase
Reference Pydantic documentation and source for code improvement
从 L2 需求和接口定义生成架构设计文档。 当用户说"生成架构"、"技术设计"、"数据库设计"时自动触发。 输出 docs/architecture/ 目录下的设计文档。
Generates comprehensive API documentation for REST endpoints, GraphQL schemas, or RPC methods when user requests API documentation or endpoint documentation
Generate TypeScript type declarations from OpenAPI/Swagger specification. Use phrases like "Generate TS models", "Create TypeScript interfaces from swagger", "Generate API types", etc.
Generate markdown explanation for a LeetCode solution (project)
Use when generating architecture documents - creates SYSTEM_OVERVIEW, API_DESIGN, DATA_MODEL, SECURITY, and ADRs
MkDocs documentation standards with mkdocs-material theme. Use when creating documentation, README files, or project docs structure.
Complete SPEC document authoring guide with YAML metadata structure (7 required + 9 optional fields), EARS requirement syntax (5 patterns including Unwanted Behaviors), version lifecycle management, TAG integration, pre-submission validation checklist, and real-world SPEC examples.
Defines the required structure and conventions for IC module specification documentation, including versioning, interface tables, and verification methodology.
Generate comprehensive documentation for .NET/C# codebases including architecture diagrams, API references, domain models, and getting started guides. Use when asked to: generate docs, document this, create documentation, write docs for, document a .NET project, create architecture documentation, document APIs.
Query Rust docs and crate APIs from CLI. Use when exploring Rust crates, building API context and codemaps for handoffs, searching rustdoc, or needing crate skeletons. Trigger on "ripdoc", "rust docs", "crate API", "skelebuild", "create codemap", or when investigating Rust library usage.
