Use casesResearch

Catch design-system drift before the system rots

Mitra watches your Figma libraries for components that have drifted off the design system, either detached from the original or restyled with values that are not tokens. The agent groups what it found by file and opens a Linear issue for the cases that spread widest. Every run is recorded step by step.

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

The prompt

Every Thursday at 4pm, go through our Figma libraries for components that have been detached or restyled with values that are not in our tokens. Open a Linear issue for anything used on more than three screens, and post the full list to #design-system in Slack 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, along with the screens they appear on.
File the ones that spread
Anything appearing on more than a handful of screens becomes a Linear issue, so the fix is tracked rather than mentioned once.
Post the whole picture
The rest goes to Slack grouped by file, so the team can see the shape of the drift without opening Figma.

Make it yours.

Designers and front-end engineers who share a component library and would rather not discover 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, collecting anything detached or restyled with off-token values. The agent 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.