112 skills · sorted by relevance
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
The English summary is being prepared. Showing the original description.
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
The English summary is being prepared. Showing the original description.
Design APIs for AI services. TRIGGERS - Use when user needs help with ai-api-design related tasks.
The English summary is being prepared. Showing the original description.
Design APIs for AI services. TRIGGERS - Use when user needs help with ai-api-design related tasks.
The English summary is being prepared. Showing the original description.
Skill for api-design-checklist tasks.
The English summary is being prepared. Showing the original description.
Design and review REST APIs, interfaces that exchange resources over HTTP, with consistent URLs, responses, and error handling. Covers pagination, authentication, request limits, and versioning to clarify how clients interact with an API.
Apply shared coding conventions to new modules, reviews, and refactoring. Guides descriptive naming, readable structure, updates that preserve existing data, and error handling, giving teams a consistent basis for checking code quality.
Design and review REST APIs with consistent URLs, HTTP status codes, error responses, and pagination, which divides results into smaller batches. Covers authentication, access limits, and versioning to help define clear behavior for API users.
Review and refine code using shared conventions for clear names, readability, error handling, and updates that preserve original data. Identify duplication, oversized functions, and unnecessary complexity to make code easier to understand and maintain.
Design and review REST APIs with consistent resource names, HTTP status codes, error responses, and pagination, which splits lists into smaller results. It also guides filtering, authentication, request limits, and versioning for public or internal APIs.
Design REST or GraphQL APIs by defining who will use them, what data they expose, and how requests behave. Establish error formats, versioning, pagination, and authentication, then review examples for consistency before implementation.
Turn a system description into REST API endpoints, the URLs and operations applications use to exchange data. Choose an endpoint list or detailed specifications covering authentication, request fields, responses, error codes, and pagination for lists.
Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.
Design REST and GraphQL APIs by clarifying who will use them and how. Define data structures, errors, authentication, pagination, and versioning, then review examples to make the interface consistent and easier to use.
Review REST API specifications with automated checks for inconsistent conventions and breaking changes—changes that disrupt existing clients. Get a design grade, improvement recommendations, and tool reports to support release reviews and API migrations.
Design REST or GraphQL APIs by defining data relationships, requests, responses, and authentication. Produce OpenAPI specifications, machine-readable API descriptions, with consistent errors, pagination, and versioning plans, then validate contracts using a mock server.
REST API design with resource naming, pagination, versioning, and OpenAPI spec generation
The English summary is being prepared. Showing the original description.
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
The English summary is being prepared. Showing the original description.
REST API设计模式，包括资源命名、状态码、分页、过滤、错误响应、版本控制和生产API的速率限制。
The English summary is being prepared. Showing the original description.
生产级 API 的 REST API 设计模式，包括资源命名、状态码、分页、过滤、错误响应、版本控制和速率限制。
The English summary is being prepared. Showing the original description.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
The English summary is being prepared. Showing the original description.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
The English summary is being prepared. Showing the original description.
Guidelines for introducing and using nullable reference types (NRT) and System.Diagnostics.CodeAnalysis nullable attributes in C# / .NET codebases. Covers the nullability model, flow analysis, the null-forgiving operator, API design rules, the full attribute catalog (AllowNull, DisallowNull, MaybeNull, NotNull, NotNullWhen, MaybeNullWhen, NotNullIfNotNull, MemberNotNull, MemberNotNullWhen, DoesNotReturn, DoesNotReturnIf), the C# 14 field keyword, incremental migration of legacy codebases, and a code-generation checklist.
The English summary is being prepared. Showing the original description.
Design stable, compatible public APIs using extend-only design principles. Manage API compatibility, wire compatibility, and versioning for NuGet packages and distributed systems.
The English summary is being prepared. Showing the original description.