Use casesResearch

Catch design-system drift before the system rots

Mitra watches your Figma libraries for components that drifted off the design system. The agent finds anything detached from the original or restyled with values that are not tokens. It groups the results by file and opens a Linear issue for the cases that spread widest.

Runs: Thursdays at 4pm
Used by: Design · Engineering

The prompt

Every Thursday at 4pm, find the Figma components that were detached or restyled off-token. Post the list to #design-system, grouped by file.

Figma

Linear

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Walk the libraries
The agent opens the files you named and compares each instance against the library component it came from.
Collect off-token values
Colors, spacing and type that match no token are gathered, with the screens they appear on.
File the ones that spread
Anything on more than a handful of screens becomes a Linear issue, so the fix is tracked rather than mentioned.
Post the whole picture
The rest goes to Slack grouped by file, so the team sees the shape of the drift without opening Figma.

Make it yours.

For designers and engineers who share a library, and learn its true state midway through a redesign. Change any of this by saying so — there is nothing to rewire.

Run it monthly instead, if your library moves slowly.
Skip the Linear issues and keep it as a Slack digest.
Narrow it to one product area and leave marketing pages out.

Questions, answered.

How do I find components that have drifted from our design system?

Mitra reads your Figma libraries on a schedule and compares each instance against the component it came from. The agent collects anything detached or restyled with off-token values, groups the results by file, and can open an issue for the worst cases. You describe the rules in plain English.

Does Mitra fix the drift itself?

No. Mitra finds the drifted components, names the screens they appear on, and files them for a person to fix. The judgement about whether a detached component was a mistake or a deliberate exception stays with the designer who owns the library.