What problem does it solve? Freight work in this monorepo must preserve byte-compatible Firestore wire shapes from the legacy Flutter ERP, and the Melhor Envio OAuth → quote → buy → print → track → webhook flow has many non-obvious traps (opaque cart 500s, token refresh races, per-tipo capability flags). This Skill provides the domain reference needed to implement, debug, or review freight code without breaking migrated data. ## Core Features & Use Cases - Architecture map: Locates every freight layer — the platform-neutral packages/integrations/freight-br client, the API-only apps/melhor-envio app, the web UI Frete tab and etiqueta row action, and the Zod schemas with the FREIGHT_TIPO_CAPS capability table. - Wire-compat guardrails: Documents critical traps such as externalOptionIntegracao being the tipo enum (not a doc id), single-token tokenMelEnv refresh with loser re-read fallback, and the Jadlog agency requirement behind opaque cart HTTP 500 errors. - Provider extension playbook: Gives a compiler-gated 7-step checklist for adding a new freight tipo or provider across the emit, fetch, and generic label categories. - Use Case: When a comprar etiqueta call fails with an unexplained 500, use this Skill to identify the missing drop-off agency on the cart insert and debug it with the debug:me-cart fixture script. ## Quick Start Ask the assistant to explain why a Melhor Envio label purchase returns an opaque 500 error and how the freight webhook maps carrier statuses to pedido states.