What problem does it solve? Architects and product managers writing specs for SMB retail or e-commerce products often produce naive designs: flat product tables without variants, single-channel inventory that oversells, reorder logic without lead time, and pricing rules that break margin floors. This Skill injects the domain knowledge needed to spec storefront, inventory, pricing, and cart-recovery features correctly the first time. ## Core Features & Use Cases - Domain Vocabulary & Rules: Codifies SKU vs variant, reorder point math (demand × lead time + safety stock), ATS, COGS/landed-cost margin, MAP, and cart abandonment metrics. - Must-Model Entities: Defines the Product→Variant option matrix, channel-aware InventoryLevel, ReorderRule, PricingRule with margin floor, and AbandonedCart with consent/suppression. - Naive-Build Anti-Patterns: Flags the common failures — no variant model, single-channel inventory, reorder without safety stock, and cart recovery that ignores CAN-SPAM/TCPA/GDPR consent. - Use Case: When speccing a multichannel inventory feature for an SMB seller, apply this Skill to produce a Retail domain section in the ARCH/PLAN doc covering variant modeling, reorder-point math, and the Shopify wedge strategy. ## Quick Start Apply the vertical-retail skill while drafting the architecture spec for a multichannel inventory and cart-recovery product for an SMB seller.
