What problem does it solve? Debugging the BMRC Logistics app often means rediscovering the same root causes: wrong stock numbers, stale config, Firestore Timestamp crashes, and permission quirks. This playbook maps each recurring symptom to its real cause and fix so you stop inventing theories and start from known failure classes. ## Core Features & Use Cases - Symptom-to-cause tables: Look up wrong numbers, lost or duplicated items, stale configuration, crashes, and auth weirdness, each mapped to the exact module and fix. - Emulator-first reproduction: Guides reproduction on the Firebase emulator with seeded data instead of poking production, including invariant test checks. - Cross-skill routing: Points to the right companion skill (domain, UI, testing, migrations) when the bug belongs to another concern. - Use Case: An item shows as expired even though the expired lot is used up. The playbook identifies the zero-stock tombstone batch carrying the old expiration and directs you to filter with batchHasStock(). ## Quick Start Use the bmrc-debugging skill to investigate why an item shows the wrong status in the BMRC Logistics app.