Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.
Generates OpenAPI/Swagger/GraphQL documentation and SDKs from code
Write clear technical documentation. Use when creating READMEs, API docs, or user guides. Covers documentation types and best practices.
Write documentation. Use when generating API docs, README files, or updating docstrings. Includes Context7 documentation standards lookup.
Generate gRPC service definitions, stubs, and implementations from Protocol Buffers. Use when creating high-performance gRPC services. Trigger with phrases like "generate gRPC service", "create gRPC API", or "build gRPC server".
写 API contract、接口契约、OpenAPI/AsyncAPI/GraphQL/gRPC、WebSocket/SSE、Webhook、SDK/库接口、文件格式规范。用于在 PRD 之后、HLD 之前产出可审查的接口契约/协议文档，作为跨团队协作的单一事实源。
撰写高质量的高层技术设计文档（HLD），基于 PRD 和 API Contract 做出技术架构决策。适用于 PRD 和 API Contract 完成后需要进行系统架构设计、技术选型、或制定技术方案的场景。
Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
Create and maintain TYPO3 extension documentation following official docs.typo3.org standards. Use when creating/editing Documentation/*.rst files or README.md, using TYPO3 directives (confval, versionadded, card-grid, accordion, tabs, admonitions), creating/adding screenshots, rendering/testing/viewing docs locally, or deploying to docs.typo3.org. By Netresearch.
Generates and maintains codebase context documentation (.context.md files). Implements the Codebase Context Specification for AI-friendly project documentation. Activates when documenting architecture or onboarding.
Instructions for updating the project documentation. Use this when the user asks to update docs, add examples, or fix typos in the documentation.
Reverse engineers and generates comprehensive technical specifications from pseudocode, algorithms, or code snippets. Produces detailed requirements documents, functional specifications, API documentation, data models, and workflow diagrams. Use when analyzing pseudocode, extracting requirements from algorithms, documenting undocumented code, reverse engineering specifications, creating specifications from implementation details, or when users mention "pseudocode to spec", "reverse engineer specification", "generate spec from code", "document algorithm", "extract requirements from pseudocode", "code to specification", or "specification from implementation".
Provides development guidance for implementing backend features using Domain-Driven Design, hexagonal architecture, event-driven patterns, and HATEOAS conventions. Use when implementing new domain features, REST APIs, or integrating cross-domain functionality in the backend.
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context. Assumes skilled developers who need domain-specific guidance, following DRY, YAGNI, and TDD principles. Use after brainstorming/design is complete when handing off to another developer or planning complex multi-step work. Do NOT use for simple tasks, quick fixes, or when you're implementing yourself and already understand the codebase - just start coding instead.
Creates high-quality technical documentation including API documentation, user guides, tutorials, architecture documents, README files, release notes, and technical specifications. Produces clear, structured, and comprehensive documentation following industry best practices. Use when writing technical documentation, creating API docs, developing user guides, documenting architecture, writing tutorials, preparing release notes, or when users mention "technical writing", "documentation", "API docs", "user guide", "tutorial", "README", "technical specification", "architecture document", or "developer documentation".
Technical documentation best practices for clear, accurate, and useful documentation. Use when writing documentation, README files, API docs, architecture guides, or any technical communication.
Provides expert guidance for writing compact, effective technical documentation. Use this skill when: (1) user mentions "documentation", "docs", "document", "readme", "architecture", or "API docs", (2) user requests to write, create, update, improve, or review any documentation, (3) user is documenting code, systems, features, or APIs, (4) user is creating README.md, ARCHITECTURE.md, CONTRIBUTING.md, or tutorial files, (5) user requests examples or how-to guides.
Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".
Write scripts for educational and explainer videos that teach effectively
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
Expert frontend development guidance covering React, Vue, Angular, TypeScript, state management, component architecture, performance optimization, accessibility, testing, and modern web APIs. Produces production-ready, maintainable, and performant frontend code with best practices. Use when building web applications, implementing UI components, managing application state, optimizing performance, or when users mention React, Vue, Angular, TypeScript, hooks, state management, components, or frontend development.
