Skip to main content
Home/Recipes/Track token drift
Automation

39.Track token drift

DeveloperDesignerQAEnterprise

Overview

Pin a release as the visual baseline. After the next sprint, extract again. The Dembrandt App shows exactly what changed: which tokens shifted, which disappeared, and which are new.

Token drift is the slow accumulation of small visual deviations that nobody catches in the moment. A color is approximated from memory. A spacing value gets rounded. A border radius changes in one component but not others. Over time the brand feels off, but no single change is large enough to trigger a review. Load an extraction into the Dembrandt App and pin it as the visual baseline. After the next release cycle, run a new extraction and load it alongside. The App computes a per-token diff: what changed, by how much, what is new, what is gone. Catch drift before it compounds.

Extract baseline

Terminal
dembrandt app.company.com --save-output

Extract after next release

Terminal
dembrandt app.company.com --save-output
Agent prompt: ASCII diff
# Load both extraction JSON files into context, then:
"Compare these two extractions from the same site.
Show the token diff as an ASCII table:
TOKEN | BEFORE | AFTER | DELTA
Flag any change above 10% with ⚠️.
Summarize what changed and whether it looks like intentional
update or unintentional drift."
App workflow (visual diff)
# dembrandt.com/app
# 1. Drag baseline JSON → pin as baseline
# 2. Drag new extraction → compare against baseline
Output

ASCII token diff table with delta values + drift summary. Or visual diff in the Dembrandt App.

Browse all

All recipes →

43 workflows