I Used Claude Design on Day 2. Here's What Web Designers Should Know.

Anthropic launched Claude Design two days ago. I spent day two putting it through a real test — an hour-long session where I asked it to generate design artifacts for a working business with a real codebase and an existing brand.

This is an honest field report. Not a hype piece, not a doom piece. What worked, what didn't, and what I think it means for web designers going forward.

What is Claude Design

Claude Design is a new product from Anthropic Labs, powered by Opus 4.7. You describe what you want, it generates visual output — prototypes, slide decks, one-pagers, design system artifacts. It reads your codebase and existing design files to maintain consistency.

Available to paid Claude subscribers at claude.ai/design.

The Test

I'm an indie product builder. I wanted to see how far Claude Design could go when handed inputs typical of a real engagement:

- A repo with existing code

- A brand logo (a gradient geometric mark)

- A paragraph of brand voice (dark-first palette, OKLCH colors, tight typography)

Then I asked it to produce production-grade marketing artifacts.

What It Generated

In one conversational session, it produced:

1. A complete design system CSS file — brand colors (hex + OKLCH), dark/light semantic tokens, gradients, shadows, radii, spacing scale, and typography preset classes.

2. **17 preview HTML cards** covering every token and component category (colors, type scales, components, utilities).

3. **A React UI kit** recreating a marketing site — 10+ `.jsx` files with components, inline Lucide icons, and an interactive demo.

4. **A set of 1280x720 cover-image HTML files**, each with a distinct accent gradient but sharing a unified layout system.

Because I asked for code, each of these landed as text files — HTML, CSS, JSX, Markdown — that I could read and edit. (If I'd asked for images or PNGs, it would have produced those instead.)

The Good Part: It Really Did Get Easier

Let me be specific about what "easier" means here, because it's the real story.

The workflow is conversational, not point-and-click

The biggest shift from Figma or Canva. I didn't drag rectangles or manipulate layers. I wrote:

> "Create a cover image with a browser mockup of a landing page on the right and title + price on the left."

And it generated that. When I wanted changes, I described them in English:

> "The logo in the output is wrong — here's the correct one."

Fixed. No layer inspector, no components panel, no constraint editor. Just description.

When you ask for code, you get code

Ask for HTML, CSS, or JSX and Claude Design outputs exactly that — version-controllable text, not a proprietary design file. You can `git add` a session's output directly. (PNG export is also there when you ask for it — but the default for code-oriented prompts is working code.)

A beginner can ship something decent with this alone

This is the part I want to be loud about. If you have an idea and zero design background, you can now produce a coherent-looking landing page, a usable color system, and marketing covers in one afternoon. "I'm not a designer" is no longer an acceptable excuse for shipping ugly things.

For a hobby project, a side hustle MVP, or a quick pitch deck, **Claude Design alone is enough**. Really.

The Honest Part: "Decent" and "Great" Are Different Tiers

Here's the thing people won't tell you in the launch-week hype.

Claude Design hands you a **solid baseline** in minutes. But the gap between "solid baseline" and "actually good" still costs knowledge, taste, and iteration — and AI can't skip that for you.

Where the baseline falls short

- **First-pass outputs drift.** Three or four iterations were normal — wrong asset pulled from the repo, proportions slightly off, spacing rhythm inconsistent between screens. If you don't *see* the drift, you ship it.

- **Fine control is harder than big direction.** "Apply a subtle mesh gradient with grain overlay" works instantly. Dialing in exact grain intensity so it reads as texture instead of noise? I dropped into the CSS myself.

- **It has no taste about your taste.** It matches *a* plausible style guide given your inputs. Whether that's the *right* style for your audience, your positioning, your category — it can't tell you. Only you can.

- **Systems thinking is still yours.** AI happily generates ten cover variations. Deciding which three ship, what the naming convention is, how this scales to the next twenty covers — that's a systems problem, not a generation problem.

The knowledge that still pays off

If you actually want output that looks *considered* rather than just *competent*, you still need to know things like:

- Why this spacing scale and not a different one

- When a gradient reads as premium vs. when it reads as dated

- How type contrast actually works (not just "bigger + bolder")

- What a design system's job is beyond "list of colors"

- How to read a layout and diagnose *why* it feels off

Nothing about Claude Design changes that. It just makes the generation step cheap, so **the knowledge-shaped bottleneck shows up earlier and more visibly**.

What This Means for Different People

If you're a beginner or non-designer

Great news. The floor just rose dramatically. You can ship things that don't look embarrassing, without six months of design study first. Use it.

Just don't confuse "no longer embarrassing" with "great." If your goal is something that resonates beyond "acceptable," you'll still hit a ceiling that only design knowledge removes.

If you're a working designer

Your execution speed is no longer the thing that makes you valuable. Anyone with a prompt can generate variations now. What compounds is:

- **Judgment** — which of the ten outputs ships

- **Direction** — what should be made in the first place

- **Craft at the edges** — the 20% of polish AI won't reach by default

- **Systems** — turning one-off artifacts into reusable, consistent work

These are all things AI accelerates your process around, not things it replaces.

If you're a design system maintainer

Probably the biggest shift. Claude Design reads your codebase and generates artifacts that match your existing tokens. Grunt work — refreshing preview pages, recreating examples, documenting new components — becomes near-free. The human role concentrates on defining principles and reviewing output for consistency.

What To Actually Do

**Don't panic, don't dismiss.** "AI will kill design" and "AI is just a toy" are both wrong for the same reason — they skip the part where *how* you use it decides the outcome.

**Learn prompt craft, but don't stop there.** Describing visual work precisely is a real skill. But a great prompt without design knowledge still produces mediocre design faster. Prompt craft is a multiplier; knowledge is the base number.

**Keep studying the fundamentals.** Type, hierarchy, rhythm, color, systems. The floor went up — so the relative value of being *above* the floor went up too.

**Integrate it, don't fight it.** Use AI for first drafts, exploration, system documentation, mundane asset generation. Reserve your focus for decisions and polish that actually need you.

The Honest Bottom Line

Claude Design makes "decent output" trivially easy. That's a big deal — a beginner can ship something they'd have been embarrassed to ship a year ago.

But "decent" and "great" are still different tiers, and the gap between them is still paid in knowledge and judgment. AI shrinks the distance from "idea" to "baseline." It doesn't shrink the distance from "baseline" to "considered, intentional, well-crafted work."

Which, honestly, is the best possible outcome. The boring part got cheap. The interesting part — knowing what's worth making, and making it well — is still where humans live.

---

Looking for hand-crafted, production-ready Next.js templates with careful attention to detail? Take a look at [Craftly](https://getcraftly.gumroad.com) — Tailwind v4 native, Next.js 16.2, TypeScript strict. Real code, carefully built.