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.
- Starts whenA designer mentions
@Merlinin a comment on the Linear issue that names the screen Merlin worksClaude Code or Codex finds the screen in the code and adds empty, error and loading states with components you already have
- 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
@Merlinin a comment on the Linear issue that names the screen. You don't need to open GitHub.Claude Code or Codex finds the screen in the code and adds an empty, an error and a loading state wherever it has none, with the components and copy patterns you already use.
The pull request is linked on the issue with each state and when it shows. If a state needs a design decision, Merlin asks on the issue, with how comparable apps on Mobbin handle it, instead of guessing.
Mention @Merlin in a comment on the Linear issue that names the screen. You don't need to open GitHub.
Claude Code or Codex finds the screen in the code and adds an empty, an error and a loading state wherever it has none, with the components and copy patterns you already use.
The pull request is linked on the issue with each state and when it shows. If a state needs a design decision, Merlin asks on the issue, with how comparable apps on Mobbin handle it, instead of guessing.
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.
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.
- 01Spot the blank invoices table
- 02File the missing states
- 03Ask which empty state to reuse
- 04Look up how other apps handle it
- 05Wait for an engineer to pick it up
- 06Find the invoices page code
- 07Add an empty state
- 08Handle the failed request
- 09Add a loading skeleton
- 10Fake each state to check it
- 11Open a pull request
- 12Link it on the issue
With Merlin
One comment on the issue gets all three states into a pull request.
@Merlinin a comment on the issueAsked by the designer in LinearAdds the states with your componentsCodex edits the checked-out repository
- 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.
- 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.
- 02Connect LinearIntegrationsOnce you connect your Linear workspace, Merlin can read the linked issue and comment there too.
- 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.
- 04Keep your code on the machineRuntimeMerlin reads the code in a local project on the runtime, so keep the repository checked out there.
- 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.
- 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.
- 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.
Once, when you paste it
- PromptYou paste the prompt to @Merlin
- GuidanceMerlin saves your rules as workspace guidance
Every time someone mentions Merlin on an issue
- IntegrationLinear sends Merlin the comment
- RuntimeMerlin picks an available machine
- ContextThe run gathers context
- WorkClaude Code or Codex adds the states
- SteeringYour team steers it from the issue
- ResultMerlin links the pull request on the issue
Related use cases
More design tasks you can hand to Merlin.
- IntegrationsYour agent's MCP
Design
Check a Figma file is ready for handoff
Mention Merlin on the Linear issue before handoff. It checks the Figma file for missing states, colors that aren't tokens and components engineering doesn't have yet.
@Merlinon the issue with a Figma linkA list of what to fix on the issue - IntegrationsSkillsYour agent's MCP
Design
Ship a UI papercut fix
Delegate a small UI papercut in Linear with its Figma frame. Merlin fixes it with your existing tokens and components and opens a pull request for an engineer to review.
Papercut issue delegated to MerlinA pull request for engineer review - IntegrationsYour agent's MCP
Design
Build a component from a Figma frame
Delegate a Linear issue with a Figma frame to Merlin. You get a pull request with the component built from your existing tokens, states included.
Component issue delegated to MerlinA pull request linked 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.