What problem does it solve? Working on the FST/Otgruzka procurement module requires knowing its exact domain rules: purchase order statuses, container tracking limits, and warehouse receiving constraints. This Skill encodes those rules so changes to the procurement codebase stay consistent with the product model and never break Firestore data integrity. ## Core Features & Use Cases - Purchase Order Lifecycle Rules: Enforces the ЗЗ (purchase order) status flow from draft to arrived, including the rule that received is only set after warehouse acceptance, never by carrier sync. - Warehouse Receiving Guardrails: Ensures receiving writes proper stock movements with purpose: 'purchase' and the order number, and forbids deleting posted orders or moving stock from drafts. - Container Tracking Constraints: Documents Maersk/MSC tracking integration limits, including the lack of /api sync on Vercel production. - Use Case: When asked to add an auto-status update from carrier tracking, the Skill reminds you the maximum auto-status is arrived and that received requires explicit warehouse acceptance. ## Quick Start Ask the AI to review or modify the FST procurement module, for example to add a new purchase order status or fix the receiving flow, and it will apply these rules.