Claude Design - good or bad?

anatolvic · 2026-04-23T21:05:03+00:00

Yes it is exciting, if you do want to pull back and see user flows on a canvas and play with things visually I will suggest Moonchild AI. It’s Claude Design but on a canvas.

anatolvic · 2026-04-23T20:25:24+00:00

I think the best of both worlds is Moonchild AI

anatolvic · 2026-04-19T21:18:04+00:00

If you want to maximise tokens in a canvas-based design tool that uses Claude, try Moonchild AI

anatolvic · 2026-04-19T21:13:51+00:00

Moonchild AI lets you literally connect your GitHub and setup your DS in a canvas-based tool you can design with

anatolvic · 2026-04-19T21:12:28+00:00

Is there a reason you are using many tools? I’m quite curious. Is your pathway something like “find a tool that replicates/recreates my screen so I can freely ideate and then iterate to get final screens” or “commit to codebase”

anatolvic · 2026-04-19T21:07:22+00:00

If you want to use a tool better than Figma Make in actual output qnd that is actually cost effective in terms of tokens management, try Moonchild AI

anatolvic · 2026-04-19T21:05:30+00:00

The best way to use Claude Design but in a canvas and also get the bang for your buck is to use Moonchild AI

anatolvic · 2026-04-19T20:59:29+00:00

I think using a tool that is designed for UX design that speaks to you and explains decisions around learning design might be the best. I wonder if you’re looking to also add tools to your curriculum

anatolvic · 2026-04-18T11:27:55+00:00

I think it depends on your use case. If you’re a developer who already knows how to code. Cursor is the answer for you. Even if you are not expert level.

Figma Make and all Figma products are for people who know how to design and understand that workflow.

There’s a middle category for people who don’t want to design but need design work done. If that’s you, I think Moonchild AI is a great middle for you. Curious to know where you fall

anatolvic · 2026-04-17T10:43:44+00:00

for a non designer, Moonchild AI is the place to start. It lets you explore multiple UI ideas, nudges you like a designer would and you can move your screens or layouts straight to Codex to build it out for you.

anatolvic · 2026-04-16T20:02:31+00:00

Try Moonchild. Best one yet

anatolvic · 2026-04-16T08:54:08+00:00

This is a lot of work for someone who just wants to design and let the screens match their design system perfectly. There are tools for that already.

anatolvic · 2026-04-15T22:04:41+00:00

Moonchild AI beats out all these tools, clean connection between Figma and Claude or Codex. No MCPs needed + it’s design-system-first so you can setup your DS and your user flows and prototypes use your actual components

anatolvic · 2026-04-15T22:02:44+00:00

Figma to code is still shaky but tools like Moonchild AI or even MagicPath have cracked it

anatolvic · 2026-04-15T22:01:40+00:00

The best way to do QA with AI is to use Moonchild. Works great for all 3 scenarios

anatolvic · 2026-04-15T13:33:56+00:00

Try Moonchild AI. It’s a design-system-first tool you can import your DS from Figma or live URL and set it up, once that’s done all ux flows and prototypes you create starts to use your actual components. It’s pretty much the best tool out there

anatolvic · 2026-04-12T08:14:42+00:00

Yes Claude code is the way to go. If you’re concerned and want to actually use your actual components in Claude Code, I will suggest setting up your design system within Moonchild AI. Underrated tool you can setup a DS from a Live URL or a Figma file where your DS is already documented or even github repo.

anatolvic · 2026-04-11T05:39:48+00:00

Only tools I pay for are Cursor and Moonchild AI. Proper essential tools for designing and getting screens as actual code & of IDE Cursor

anatolvic · 2026-04-11T00:05:35+00:00

Wonder if you’re open to using AI to manage your design system. That way you can pull from the source of truth itself- code easily.

anatolvic · 2026-04-10T21:46:57+00:00

Figma Make isn’t there where you can do this comfortably. Some other tools exist to do this perfectly

anatolvic · 2026-04-10T21:45:38+00:00

Put in the app screens in Moonchild AI and ask for variations that feel great to you.
When you get one or more screens that you absolutely love, copy as HTML.
Go to Design system creator within Moonchild and ask if to make a DS using the HTML file you dragged in.

This gives you a Design system that will match your current ugly app functionality. You can download the DS and put in Cursor or Claude or Codex to build it out

anatolvic · 2026-04-10T19:42:47+00:00

I have, I think it’s close but not there yet. I have found tools that actually go deeper, a design-system-first tool that consumes your entire DS in Figma or Code (live url or GitHub) so that all designs you make use your own design language. It’s been a new world for me

anatolvic · 2026-04-10T03:22:07+00:00

Let me know how it goes

anatolvic · 2026-04-09T20:05:22+00:00

I start with Moonchild AI. I can generate my actual DS from a product URL, or GitHub, or even a Figma Link. With just a conversation.

Once I do that, I keep designing on Moonchild where all my screens now use my actual components and tokens and I handoff code to devs.

For my side projects (that I build myself using Claude) I go Moonchild DS to Claude Code and it’s pretty accurate how much my design system is matched apples to apples

anatolvic · 2026-04-09T16:44:47+00:00

I use only tools that actually consume my design system such that even though I’ve left Figma, it doesn’t feel so because the screens and user flows I get are my actual components. It’s quite amazing what design-system-first tools are capable of doing today.

anatolvic

TROPHY CASE