CI/CD drift detection
Overview
Extract on every release and load into the Dembrandt App to diff against the pinned baseline. Teams that ship frequently catch visual drift before it accumulates into a rebrand.
Requires dembrandt 0.20.1 or later. Run npx dembrandt@0.20.1 --version to verify.
For teams that ship frequently, manual design review cannot keep up with the pace of releases. This is the artifact-based workflow: extract the deployed site after each release cycle, save the output, and archive it as a build artifact for later comparison. The Dembrandt App computes a per-token diff against the pinned baseline: what changed, what drifted, what is new. For hands-off history, pass an API key with --key instead and each run is uploaded and scored against the previous snapshot automatically (see the API-key drift recipe). Automated pass/fail gating in the pipeline is on the roadmap.
Extract after each release
Token snapshots archived per release. Agent produces ASCII diff on demand, no --compare flag needed.
More in Automation
Browse all
All recipes →
Continue reading
Getting started
Install Dembrandt and turn any public website into a complete set of design tokens in under 2 minutes. All you need is Node.js and a terminal.
MCP
Use Dembrandt as a tool inside Claude Code, Cursor, Windsurf, or any MCP-compatible editor. Your agent extracts live design tokens automatically when you ask.
Skills
30 UX and design system skills for AI agents. Install once, your agent designs with hierarchy, WCAG standards, and brand accuracy. The UX knowledge that normally costs senior consultant days.