🍷 dsh-palate — an eye that grows

Design-audit tools measure with a fixed ruler. dsh-palate trains an eye that grows.

Most design-review plugins ship a static ruleset and apply it forever — use them once or a thousand times, the judgment is identical. dsh-palate is the opposite: it keeps a taste corpus that accumulates. Every example you feed it and every principle you distill sharpens the judgment your agent draws on. The more you use it, the better its eye gets.

Why this exists

Taste is not a gift — it's pattern recognition built from exposure. See enough good and bad design, and the rules emerge. dsh-palate turns that into a mechanism an agent can actually use:

1. Observe — inspect a screenshot, URL, or design and name concrete visual evidence
2. Stage — turn that analysis into examples and principles that wait in a reviewable candidate queue
3. Confirm — only an explicit accept/reject decision changes the corpus; rejected ideas stay visible without changing taste
4. Review — critique a new design against the accumulated taste, not a generic checklist
5. Calibrate — record which recommendations actually helped; only confirmed helpful principles gain evidence, so the palate compounds honestly

What the agent gets

Tool	What it does
palate_intake	Stage a structured visual analysis as pending example/principle candidates; it never changes taste by itself
palate_candidates	Inspect pending, accepted, or rejected visual-training candidates and their source sessions
palate_decide	Apply the user’s explicit accept/reject decision; this is the only candidate-to-palate mutation path
palate_review	Assemble the accumulated taste (principles + relevant past examples) as context, so the agent critiques grounded in learned judgment
palate_feedback	Use a review_id to record whether a critique helped and which principles were accepted or rejected; only accepted principles gain evidence
palate_add	Feed an example (good/bad/note + reason + tags) into the corpus — grows the palate
palate_learn	Distill a new principle from experience and add it to the codified taste
palate_packs	Inspect opt-in visual-reference packs and whether they are already applied
palate_seed	Apply one or more visual-reference packs exactly once, without overwriting existing taste
palate_list	Browse the accumulated corpus
palate_principles	List the codified principles, ordered by evidence
palate_effectiveness	See which principles were accepted or rejected in real review feedback
palate_stats	How much taste has accumulated: examples studied, principles distilled

Ships with a starter palate of 12 foundational principles plus four transparent teaching examples (good and bad dashboards, a readable table, and generic landing-page boilerplate), so the first review has concrete evidence — then it grows from there.

The four starter examples are inserted only when the local taste database is empty. Installing or upgrading the plugin never overwrites an existing palate.

Visual reference packs: Apple and X

dsh-palate also ships two opt-in visual-reference packs:

…