blaze-craft

Run a full api-craft contract design pass on a new or changed surface. Produces the contract shape, OpenAPI / GraphQL spec entries, error envelope, pagination + idempotency + rate-limit specs as applicable.

Audit the API error envelope and controlled-vocabulary `code` set; converge to RFC 9457 problem+json.

Design or audit the API versioning strategy and deprecation policy for a given API.

Design a webhook contract — payload schema, HMAC signing, retry policy, dead-letter, replay protection, ordering statement.

Coordinate parity between App Store Connect and Play Console for a release — version numbers, release notes, screenshots, privacy disclosures, age ratings.

Reviews any change touching API surface area for breaking changes, error envelope consistency, versioning discipline, idempotency, rate-limit headers, webhook signing, pagination shape, and OpenAPI / GraphQL spec drift. Use when the user opens a PR that modifies a handler, route, or spec file; or when the user explicitly asks for an API contract review. Returns a verdict (PASS / FAIL / NEEDS-WORK) plus a list of findings ranked by severity. Does not write code.

Walks the mobile stack-choice decision tree from the mobile-craft skill (workflow-playbook Phase 3) and produces a stack decision record. Use when the user asks "should I build this native, RN+Expo, or Flutter?" or any variant. Inspects the actual feature set, team capability, and shipping constraints — does not assume from project name. Returns a decision document, not code. Hands off to ios-craft / react-native-foundations / expo for implementation.

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).

Mobile orchestration and decision-making — the layer above platform implementation skills. Owns stack-choice phase (native vs RN+Expo vs Flutter, with constraints documented), cross-runtime patterns (offline-first sync, push delivery, deep linking, biometrics, background work where iOS / RN / Expo have different shapes but the contract should stay consistent), and cross-store shipping discipline (parity between App Store Connect and Play Console for release notes, screenshots, privacy disclosures). Hands off Apple-platform implementation to ios-craft, React Native to react-native-foundations, Expo to expo. Android is a sub-domain reference, not a primary focus, since shipping has been Apple-platform-led to date. Use when the user mentions: mobile, mobile app, native app, mobile stack, native vs Expo, native vs React Native, native vs Flutter, RN vs Expo, Expo vs native, Flutter vs RN, mobile architecture, mobile shipping, cross-platform, cross-runtime, cross-store, App Store + Play Store, App Store Connect + Play Console, parity release, mobile release plan, mobile push, deep link strategy, Universal Links, App Links, deferred deep link, offline-first, mobile offline sync, mobile background sync, mobile biometrics, Touch ID, Face ID, Android biometrics, mobile observability. Do NOT trigger for: Apple-platform implementation (use ios-craft); React Native implementation (use react-native-foundations); Expo / EAS implementation (use expo); web responsive (use frontend-craft); pure 3D scene that isn't a shipped app (use game-development or ar-vr-development).