Loading

Design system drift review

Shipped screens and PRs flagged for design-system drift.

15 minDesignClaude Cowork
Loading

Set up

Try a plugin

The Design plugin ships with /design-system already structured to audit components for naming, token use, and hardcoded values. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.

DesignAccelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs.
Add
/design-systemAudit, document, or extend your design system.
Open in Claude
/ux-copyWrite or review UX copy — microcopy, error messages, empty states, CTAs.
Open in Claude

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

GitHub
Read open PRs that touch UI and post the drift report as a review comment.
Connect
Figma
Use the published library as the source of truth for tokens and components.
Connect
SlackOptional
Post the daily drift summary to the design-system channel for triage.
Connect

Set your working folder

Drag the files you'll use (production screenshots, the PR diffs you're reviewing, your tokens file, the component inventory) into one folder on your machine, then give Claude access to it in the Claude desktop app. Claude reads from the folder and writes the drift report back to it. If you run design QA regularly, create a project from that folder so your system source stays attached.

Design-QA / Sprint-42
prod-settings-billing.pngApr 27, 2026820 KB
pr-4821-billing-panel.diffApr 27, 202614 KB
tokens.jsonApr 20, 202618 KB
In Cowork’s chat bar:Design-QA / Sprint-42

The prompt

Copy this into Claude

Review the shipped screens and open PRs in this folder against our design system. For each one, list every place it drifts from our tokens, components, spacing, or interaction patterns, rate the severity, and suggest the system-compliant fix. Skip anything that already matches.

Design-QA / Sprint-42

Why this works

Prompt

Spell out what to check for. Tokens, components, spacing, interaction: the checklist is explicit.

Prompt

Ask for a severity on each finding. Triage knows what to fix this sprint.

Prompt

Say what to leave out. The report is only the work, never the noise.

Source

Put the reference files in the folder. Tokens and inventory are read, not remembered.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Claude work for you

Once the prompt produces a drift report you'd actually post on a PR, tell Claude to save what you've done as a skill of your own. Layer in your severity thresholds, your allowed exceptions, your component-to-code mapping, and the comment tone your engineers respond to. A few minutes of conversation and the skill runs with your standards from then on.

Make what we've done in this task so far into a skill called /drift-review.

Design-QA / Sprint-42

Review the skill, and save it if Claude hasn't already.

Make it repeatable

Share it as an artifact

Drift compounds quietly between sprints. Ask Claude to publish the report as an artifact and the design-system team has one link — re-run the skill or schedule it to refresh.

Publish that drift report as an artifact for the design-system channel. Keep a running tally of high-severity items still open.

Design-QA / Sprint-42

Run it on every PR that touches UI

Drift is cheapest to catch before merge. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and set /drift-review to run twice a day, checking open PRs and the latest production screenshots.

Set up a scheduled task for weekdays at 10am and 4pm: check open PRs labeled "ui" and Design-QA/Sprint-42 for new screens, run /drift-review on each, and draft the drift report as a PR comment or a #design-system post for me to approve.

Design-QA / Sprint-42
Scheduled taskActive
UI drift check

At 10am and 4pm, checks open UI PRs and the QA folder, runs /drift-review, and drafts the drift report as a PR comment or a #design-system post for your approval.

Every weekday at 10 am & 4 pm · checks open UI PRs and Design-QA/Sprint-42Open in Claude

To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.

Share with your teammates

Your /drift-review skill now carries your tokens, your component map, your severity scale, and your exception list. Share it so every squad gets the same review on every PR, and the system team stops being the bottleneck for "is this on-system."

What changes for design QA