reference-pydantic
Reference Pydantic documentation and source for code improvement
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.
add and manage documentation in code, including constants, variables, functions, classes, and modules
Generate package-info.java files for Java packages. Use when the user requests to add package documentation files to Java packages, create package-info.java files, or document Java package structures. Automatically scans directories for Java packages and creates Javadoc package documentation files where they don't exist.
Review, create, or update docs/manual.md with user documentation for the product
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 based on code changes.
Check if recent changes need documentation updates and suggest which docs to update.
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
Display the project's main CLAUDE.md file containing all development guidelines, rules, and quick references for this VST3 plugin project.
Designs intuitive Python library APIs following principles of simplicity, consistency, and discoverability. Handles API evolution, deprecation, breaking changes, and error handling. Use when designing new library APIs, reviewing existing APIs for improvements, or managing API versioning and deprecations.