u/bodyakrol

UI copy is one of those tasks that looks small on a task list and quietly eats hours per feature.

I built a UX copywriting skill in Claude.
It connects to Figma via MCP.
And it writes copy directly into my Figma files.

I don't think about text upfront anymore.
I build rough flows with dummy data and send the flow to Claude.It handles the rest in one prompt.

Before: open a screen, think about the heading, write it, move to the next screen. Repeat for every CTA, every error message, every label in the flow.

Now: one prompt and AI will write UI copy for selected flow.

The goal is to spend less time on copy and more time on actual design decisions.

Question:
Has anyone else tried automating the copy layer in their design workflow? Curious what's working.

A good CTA should read naturally as a pair with the section title. Not as a standalone phrase, but as a logical continuation of what the title is already saying. And at the same time it has to encourage the user to act.

This is one method that can help with that. Not a replacement for other approaches, but a useful addition.

How it works:
1. Start a new chat and give AI this instruction: “I will describe a situation or task. You respond with a single short action phrase (2-3 words max) — what a real person would actually do first.”
2. Then write: “I need + [your section title]”
3. AI responds with one phrase. If you need more options, just write “5+” and it will give you a list to choose from.

It won’t always be perfect, but it tends to be more natural than brainstorming labels in isolation.

Has anyone tried something similar? Curious if there are other prompting approaches for microcopy.

I started using Mobbin's MCP integration with Claude about a week ago and it's become a natural part of how I work. Here are the use cases that actually proved useful, because it's not just "search for UI inspiration."

1. Understanding how other products use secondary colors in their design systems
I was trying to figure out the logic behind secondary color usage. Not just visually, but how products apply it consistently across states and components. Mobbin + Claude let me pull real examples and analyze the pattern without switching between tools constantly.

2. Layout inspiration with context
This one surprised me. If you have an ongoing chat with enough context about what you're building, Claude can search Mobbin for relevant layouts on your behalf. It's not generic inspiration. It's filtered by what you're actually working on.

3. Comparing and validating design decisions
When I'm unsure about a solution, I'll ask Claude to find examples of how other products handle the same problem. Comparing to others shouldn't be the main argument for a design decision, but it's a useful signal. Either your solution matches successful products, which gives you some confidence, or nobody's doing it your way, which forces you to think harder about why.

Has anyone else been using Mobbin MCP? Curious what other use cases people have found.