api-design-standards

Guide API design and implementation in Azure API Management with OpenAPI 3.0.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/SandboxServers/github-copilot-agents --skill api-design-standards-sandboxservers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-design-standards
Source: https://github.com/SandboxServers/github-copilot-agents/tree/main/skills/api-design-standards.skill
Command: npx skills add https://github.com/SandboxServers/github-copilot-agents --skill api-design-standards-sandboxservers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openapi, azure-apim, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps organizations establish and enforce API design standards, ensuring consistency and quality in API development and management within Azure API Management.

Core Features & Use Cases

  • API Design Guidelines: Provides comprehensive guidelines for API design, including contract-first development, resource naming, versioning, and error handling.
  • Implementation Assistance: Offers operational instructions for implementing API design standards, including the use of OpenAPI 3.0 specifications and Azure API Management.
  • Use Case: Ideal for new API design projects, API contract reviews, or when setting up API standards for a team.

Quick Start

Implement API design standards using the 'api-design-standards' skill by following the guidelines and instructions provided in the SKILL.md file.

Frequently Asked Questions about api-design-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce API design standards in Azure API Management?

You can enforce API design standards in Azure API Management by applying guidelines for contract-first development, resource naming, versioning, and error handling. This ensures consistency and quality across API development and management.

What are the best practices for API versioning and error handling in OpenAPI 3.0?

Best practices for API versioning and error handling involve adopting a contract-first approach using OpenAPI 3.0 specifications. This defines strict resource naming conventions and standardized error responses before implementation.

Do I need OpenAPI 3.0 specifications to use this API governance skill?

Yes, OpenAPI 3.0 specifications are required for execution. The skill uses these specifications to guide contract-first development and implement operational design standards within Azure API Management.

Can I use this skill for API contract reviews and setting up team standards?

Yes, this skill is ideal for new API design projects, API contract reviews, and setting up API standards for a team. It provides comprehensive guidelines and operational instructions for implementation.

How does contract-first development improve API consistency in Azure APIM?

Contract-first development improves API consistency by defining the OpenAPI 3.0 specification before implementation. This enforces standardized resource naming, versioning, and error handling across all APIs in Azure APIM.

What are the limitations of managing API design guidelines without OpenAPI specifications?

Without OpenAPI 3.0 specifications, executing this skill for API governance in Azure API Management is not possible. It requires both dependencies to provide implementation assistance and enforce design standards.