Design

Add the missing empty and error states

Mention Merlin on a Linear issue that names a screen. It adds the empty, error and loading states with your existing components and opens a pull request.

@Merlin from now on, when someone mentions you on an issue and asks for the missing states, find the screen the issue names and add an empty, an error and a loading state wherever it has none. Use our existing components and copy patterns rather than new ones, and open a pull request linked to the issue that lists each state and when it shows. If a state needs a design decision, check how comparable apps handle it on Mobbin and ask on the issue with what you found before writing it.

WEB · design
Get started for free
  1. Starts whenA designer mentions @Merlin in a comment on the Linear issue that names the screen
  2. Merlin worksClaude Code or Codex finds the screen in the code and adds empty, error and loading states with components you already have
  3. You getA pull request linked on the issue, listing each state it added and when it shows

Tools

  • Linear
  • GitHub
  • Mobbin

Capabilities

  • Integrations

How it works

From a comment on the issue to a pull request with every state.

Mention @Merlin in a comment on the Linear issue that names the screen. You don't need to open GitHub.

WEWEB › Issues › WEB-263

Invoices page has no empty or error state

A new workspace sees a blank table on /settings/invoices, and a failed load shows nothing at all.

Activity

Mianow

@Merlin can you add the missing states to /settings/invoices? Use what we already have for empty and error on other pages.

Leave a comment…

Properties

In Progress

Mia

Labels

Papercut

Before and after

Every screen gets its empty, error and loading states, not just the happy path.

Without Merlin

The designer files the gap, then waits for an engineer to find time and dig up the right components.

  1. 01Spot the blank invoices table
  2. 02File the missing states
  3. 03Ask which empty state to reuse
  4. 04Look up how other apps handle it
  5. 05Wait for an engineer to pick it up
  6. 06Find the invoices page code
  7. 07Add an empty state
  8. 08Handle the failed request
  9. 09Add a loading skeleton
  10. 10Fake each state to check it
  11. 11Open a pull request
  12. 12Link it on the issue

With Merlin

One comment on the issue gets all three states into a pull request.

  1. @Merlin in a comment on the issueAsked by the designer in Linear
  2. Adds the states with your componentsCodex edits the checked-out repository
  3. Pull request linked on the issueEach state and when it shows

Setup

Connect Linear and GitHub, then ask from any issue.

Set these up once and any designer can ask for a screen's missing states from its issue. A screenshot of the new state lands on the issue with the summary.

  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. 02Connect LinearIntegrationsOnce you connect your Linear workspace, Merlin can read the linked issue and comment there too.
  3. 03Install 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.
  4. 04Keep your code on the machineRuntimeMerlin reads the code in a local project on the runtime, so keep the repository checked out there.
  5. 05Keep Mobbin on your agentOptionalYour agent's MCPIf your machine's agent already uses the Mobbin MCP server, Merlin can use it here too. You don't need to set up anything in Merlin.
  6. 06Share a machine that has the codeRuntime

    Most designers don't keep the repository checked out. An engineer can share a machine that has it with the workspace. Merlin picks the asker's own machine first and a shared one after that.

  7. 07Paste the setup promptGuidanceAn owner or admin sends the prompt below to @Merlin once, and it becomes workspace guidance for every future run.

Prompt

Tell Merlin how to fill in a screen's missing states.

@Merlin from now on, when someone mentions you on an issue and asks for the missing states, find the screen the issue names and add an empty, an error and a loading state wherever it has none. Use our existing components and copy patterns rather than new ones, and open a pull request linked to the issue that lists each state and when it shows. If a state needs a design decision, check how comparable apps handle it on Mobbin and ask on the issue with what you found before writing it.

WEB · design

Once, when you paste it

  1. PromptYou paste the prompt to @Merlin
  2. GuidanceMerlin saves your rules as workspace guidance

Every time someone mentions Merlin on an issue

  1. IntegrationLinear sends Merlin the comment
  2. RuntimeMerlin picks an available machine
  3. ContextThe run gathers context
  4. WorkClaude Code or Codex adds the states
  5. SteeringYour team steers it from the issue
  6. ResultMerlin links the pull request on the issue

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.