Doordash Profile
Manage the dietary profile (allergens with severity tiers, diets, dislikes) used by doordash-allergy-shield to vet DoorDash carts
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/doordash/doordash-profile.md
---
allowed-tools: Bash(cat:*), Bash(mkdir:*), Bash(jq:*), Read, Write, Edit
argument-hint: [show | add <person> | edit <person> | rm <person>]
description: Manage the dietary profile (allergens with severity tiers, diets, dislikes) used by doordash-allergy-shield to vet DoorDash carts
---
# Dietary Profile Manager
Manage the doordash-allergy-shield dietary profile: **$ARGUMENTS**
State: `~/.claude/doordash-profile/dietary.json`. This command is the sanctioned
way to edit it — the vetting flows treat the profile as human-confirmed
input, so every change here must be explicitly confirmed by the user.
## Current State
- Profile: !`cat ~/.claude/doordash-profile/dietary.json 2>/dev/null || echo "(no profile yet)"`
## Task
Parse `$ARGUMENTS` and run the matching subcommand:
### `show` (default when no arguments)
Render the profile as a table per person: allergens (with severity),
diets, dislikes. Explain the severity tiers:
- `anaphylaxis` — hook-enforced at checkout, never overridable in-session
- `avoid` — conflicts require explicit acknowledgment
- `preference` — mentioned, not gated
### `add <person>`
Interview the user for the new person:
1. Allergens — for each, ask the severity tier explicitly. Never assume
severity; if the user says "allergic to X" without qualifying, ask
"would exposure be dangerous (anaphylaxis-tier) or is it avoid-level?"
2. Diets (vegetarian, vegan, halal, kosher, gluten-free, ...).
3. Dislikes.
4. Read back the complete entry and confirm before writing.
### `edit <person>`
Show the person's current entry, ask what to change, confirm the final
entry before writing. Severity downgrades of an `anaphylaxis` entry require
the user to type the allergen name back explicitly — make deliberate
friction for the dangerous direction.
### `rm <person>`
Show the entry, confirm, remove.
## Rules
- Keep the JSON schema exactly as doordash-allergy-shield documents it
(`people.<name>.allergens[].{name,severity}`, `diets[]`, `dislikes[]`) —
the checkout-gate hook parses this file.
- Read-modify-write the whole file; never append or shell-redirect into it.
- Never invent or infer allergens from past orders — this file is
human-declared only.
- After any change, remind the user that already-vetted carts were vetted
against the OLD profile; re-vet before checking out.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: fc424dadf2ca27f53f216d450b0e32addce6f29150105157970117de516cba8d. Files are served as downloads and are never executed by this page.