What problem does it solve? Monolithic commerce platforms become hard to scale and evolve when different domains like catalog, checkout, and loyalty need independent release cycles or best-of-breed vendors. This Skill guides the design of a composable commerce architecture where each capability is an independent service coordinated through APIs and events. ## Core Features & Use Cases - MACH Service Design: Define bounded contexts for catalog, search, CMS, checkout, payments, and fulfillment using vendors like commercetools, Algolia, Contentful, and Stripe. - BFF Aggregation & Resilience: Build a Backend-for-Frontend layer with parallel fetching, GraphQL schema stitching, and opossum circuit breakers with fallbacks. - Event-Driven Sagas: Coordinate distributed transactions with AWS EventBridge choreography, compensating transactions on payment failure, and additive API versioning with OpenTelemetry tracing. - Use Case: A retailer migrating off Magento can use this Skill to build a product detail page BFF that aggregates catalog, inventory, reviews, and recommendations while degrading gracefully when the inventory service slows down. ## Quick Start Use the composable-commerce skill to design a BFF aggregation layer with circuit breakers and an event-driven order saga for my headless storefront.
