Exactly How to Set Up Claude Design So It Works For You

Exactly How to Set Up Claude Design So It Works for You — From a Snobby Designer’s Perspective

Okay, so — I built a design system for a client last week and about halfway through I thought, I should just record this whole thing start to finish. I had two design systems open at once too, mostly because I was curious how that was even going to go. (Spoiler: it works. More on that below.)

The short version

• It’s never going to be perfect on the first try. Not even close.
• Feed it everything you’ve got — fonts, logos, screenshots, old PDFs, decks, brochures. Order doesn’t matter at all.
• Don’t stop at fonts and logos — feed it your positioning, voice guidelines, and proof bank too. That’s what makes what it builds later actually sound like you (or your client).
• Uploading a big photo library? Point it at the folder instead of attaching files one by one, or Claude Design will cap you out.
• Click Design Systems, not Projects, when you’re building your system. I didn’t, and it cost me.
• While your system’s building, you can chat or work in another window — that’s the real multitasking win here, not running two systems at once.
• Plan on a real afternoon your first time. There’s a lot of waiting built in.
• Once you’re generating actual designs, you need your own system for keeping them organized. Claude Design won’t do it for you.

Nobody’s first output is good

It’s never going to be perfect on the first try. If you’re staring at round one thinking you did something wrong, that’s literally me two weeks ago —so zero judgement here.

The hype out there makes it look like you type one sentence and a finished brand falls out. My own IG stories have probably sold that fantasy too, not gonna lie. It doesn’t work like that. The way I actually get good output out of Claude Design is ten bajillion iterations and a few years of nerding out in AI Land before any of this came along.

Design sense still matters, a lot. It’s less about reading every label on the page correctly and more about the gut check: does this look and feel like the brand? Do the fonts feel right? Does it flow the way you want it to?

Case in point — the first version of one design system I ran came back looking super corporate. Technically had the right brand colors and everything. But it felt like it had gone through a hundred-step game of telephone before it reached me. Brutal. I’m still hunting for the screenshot — if I find it, it’s getting bolted onto this post as a warning label. (I will find it. This is a promise to myself as much as to you.)

Here’s what actually worries me a little: if everybody’s just quickly cranking out design systems, everything’s going to start looking like Anthropic / Claude’s own aesthetic. So, hot tip: make your brand look and feel different right off the hop. (As gorgeous as their stuff is!)

Knowing what you love, and shaping it into something memorable, is a real skill. I’ve got an old Instagram inspo folder I’ve been dumping into forever — most of it dead weight from 2019 — but every design system I build, I go digging through it for two or three things that still feel like the brand and ask Claude to tack them on. That folder does more work than any prompt I write.

Feed it everything, not just the “official” stuff

Onwards — here’s what I look for: fonts, logos, screenshots of everything the client’s already put out into the world, PDFs, brochures, old decks. Order doesn’t matter — just dump it all in.

Grabbing all of it feels like a job a robot could do. Click download, click download, click download, kind of useless work. But here’s the thing: you only have to do it once. After that it’s just pulling automatically, forever. It’s freakin’ magic.

Your fonts, logos, and brand photos are almost always sitting right there on your own website, organized hard drive or not. (Mine sure isn’t, ha.) I try not to hold onto files longer than I need to. If I’m not gonna use it, it gets archived or trashed — it already lives on the internet somewhere anyway. Keeps my desktop from turning into an actual landfill.

One practical heads up: if you try to dump in a big folder of photos at once — I had an actual library of 300 — Claude Design will tell you no, that’s too much. Don’t panic. Point it at the specific folder on your computer instead of attaching every file one by one, and it’ll pull out what it actually needs. Way less painful than it sounds.

Feed it your actual voice too

This is the tip most people skip, and I think it matters the most: while you’re in there, pull in your actual project files too, not just fonts and logos.

Positioning. Voice guidelines. Proof bank. Whatever you’ve already built out.

I ran a batch of these into a design system recently, and the difference showed up downstream. When I asked it to generate social content off that same system afterward, it actually sounded like the client instead of a stand-in that could’ve been anyone. What you put into the design system isn’t just visual — it’s teaching everything built off it how to talk, too.

One caveat: there’s a limit to how much you can experiment with this before it gets a little garbled. Too much input at once and it all bogs down instead of sharpening up. Add in layers, not all at once.

Click Design Systems, not Projects

I learned this one the hard way — when you open Claude Design, go to Design Systems, not Projects, if you’re building one.

I just hopped into Projects on my first try and had to spend fifteen minutes trying to cobble it back together for the actual system. (I know I said “actual” there.) Rookie move.

Running more than one window

Most people aren’t going to be building more than one full design system at a time — that part’s rare. But while your system is building, you can hop over to regular Claude chat and get something else done. That’s the real multitasking win, and it’s genuinely useful dead time instead of confusing dead time.

Where multiple windows come in handy is later, once your system already exists. If you want to generate two separate projects or design directions off it, that’s when a second window makes sense.

Trying to build two systems from scratch at the same time, though? That’s a special kind of chaos. Open multiple tabs with caution. (My poor brain — sooo many open tabs lately!)

How long this should take

Plan on a real afternoon, not five minutes. There’s a lot of waiting built in between rounds — real dead time, enough that I keep a stack of books on my desk specifically for this.

Read a chapter. Learn to French braid. Do a mini workout in your office. Anything except hunching over your desk like a Claude goblin the entire time.

I’ve built a handful of Claude Design Systems now, and a good one still took me a full evening yesterday. Call it two to three hours, mostly in fits and starts.

Okay, you’ve built the system — now actually use it

Building the system is one job. Generating actual designs with it is a different one — that’s what happens next, inside Projects.

(Story time: I’ve got one from yesterday — a simple prompt that turned into SUUUUCH great output on the first try. Dropping it in here. Pardon my giant face if you’re on desktop.)

That’s the fun part. It’s also where the mess starts.

The part I haven’t solved yet

So: you build the system, then you start generating designs off it, and pretty soon your Projects file turns into an giant mess. Maybe that’s fine if it’s just you.

But if you’re doing client work in here, you need everything organized and findable. Figure out an actual system: label everything with the client name, favourite the ones that are ready to roll, throw an asterisk on the ones that just need one more round of revisions. That’s what we’re doing. You do you, just pick something and stick to it.

I’m still debating whether Cowork should run a weekly export on top of that — something that takes whatever’s sitting in your Projects folder and organizes it onto your hard drive or cloud storage by client, then date, then use case, so you can actually find the thing you drafted seven months from now.

Whether it should also clean out Claude Design itself once it’s exported, I’m torn on. Having the editable files sitting right there is really useful, and I don’t want to lose that by being too aggressive about tidying up! So for now, we’re just trying to keep it organized with proper naming and archiving and crossing our fingers that Claude comes up with something soon.

One thing I stole from this for content in general

We’re getting a little distracted here, but we all have monkey brains, so here’s something useful: if you’re trying to teach something, just record yourself doing it. What you’ve got is fine as-is, or go back and trim it if you want — doesn’t matter if there’s a twenty-minute gap in the middle where you wandered off to do something else. That messy, unedited, stream-of-consciousness version of you working through it is some of the best raw material you’ll get for anything you write after.

This post took about 30 minutes to write. In the middle of that 30 minutes I also forgot what I was working on, responded to a pile of IG messages, tested a new tool I built to help people set up their own Claude, and created three post templates inside a client’s design system. Also kissed my husband good morning and finished a cup of coffee.

So — solid half hour. In 2024, this post would’ve taken me at least half a day with a lot less life happening in between. AMAZINNNNG!!

Who this is for

This is for any small business owner poking around Claude Design for the first time, not a design team that already has a system dialed in. If that’s you: plan on a real afternoon, and don’t expect the first version to look like something you’d actually use. The good version’s a few rounds off, not one click away.

Once you’re feeding it well, it gets good — like, better-designer-than-me good, with the right instructions. So don’t be shy about going back in over and over. Iterate, iterate, iterate — just synthesize as you go so it doesn’t turn into input soup.

One honest caveat before you go build your own: none of this is set-it-and-forget-it. I’m planning on regular maintenance on mine, not a one-and-done setup. And since we’re talking about a tool that’s still in beta, there’s a decent chance something in this post is already a little out of date by the time you’re reading it — a button that moved, a limit that changed, whatever. The click order might shift under you. The principles underneath it won’t.

Whether this turns into something we build for clients directly, I’m still working that out — right now it’s just how I get my own stuff done. If you want it done for you, well… you know where to find me.

FAQ

Do I need design experience to use Claude Design? No, but it helps. You don’t need to know design software, but you do need to know what “good” looks like when you see it — that’s what lets you push back on a rough first draft instead of settling for it.

How long does it take to build a design system in Claude Design? Plan on a real afternoon your first time, not five minutes. Most of that is fine-tuning across a few rounds, plus real waiting time while things render.

What’s the difference between “Design Systems” and “Projects” in Claude Design? Design Systems is where you build out your fonts, colors, logos, and components. Projects is where you generate actual designs using that system. Mixing them up early on will cost you real time — ask me how I know.

Can I upload a large photo library to Claude Design? Not all at once — there’s a cap. Point Claude at the folder on your computer instead of attaching hundreds of files individually, and it’ll pull what it needs from there.

Can I have more than one Claude Design window open at the same time? Yes — click into a design from your Claude Home and it opens in its own window. It’s most useful once you’ve already got a system built and want to generate a couple of design directions off it. Building two systems from scratch at the same time gets confusing fast.

Will Claude Design keep my projects organized automatically? Not yet. Once you’re generating a lot of designs, you need your own system for labeling and organizing them — by client name, favouriting the ones that are ready, flagging the ones that need another round.

---

Liked this? I send a short email every couple of weeks — one real story (recent lowlights include becoming a certified Claude goblin, hunched over a laptop for three straight hours) plus one useful thing about your website or marketing. Never longer than your coffee. [Come hang out →]