Design

Check the design system for drift every month

Once a month, Merlin compares your Figma library with the components in code. You get what differs, component by component, in #design-system.

@Merlin on the 1st of every month at 10:00, compare the components in our Figma library with the components in acme/web. Post here the components that exist in only one place and, for the ones in both, the variants and props that don't match. Only report: don't change Figma or the code.

#design-system
Get started for free
  1. Starts whenA monthly schedule runs on the 1st at 10:00 and posts to #design-system
  2. Merlin worksClaude Code or Codex reads the Figma library with the Figma MCP and the component code in GitHub, then compares names, variants and props
  3. You getA list in #design-system of components that exist on one side only and variants that don't match

Tools

  • Slack
  • Figma
  • GitHub

Capabilities

  • Automations
  • Integrations
  • Your agent's MCP

How it works

From the Figma library and the code to a monthly drift report.

On the 1st of every month at 10:00, a schedule starts a run and posts to #design-system.

/AcmeTeam/Automations/Check the design system for driftFeedback?M

Overview

Agents

Skills

Memory

Automations

Integrations

Settings

Check the design system for drift

Pause
StatusActive
CreatorM Mia You
ScopeWorkspace
Last runSep 1, 2026, 10:00 AM

DetailsRun history

Trigger

When Merlin runs it.

RuleHow often Merlin runs it.Monthly
Day of monthShort months use their final day.1
TimeNext run Nov 1, 2026, 10:00 AM.10:00

Run

What Merlin does each time, where it runs, and where the result goes.

Run instruction

on the 1st of every month at 10:00, compare the components in our Figma library with the components in acme/web. Post here the components that exist in only one place and, for the ones in both, the variants and props that don't match. Only report: don't change Figma or the code.

RuntimeThe computer and coding agent that run it.Mia's MacBook Pro · Claude Code
DestinationWhere Merlin posts the result. Choose None when the instruction already acts in your tools.#design-system

Before and after

Drift gets caught every month instead of at the next redesign.

Without Merlin

Someone lists the Figma library and the code side by side and compares them component by component.

  1. 01List the library's components
  2. 02List the components in code
  3. 03Line them up side by side
  4. 04Open each component's variants
  5. 05Read each component's props
  6. 06Mark what doesn't match
  7. 07Share the list in the channel

With Merlin

The comparison runs every month and the list is waiting in the channel.

  1. Day 1 of every month at 10:00Monthly schedule posting to #design-system
  2. Compares the library with the codeClaude Code with the Figma MCP
  3. What differs, in #design-systemReport only, nothing changed

Setup

Connect GitHub, give the agent Figma, then schedule the check from #design-system.

Set these up once and the report arrives on the 1st of every month. Whoever sends the prompt becomes the automation's creator.

  1. 01Connect a machineRuntimeInstall the Merlin desktop app or CLI on a computer running Claude Code or Codex. You can also use a machine a teammate shares with your workspace.
  2. 02Add Merlin to SlackIntegrationsInstall the Slack app and add Merlin to the channel you work in. A private channel needs /invite @Merlin.
  3. 03Add Figma to your agentYour agent's MCPConnect the Figma MCP server to Claude Code or Codex on the machine that runs this. Its credentials stay on that machine.
  4. 04Install the GitHub appIntegrationsPick the repositories Merlin can access, so it can read and link the pull requests there. Pushes use the machine owner's own Git access.
  5. 05Send the prompt from a machine with FigmaRuntime

    Runs act for the automation's creator and prefer a machine they own, then a public one. Sign the Figma MCP in there with a Dev or Full seat on a paid plan, since Figma's Starter plan allows only a few MCP calls a month.

  6. 06Paste the setup promptAutomationsSend the prompt below to @Merlin in Slack, in the channel it should post to. Merlin creates the automation and tells you what it set up.

Prompt

Schedule the monthly drift check with one prompt.

@Merlin on the 1st of every month at 10:00, compare the components in our Figma library with the components in acme/web. Post here the components that exist in only one place and, for the ones in both, the variants and props that don't match. Only report: don't change Figma or the code.

#design-system

Once, when you send it

  1. PromptYou send the prompt to @Merlin
  2. AutomationMerlin creates the automation

Every scheduled run

  1. ScheduleThe schedule starts a run
  2. RuntimeMerlin picks the creator's machine first
  3. ContextThe run gathers context
  4. WorkClaude Code or Codex compares Figma with the code
  5. ResultMerlin posts what differs in #design-system
  6. SteeringReplies in its thread follow up

Bring your coding agents into the tools your team already uses.

Let your whole team hand work to Claude Code and Codex today. Connect one machine and add Merlin to Slack, Linear or GitHub. 14-day free trial, no API keys, no card.