Meaghan Choi
Design Lead for Claude Code at Anthropic.
Meaghan Choi did not write this page. ppll compiled it from their own words, each linked to the source. Is this you? · Report a mistake
What they believe
-
Knowing when to use AI tools for execution and when to go deep on the thinking work is a skill, and quality and polish do not have to take all of a designer's time.
it doesn't have to be all of your time. And so knowing when to use these tools for execution and offload and knowing when you need to go deep and do the thinky work is a skill set. And I think that's one that I see people doing wrong.
youtube.comSaid 8 Jul 2026This on korrents
The bold line is korrents’ wording; the quote is theirs. These one: what they wrote before what they said aloud, one per source, newest first.
Beliefs
Korrents What they believe 20 beliefs — each backed by an exact quote.
Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.
Recent
Knowing when to use AI tools for execution and when to go deep on the thinking work is a skill, and quality and polish do not have to take all of a designer's time.
it doesn't have to be all of your time. And so knowing when to use these tools for execution and offload and knowing when you need to go deep and do the thinky work is a skill set. And I think that's one that I see people doing wrong.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
People often ask Claude to execute when they should be asking it for the early thinking, because today it is not good at telling you an idea is wrong and just executes what it is asked.
you might be asking Claude to do execution when you you should actually be asking Claude to do the early thinking. The execution is wrong. Like the shape of the execution is incorrect. And Claude is not good today at telling you if your idea is wrong, it'll just execute on the thing that you ask it to do.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Developers expect a CLI to be extraordinarily information dense, showing more than a graphical interface would, because a CLI has no progressive disclosure.
Because you're serving developers, they have very specific expectations with the CLI actually that you want it to be extraordinarily information dense. Like you would show more in a CLI than you would ever probably show in like a guey, like a graphical interface, because there's no such thing as progressive disclosure.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Show 17 more
The invisible thinking behind a product, the mental model, the interaction model and the base primitives, has long been the unsung hero of product designers.
the invisible thinking that goes behind building a product. That's one that I think I expect and hire for at Anthropic and I think has been the long unsung hero of product designers everywhere is like the mental model, the interaction model, like the base primitives that compose how you think about what you're interacting with.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
In a terminal, keyboard shortcuts are massive, because they are the primary way of interacting.
keyboard shortcuts are massive. I would say like there are power tools like Figma and other places where they do consider keyboard heavier but like the primary way you interact with a terminal is keyboard shortcuts.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
It is really important that people feel a little bit of warmth from AI tools, and they should not be super detached from them.
I think it's really important that you feel a little bit of warmth from these tools. You don't want to be super super detached from them.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
The aim is to avoid inventing new UI and to make a tool feel so natural that it becomes part of the workflow.
The UI part of itself is extremely simple because in my goal, we're trying not to invent new UI. We want it to feel so natural that it just becomes intrinsically part of your workflow.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Work on the user model, relationship and behavior is the really important design thinking, while design polish pieces are really easy to offload.
Those are the really important pieces that we spend a lot of time thinking on that we won't offload because it's about the user model relationship and behavior and like these design polish pieces or some of these updated ones are like really easy ones to offload.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
When what is being tested is the underlying mental model, it is probably not worth polishing, because the thing might not make sense; knowing when craft and polish are needed is important.
sometimes knowing when it needs that craft and polish or knowing when just the shape of it is actually what you're trying to test is really important. And so you might launch something or test something that looks terrible, but what you're actually testing is the underlying mental model of the shape of product. And I don't think it's worth polishing that thing actually because it might not even make sense.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Experimenting with mental models does not require high craft and is better done at speed, in the open, in iteration than by polishing something that is the wrong shape.
that experimentation of mental models doesn't require that high of craft and it's better done actually in speed in the open in iteration as opposed to spending a lot of time polishing something that's actually the wrong full wrong shape
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Sharing responsibility for quality, educating and delegating rather than gatekeeping, helps engineers and product partners feel they own it too.
I tend to find the more we can share responsibility of what we think quality looks like in our product and not be the gatekeepers but educate and kind of delegate around us so that both our engineers and product partners feel that quality is something that they own and drive too.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Quality has never been only design's responsibility, and the most successful organizations feel it is owned by everybody.
I don't think and it never has been historically only design's responsibility to mean quality the most successful organizations feel like it's owned by everybody
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Designers should define quality and share it as a workflow anyone on the team can use, in a way that is additive, teaching and guiding rather than stopping.
invest in like how you define your quality and how you uplevel it and then share that as a workflow that anyone on your team can use and don't do it to stop them. Although it is important to know when to stop and hold the bar, but try and do it in a way that like is additive and is teaching and guiding rather than stopping.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
There is probably still going to be a need for a lot of fixed interfaces, because much of a product needs to be reliably stable, like a login screen or billing settings.
we're still going to need a lot of fixed interfaces. So there's two concepts now that UI can fall into. There's fixed and then there's like adaptive or like non-deterministic is kind of and I think there's just so much that needs to be reliably stable that you don't want to relearn and you don't want to be dynamic like a login screen, billing settings
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Deciding what should be fixed and what adaptive is an important design decision; people often assume everything should be customized, but a lot of people do not want that.
Knowing what should be fixed and what should be adaptive or dynamic is a really important decision for you as a designer to make as you're designing these features because I think often people will assume that everything should be customized because it can. I'm very much of the opinion that a lot of people don't want everything to be customized.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Just because something can be built as a function does not mean it needs to be, and adding it brings a lot of product bloat and complexity.
Just because it can build and just because it can be a function doesn't mean it needs to be. It adds a lot of product bloat. It makes it very complex.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
In terms of full functionality, things can be a little simpler than they are now; not every idea is good or necessary, and sometimes adding it is worse.
in terms of like full functionality, things can be a little bit simpler than they are right now. And not every idea is good or necessary. Sometimes adding it is worse.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Being very open-minded and curious is really useful in the emergent phase of this technology: hold opinions, develop them, and be willing to let go and update.
Being very open-minded and curious, I think is really useful. Like hold your opinions, develop them, and then be willing to let go and update how you think about things.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Designers should lean into the chaos, develop new ways of working and continuously update, rather than cling to a structured process.
design used to be so structured and processed that it feels like you really want to cling to that. But I'm urging people to do the opposite which is like lean into the chaos, develop new ways of working and like continuously update.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
Discernment about what should be built, and how to build it for the product, is the core builder process right now.
But I think discernment on what should be built, how to best build it in a way that suits your product and what you're trying to express and what role you should play in building it and where that craft should fall is like a big one. Like that's the core builder process right now.
Meaghan Choi - Designing Claude Code (and what's coming next) Said 8 Jul 2026
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
Where they publish
x.com @meaghaneschoi Short posts on designers working in code with Claude Code.
Posts about how Anthropic's designers prototype and ship production code with Claude Code, talks she gave on bridging the design and dev gap, and ideas for sub-agents such as a design reviewer and an accessibility checker. Profile bio reads “design @claudeai”.
Link verified 4 Oct 2026.
Interviews As a guest Long-form interviews on other people’s channels, chosen and not exhaustive.
Her own voice by her own participation: Dive Club’s conversation on designing Claude Code's terminal UX, Artifacts and Claude Tag, when she still uses Figma, and the new shape of designer.
Link verified 4 Oct 2026.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.