◉CLAUDE LABJP
●CC 2.1.330 — Claude Code 2.1.330 fixes the multi-minute freeze right after compacting a long conversation●SONNET 4.5 — Sonnet 4.5 retires from the Claude API on 11/30, 8 days left. The suggested replacement is claude-sonnet-5-5●MCP 401 — Users report MCP servers that return 401 time out silently instead of showing an error●NEW — New: Desktop creates a worktree for every session? Three places to check●OPUS 4.5 — The 11/24 date for Opus 4.5 is a not-sooner-than floor, not a retirement notice●SCHEMA — Same schema, different shape: compare structured output from the Agent SDK and the Messages API●CC 2.1.330 — Claude Code 2.1.330 fixes the multi-minute freeze right after compacting a long conversation●SONNET 4.5 — Sonnet 4.5 retires from the Claude API on 11/30, 8 days left. The suggested replacement is claude-sonnet-5-5●MCP 401 — Users report MCP servers that return 401 time out silently instead of showing an error●NEW — New: Desktop creates a worktree for every session? Three places to check●OPUS 4.5 — The 11/24 date for Opus 4.5 is a not-sooner-than floor, not a retirement notice●SCHEMA — Same schema, different shape: compare structured output from the Agent SDK and the Messages API
Articles/Claude.ai
◉ Claude.ai/2026-06-19Advanced

Pointing Claude Design at Your Codebase: Closing the Design-to-Implementation Loop Solo

The June 17 update lets Claude Design start from your local codebase, so generated assets reflect your existing components. Here is how I wire code-grounded generation into maintaining four sites' UI alone as an indie developer.

Claude Design8Claude Code291design-system4workflow43anthropic12

✦ Premium Article

I have lost count of how many times I re-explained my brand to a design tool. Every time I wanted a new screen mockup, I would restate it: radius is 8px, button height is 44px, primary is this particular purple. The results looked clean, yet they were always slightly off from the components I had already shipped, so I ended up reconciling everything back in code. That rework quietly ate my time.

The Claude Design update that landed on June 17 pulls out one root of that rework. It can now start from a local codebase, and the generated assets reflect elements of your existing product. Design-system import, direct canvas editing, and additional export formats arrived in the same release. It is a beta available on Pro, Max, Team, and Enterprise.

What I cover here is the reverse of the existing Claude Design to Claude Code handoff, which runs design toward implementation. This is the new direction—generating design from code—mapped onto how I maintain Dolice Labs' four sites by myself.

What "starting from code" actually changes

Until now, Claude Design took copy, reference images, or a verbal brand description as input and produced mockups. For better or worse it was a "draw from scratch" tool, and aligning with the existing product was a human job done afterward.

The June 17 update adds four things.

AdditionWhat it enablesWhy it matters solo
Code-grounded generationReads a local repo and reflects existing component shape, spacing, and colorNo more re-explaining the brand
Design-system importTakes your existing token definitions as the source of truthThe per-draft drift disappears
Direct canvas editingEdit output by hand without re-promptingDetail tweaks beat prompt round trips
More export formatsChoose the right export per destinationHand off in the best shape downstream

The first point is the one I feel most. Shipped components act as the de facto brand guide, and the design side conforms to them. It answers the old ambiguity of whether design or implementation is canonical with a single stance: code is the source of truth.

Decide first what to feed it, and what not to

Starting from a codebase does not mean letting it read the whole repo. Claude Lab's frontend is Next.js plus TypeScript, but only a small slice is relevant. The tighter the scope, the less the generated drafts wander.

The three layers I hand over as the starting point are roughly these.

LayerExample pathsRole
Tokenssrc/styles/tokens.css, tailwind.config.tsCanonical color, spacing, radius, type
Base componentsunder src/components/ui/Shape of buttons, cards, inputs
One representative screena single article page.tsxReference for spacing and density

What I withhold is API routes, billing logic, build config, and tests. They contribute nothing to appearance and only scatter the tool's attention. Placing a small scope-declaration file at the repo root keeps the starting point stable.

# DESIGN_CONTEXT.md — declares what Claude Design should read
 
## Canonical (always reference)
- src/styles/tokens.css        … single source of truth for color/spacing/radius/type
- tailwind.config.ts           … token aliases
- src/components/ui/           … Button / Card / Input / Badge implementations
 
## Reference (density hints only)
- src/app/[locale]/articles/[category]/[slug]/page.tsx … one representative screen
 
## Do not read
- src/app/api/                 … irrelevant to appearance
- src/config/pricing.ts        … sensitive, irrelevant to appearance
- **/*.test.ts                 … same

This file is distinct from Claude Code's CLAUDE.md. If CLAUDE.md is the agent's code of conduct, DESIGN_CONTEXT.md is a map of the scenery design generation should look at. Keeping them separate means editing one does not drag in the other.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦If you keep re-explaining your brand to design tools, you'll be able to start from your repo so existing tokens are reflected automatically
✦You'll get a scoping approach for what to feed Claude Design (and what to withhold), plus an import order that makes your design system the source of truth
✦You'll learn why a code-grounded draft hands off to Claude Code without breaking, closing the round trip
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

◉ Claude.ai2026-11-19
When Claude Edits settings.local.json, Let a ConfigChange Hook Record Whether It Took
Claude Code watches its settings files and reloads permission changes mid-session. If the prompt still comes back, here is what to check before restarting, plus a small ConfigChange hook script that logs only added and removed permission rules.
◉ Claude.ai2026-11-17
My Scheduled Job Woke Claude Up Just to Ask Anything New — Multiply Runs per Day by Tokens per Run First
When a recurring job you asked Claude to build drains your weekly allowance early, the culprit is often the runs that only check for changes. A runnable estimator, a non-AI pre-check, and a failure brake that stops the job before it keeps spending.
◉ Claude.ai2026-11-15
When “Browser extension is not connected” Won’t Go Away: Four Layers I Check Before Reinstalling
When Cowork or Claude Code reports “Browser extension is not connected” for Claude in Chrome, here is the order I use to find where it stops: Chrome, the profile, Desktop settings, and the bridge, plus a small macOS check script.