doordash-allergy-shield

原文涵盖的主题

• DoorDash Allergy Shield
• Honest limits (state these to the user on first use)
• Components in this bundle
• State
• Protocol
• Session start
• After EVERY cart mutation (add-items / remove-item / reorder)
• At checkout

Claude has no cross-session memory: tell it "I'm allergic to peanuts" today and tomorrow it happily adds pad thai. This skill persists a dietary profile and makes cart vetting mandatory — with a deterministic hook double-checking the highest-severity allergens before any checkout URL is emitted. Unofficial community skill built on DoorDash's doordash-oss/doordash-cli. Matching is heuristic, against item names/descriptions from cart show output plus a synonyms table. It cannot see full ingredient lists and knows nothing about cross-contamination in the kitchen. It is a tripwire against agent mistakes, not a medical device. The DoorDash payment page — where the human reviews the real order — is the documented final check. False positives are accepted by design: blocking a safe ponzu bowl is cheap; the reverse is not. Hook matching is substring-based (short allergen names like "oat" can match inside "goat cheese") — annoying, never dangerous. The references/allergen-synonyms.md table is intentionally broader than the compact synonym subset hardcoded in the checkout-gate hooks; adding a synonym to the reference doc alone does not change what the hooks enforce. | Piece | Role | |---|---

这里只展示节选，请以完整原文和当前要求为准。