Define REST and HTTP API conventions for Figurio backend endpoints.
npx skills add https://github.com/cellarwood/figurio --skill api-design-cellarwood
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/cellarwood/figurio/tree/main/skills/api-design Command: npx skills add https://github.com/cellarwood/figurio --skill api-design-cellarwood
Help engineers design and change Figurio's backend HTTP APIs so they are predictable, safe, and maintainable, reducing payment, fulfillment, and integration regressions.
Draft an orders API that returns the canonical order resource after writes, validates ownership and state transitions, requires idempotency for payment-affecting endpoints, and verifies Stripe webhook signatures.
High-intent search queries and answers about installing and using this skill.
To design REST APIs with idempotency for payment endpoints, enforce idempotency keys on charge-related writes, return canonical resources after writes, and use 409 status codes for conflicts to ensure predictable behavior.
Handling Stripe webhook signature verification in a REST API requires validating webhook signatures, enforcing event idempotency, and applying reconciliation best practices to prevent payment regressions and ensure safe fulfillment integration.
Structuring error semantics in HTTP APIs for order lifecycle workflows involves returning short actionable error payloads, validating ownership, and using explicit state transitions to maintain predictable behavior across services.
Yes, this REST API design approach supports custom generation job and preview delivery endpoints by applying resource-oriented REST patterns with plural collections and stable IDs across catalog, checkout, and operator-facing services.
When changing backend HTTP API conventions, follow testing expectations covering contract tests, idempotency validation, webhook replay handling, and edge cases for stateful workflows to verify safe and maintainable integration.
You need idempotency keys for charge-related writes in REST APIs to prevent duplicate charges during network retries, ensure safe payment processing, and maintain consistent state transitions across order lifecycle workflows.
hendrax5Standardize REST API responses, URL versioning, pagination, and error mapping.
lekemulaGenerate RSpec or Minitest tests for Ruby on Rails classes.
arbazkhan971Integrate Stripe payment processing and subscription billing into web and mobile backends.
yusufcmgGuide REST and GraphQL API design with patterns and best practices.
