shine-api-design

Generate OpenAPI 3.1 skeletons or GraphQL SDL for a given domain.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-api-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-api-design
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-api-design
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-api-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing consistent API surfaces for REST or GraphQL can be error-prone and time-consuming. This skill generates a ready-to-review API blueprint using OpenAPI 3.1 or GraphQL SDL for a given domain, ensuring consistency and reducing boilerplate.

Core Features & Use Cases

  • OpenAPI 3.1 skeleton generation: Resources, operations, schemas, error envelopes, pagination, and versioning policy.
  • GraphQL SDL generation: Types, inputs, enums, and basic resolver outlines for a domain.
  • Auth & security modeling: OAuth 2.1 / API key schemes with rate limiting and standardized error definitions.
  • Use Case: Design an API surface for a domain such as "inventory" or "customers" and obtain a draft API contract ready for review.

Quick Start

Provide a skeleton OpenAPI 3.1 document (or GraphQL SDL) for the given domain and review the draft.

Frequently Asked Questions about shine-api-design

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

FAQPage Schema
How do I generate an OpenAPI 3.1 skeleton for a specific domain?

To generate an OpenAPI 3.1 skeleton, provide your target domain such as inventory or customers to the API design tool. It outputs a ready-to-review draft contract covering resources, operations, schemas, pagination, and error envelopes.

Can I generate GraphQL SDL and resolver outlines for my API design?

Yes, you can generate GraphQL SDL for your domain. The API design process creates types, inputs, enums, and basic resolver outlines, providing a structured draft blueprint ready for immediate review.

How do you model authentication and rate limiting in an API contract?

Model authentication and rate limiting in an API contract by applying OAuth 2.1 or API key security schemes. This approach defines standardized error responses and rate limiting policies directly within the generated specification.

What is the best way to design consistent REST API resources and pagination?

The best way to design consistent REST API resources and pagination is to automate the API surface design. This generates a standardized OpenAPI 3.1 blueprint, ensuring consistent versioning policies and reducing boilerplate errors.

Do I need to manually define error envelopes and versioning for my API design?

No, you do not need to manually define error envelopes and versioning. The API design automation includes these policies and standardized error definitions within the generated OpenAPI or GraphQL draft automatically.