api-designer

Designs standardized REST, GraphQL, gRPC and AsyncAPI blueprints with OpenAPI/AsyncAPI specs output.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ouakar/ubinarys-dental --skill api-designer-ouakar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-designer
Source: https://github.com/ouakar/ubinarys-dental/tree/main/skills/forgewright/skills/api-designer
Command: npx skills add https://github.com/ouakar/ubinarys-dental --skill api-designer-ouakar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The API designer helps teams standardize API design processes for REST, GraphQL, gRPC, and AsyncAPI patterns, ensuring pagination, versioning, error handling, rate limiting, and governance, all orchestrated by a production-grade workflow.

Core Features & Use Cases

  • Design standard API specs (OpenAPI/AsyncAPI) aligned to organizational governance.
  • Establish resource modeling, naming conventions, and pagination/versioning strategies for multi-protocol APIs.
  • Use case: when delivering an API program, produce a governance-ready design pack and implementation blueprint.

Quick Start

Provide a complete API design plan for a new service, including domain modeling, resource design, OpenAPI specs, and governance guidelines.

Frequently Asked Questions about api-designer

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

FAQPage Schema
How do I design production-grade APIs that include governance and OpenAPI specs?

Designing production-grade APIs with governance involves standardizing resource modeling, versioning, pagination, and error handling across REST, GraphQL, gRPC, and AsyncAPI patterns to output OpenAPI specs and governance documentation.

What is the best way to standardize API versioning and pagination across multiple protocols?

Standardizing API versioning and pagination across multiple protocols requires establishing consistent naming conventions and resource modeling strategies, guided by a production-grade orchestrator to ensure multi-protocol API governance.

How do I generate a governance-ready API design pack for an enterprise API program?

Generating a governance-ready API design pack involves creating a complete API design plan that includes domain modeling, resource design, OpenAPI or AsyncAPI specs, and clear governance guidelines for enterprise delivery.

Does this API design approach work for both REST and AsyncAPI event-driven patterns?

Yes, this API design approach works for both REST and AsyncAPI event-driven patterns by applying standardized resource modeling, error handling blueprints, and security policies across REST, GraphQL, gRPC, and AsyncAPI protocols.

When do I need a production-grade orchestrator for API design?

You need a production-grade orchestrator for API design when your teams are building enterprise-grade APIs that require strict standardization, cross-protocol governance, versioning policies, and clear error handling blueprints.

What limitations exist when standardizing error handling across gRPC and GraphQL APIs?

Standardizing error handling across gRPC and GraphQL APIs requires navigating distinct protocol-specific error paradigms, necessitating a unified governance policy to produce clear, consistent error handling blueprints across the diverse API patterns.