How it works

┌──────────────┐       ┌────────────────────────┐       ┌────────────────┐
│ your task    │──────▶│ tastecode              │──────▶│ provider CLI   │
│ (CLI arg)    │       │  reads tastecode.md    │       │  (claude/codex/│
│              │       │  builds enhanced prompt│       │   aider/...)   │
└──────────────┘       │  spawns provider       │       │                │
                       └────────────────────────┘       └────────────────┘

When you run tastecode use claude "add a login page":

1. Read tastecode.md (falls back to .tastecode/taste.md or .tastecode/taste.json).
2. Build an enhanced prompt:
   • TasteCode preamble
   • Full taste-file contents
   • Your task
   • Strict rules: minimal edits, no overcoding, match project style
3. Spawn the local provider CLI (e.g. claude -p with prompt via stdin) and stream its output back to your terminal.

TasteCode itself does not contact any model. All network calls happen inside the wrapped tool, with its own auth and permission settings.