Help us improve
Share bugs, ideas, or general feedback.
From blaze-craft
Wire contract design — REST, GraphQL, RPC, gRPC choice, versioning strategy, breaking-change discipline, error envelope schemas, pagination patterns, idempotency keys, rate-limit semantics, webhook contracts (signing / retry / ordering), authentication on the wire, SDK ergonomics, and API documentation as the developer entry point. Use when the user mentions: API design, API contract, REST API, GraphQL, gRPC, RPC, OpenAPI, Swagger, JSON Schema, AsyncAPI, problem+json, RFC 9457, RFC 7807, error envelope, error code, pagination, cursor pagination, offset pagination, idempotency, idempotency key, rate limit, rate limiting, 429, X-RateLimit, Retry-After, webhook, webhook signing, HMAC, retry policy, dead-letter, exponential backoff, jitter, API versioning, semantic versioning, breaking change, deprecation, Sunset header, content negotiation, API authentication, Bearer token, API key, OAuth scopes, mTLS, SDK design, API SDK, API docs, developer experience, DX, contract testing, Pact, Spectral, OpenAPI lint. Pair with fullstack-engineer / cloudflare for handler implementation, supabase for data layer, auth0 for auth provider config. Do NOT trigger for: handler implementation (use fullstack-engineer / cloudflare); database schema design (use supabase); auth provider configuration (use auth0 / supabase); UI work consuming an API (use frontend-craft).
npx claudepluginhub blaze-sports-intel/blaze-craft --plugin blaze-craftHow this skill is triggered — by the user, by Claude, or both
Slash command
/blaze-craft:api-craftThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
API design as a craft separate from API implementation. This skill owns the **wire contract** —
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
API design as a craft separate from API implementation. This skill owns the wire contract — the shape of the conversation between the service and its consumers — independent of how the service is implemented underneath.
Triggers: API design, API contract, REST, GraphQL, gRPC, RPC, OpenAPI, Swagger, JSON Schema,
AsyncAPI, problem+json (RFC 9457 / RFC 7807), error envelope, error code, pagination (cursor or
offset), idempotency, idempotency key, rate limit, 429, X-RateLimit-*, Retry-After, webhook,
HMAC signature, retry policy, dead-letter queue, exponential backoff, jitter, API versioning,
breaking change, deprecation, Sunset header, content negotiation, Bearer token, API key, OAuth
scopes, mTLS, SDK design, API SDK, API docs, developer experience, DX, contract testing, Pact,
Spectral, OpenAPI lint.
Use when the user wants any of:
Accept-Version header, media-type versioning) and
the deprecation / Sunset policy that goes with it.code discipline).total_count is returned and at what cost).X-RateLimit-Limit /
X-RateLimit-Remaining / X-RateLimit-Reset / Retry-After headers, 429 behavior.fullstack-engineer or cloudflare (Workers, Hono).supabase or the runtime's data layer skill.supabase /
auth0.frontend-craft.references/official-sources.md — RFCs
(9457, 9110, 8594, 6585), OpenAPI 3.1 spec, JSON Schema 2020-12, OAuth 2.1 draft, AsyncAPI.workflow-playbook.md).quality-rubric.md for the full matrix.Sunset header values, migration guide.code
values, the mapping from internal error to wire error.next / prev link
headers (RFC 8288), how total_count is or isn't returned.Idempotency-Key header semantics, replay window, conflict behavior
when the same key arrives with a different body.Retry-After.The full catalog with concrete fixes lives in references/anti-patterns.md. Highlights:
meta envelope (no source, no fetched_at, no
timezone).Retry-After (client retries immediately, makes it worse).meta.fetched_at populated with the current request time instead of
the upstream data's actual freshness.code from the controlled vocabulary./api-design <surface> — full contract design pass on a new or changed surface./api-versioning <api> — versioning strategy and deprecation policy./api-errors <api> — error envelope review and controlled-vocabulary cleanup./api-webhook <event> — webhook contract design with signing, retry, dead-letter.references/official-sources.md — RFCs, OpenAPI 3.1, JSON Schema, OAuth 2.1, AsyncAPI.references/workflow-playbook.md — long-form workflow with Phase 4 capability→artifact map.references/anti-patterns.md — full anti-pattern catalog with concrete fixes.references/quality-rubric.md — pass/fail rubric for contract review.references/examples.md — real before/after invocations.scripts/validate_skill.py — sanity-checks SKILL.md frontmatter and references via the
shared plugin-level validator.A real client calling the API gets a predictable, documented, schema-valid response — and the error path is just as predictable as the success path. Build success on the maintainer's machine is not done. 200 from the handler is not done. The contract-specific states below all need to hold:
code from the controlled
vocabulary, and the HTTP status matches the semantic.Sunset header and a documented migration path.Verification actually happened — evidence captured (curl transcript, linter output, schema validation result, signed webhook delivery log).