What problem does it solve? Building a new marketplace channel (Shopee, Amazon SP-API, Magalu, Loja Integrada) in this monorepo is error-prone: there is deliberately no shared channel interface, capability claims must be evidence-based, and stock sync can silently burn Firestore Enterprise budget. This Skill enforces a docs-first, capability-driven process so a new channel is planned from the provider's own documentation rather than copied from Mercado Livre. ## Core Features & Use Cases - Four-phase workflow: survey the provider's documentation, fill the MARKETPLACE_TIPO_CAPS row with three-valued capabilities, generate a ~20-step master plan, then plan each step at implementation time. - Reference catalogue: carries the Mercado Livre implementation capability-by-capability, explicitly marking which decisions are ML-specific evidence (orderML mirror, tokenDuravel, unsigned webhooks) versus generic patterns. - Cost and concurrency guardrails: stock-sync read/write cost axes, watermark unit rules, shared seams (notification pipeline, OAuth state, read cache, findOrCreateCliente) that must be reused instead of re-rolled. - Use Case: When asked to add Shopee as a new sales channel, use this Skill to produce the capability survey, the caps row, and the ordered master plan of issues before writing any code. ## Quick Start Use the marketplace-integration skill to plan a new Shopee sales channel, starting with a capability survey of Shopee's official API documentation.
