korrents
Nate Parrott

What Nate Parrott thinks about Anthropic

@nate-parrott · 19 positions · 0 changes of mind

Designer at Anthropic who started Claude Design; earlier a founding designer at The Browser Company.

Everything they publish, on ppll ↗

Nate Parrott did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

5 dated positions, 2026, in their own words. Our reading of what Nate Parrott has said — not written or endorsed by them.

  1. Our readingEvery designer should use Claude Code if part of the team's end product is code, because it beats going back and forth with an engineer.

    patiencedesign

    Their wordsevery designer should be using cloud code if part of your team's end product is coding if only because it's so much easier than going back and forth with an engineer and like bugging them to make changes and hoping they have the patience to wait and get it right.

    ↗Nate Parrott - How a Side Project Became Claude Designyoutube.com 4th of 19 in this recording

  3. Our readingDesigners should code and ship, and a tool like Claude Design is for everything else, such as communicating an idea.

    design

    Their wordsthe way that I've drawn the line is by saying that designers should code designers should ship and claw design is for everything else. Cloud design is for when you want to communicate an idea.

    ↗Nate Parrott - How a Side Project Became Claude Designyoutube.com 10th of 19 in this recording

  5. Our readingDon't ask Claude for a design without context: give it as much context as you can, be prescriptive, and don't trust it to be an amazing designer on its own.

    design

    Their wordsdon't just ask Claude to like make you a design without giving it any context. Give it as much context as you can. And ideally be pretty prescriptive about what you want to get out and let Claude do the hard work of mocking it up and coding it. But like don't trust Claude to be an amazing designer and do all the work for you.

    ↗Nate Parrott - How a Side Project Became Claude Designyoutube.com 15th of 19 in this recording

  7. Our readingWhere Claude is weak, as with animation timing, ask it to build you a tool so you can dial it in yourself.

    Their wordsAsk for tweaks, especially in areas where you see Claude is not very good at figuring it out right off the bat. So, for example, if you're trying to make animations or you're trying to make really dialed in visual interactions, Claude is not very great at doing things like timing or figuring out things like spring parameters or animations because it can't see video. It can only see screenshots. So, instead, if you're finding that Claude is having a lot of trouble at that, say, "Hey, Claude, make me a tool so that I can dial this in myself.

    ↗Nate Parrott - How a Side Project Became Claude Designyoutube.com 16th of 19 in this recording

  9. Our readingVoice is the best way to give Claude much more context faster, and it gives better results.

    Their wordsUse voice. I'm a huge voice fan. Uh, this sort of goes along with the rule that you get out what you put in. If you give yourself the self the tools to give Claude much more context faster and voice is the best way to do that. I found you will get much better results and you'll just have a better time.

    ↗Nate Parrott - How a Side Project Became Claude Designyoutube.com 17th of 19 in this recording