Design REST and GraphQL APIs with OpenAPI 3.1 specifications and operational details.
npx skills add https://github.com/EliasOulkadi/shokunin --skill api-forge
Please help me install this Agent Skill. Skill: api-forge Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/api-forge Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill api-forge
This Skill solves the problem of designing consistent, reliable HTTP APIs by turning product requirements into a complete API contract with predictable behavior for errors, pagination, rate limiting, webhooks, and idempotency.
Example use case: you need an API for an orders system with secure endpoints, cursor pagination for public listing, webhook notifications for order.created, and safe POST behavior using Idempotency-Key.
Ask the AI to design a REST API with cursor pagination, standardized error envelopes, rate limiting headers, webhook delivery with HMAC-SHA256 verification, and Idempotency-Key support for POST create endpoints.
High-intent search queries and answers about installing and using this skill.
Designing a REST API with OpenAPI 3.1 involves generating specifications with endpoint summaries, parameters, and structured error envelopes containing request_id and code mappings for predictable HTTP behavior. This process ensures consistent status-code mapping and fully enumerated responses across all endpoints.
Implementing cursor-based pagination and rate limiting requires defining operational design details with cursor constraints and token-bucket rate limiting tiers within your API contract. This approach enforces production-grade HTTP semantics and manages data retrieval efficiently for public listing endpoints.
Adding webhook delivery with HMAC-SHA256 signature verification to an API design entails specifying webhook retry mechanisms and signature validation within the operational design details. This ensures secure, reliable event notifications for resources like order.created actions.
Idempotency-key behavior for POST create endpoints works by applying Stripe-style patterns to ensure safe create and update flows without duplicate processing. Defining this behavior in your API contract prevents accidental duplicate requests from creating multiple identical resources.
Yes, you can use this API design approach for both REST and GraphQL services by producing an OpenAPI 3.1 specification alongside operational design details for real HTTP services. It accommodates defining resources, endpoints, response contracts, and production security checklists for both architectures.
A production-ready API security checklist for HTTP services should include input validation, safe failure responses, structured error envelopes, and webhook HMAC-SHA256 signature verification. Enforcing correct method usage and consistent status-code mappings ensures secure, reliable operational behavior.
wesleyegbertoGenerate OpenAPI 3.1 specifications and resource models for REST and GraphQL APIs.
jg-chalk-ioDesign REST and GraphQL interfaces enforcing OpenAPI 3.1 authentication and rate limiting policies.
Renzo-TognellaDetect API abuse and DDoS attacks with adaptive rate limiting algorithms.
nahisahoDesign RESTful, GraphQL, and gRPC APIs with OpenAPI and Protobuf definitions.
