api-patterns-skill

Generate API design sections aligned with enterprise REST and governance standards.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/dacy/architect-skill --skill api-patterns-skill-dacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-patterns-skill
Source: https://github.com/dacy/architect-skill/tree/main/.claude/skills/api-patterns-skill
Command: npx skills add https://github.com/dacy/architect-skill --skill api-patterns-skill-dacy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

APIs across organizations often diverge from established enterprise standards in design, versioning, authentication, and governance. This Skill provides a structured approach to generate API design sections that align with defined standards and flag deviations early in the development lifecycle.

Core Features & Use Cases

  • Generate API design content that adheres to enterprise standards (REST, versioning, auth, rate limiting, contract design)
  • Flag deviations against standards sources such as api-standards.md, error-codes.md, gateway-policy.md, and openapi-template.yaml
  • Auto-triggered by orchestration for any solution with API surface area to ensure consistent governance

Quick Start

Generate a Confluence-ready API Design section for your API surface while applying the organization's standards.

Frequently Asked Questions about api-patterns-skill

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

FAQPage Schema
How do I enforce enterprise API standards across REST endpoints and versioning?

API design standardization applies rules to REST endpoints, versioning, authentication, rate limiting, and contracts. It ensures consistent governance across solutions with an API surface by flagging deviations early in the development lifecycle.

What is the best way to flag API design deviations against OpenAPI templates?

The best way to flag API design deviations is to validate your API surface against standards sources like openapi-template.yaml, api-standards.md, and gateway-policy.md, which identifies misalignments early in the lifecycle.

Can I generate a Confluence-ready API design section for my API surface?

Yes, you can generate a Confluence-ready API design section for your API surface. This process applies the organization's enterprise standards for REST, authentication, and contracts directly to the generated documentation.

Does API standardization work without custom error-codes or gateway-policy references?

API standardization works without custom references by applying enterprise defaults. When standards files like error-codes.md or gateway-policy.md are absent, the process falls back to default rules for contracts and inter-service boundaries.

How do I apply gateway policy and rate limiting rules to inter-service boundaries?

You apply gateway policy and rate limiting rules to inter-service boundaries by enforcing API design standardization across the entire API surface, ensuring all service contracts satisfy the defined governance policies.