惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - Franky
C
CXSECURITY Database RSS Feed - CXSecurity.com
S
Schneier on Security
Know Your Adversary
Know Your Adversary
Security Latest
Security Latest
Spread Privacy
Spread Privacy
Project Zero
Project Zero
T
The Exploit Database - CXSecurity.com
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
AI
AI
N
News | PayPal Newsroom
A
Arctic Wolf
NISL@THU
NISL@THU
W
WeLiveSecurity
Security Archives - TechRepublic
Security Archives - TechRepublic
Hacker News: Ask HN
Hacker News: Ask HN
P
Palo Alto Networks Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
大猫的无限游戏
大猫的无限游戏
L
Lohrmann on Cybersecurity
Last Week in AI
Last Week in AI
T
Threatpost
The Last Watchdog
The Last Watchdog
博客园_首页
C
Cybersecurity and Infrastructure Security Agency CISA
酷 壳 – CoolShell
酷 壳 – CoolShell
量子位
Engineering at Meta
Engineering at Meta
爱范儿
爱范儿
aimingoo的专栏
aimingoo的专栏
S
Security Affairs
P
Privacy & Cybersecurity Law Blog
B
Blog RSS Feed
AWS News Blog
AWS News Blog
P
Proofpoint News Feed
雷峰网
雷峰网
T
Tenable Blog
Schneier on Security
Schneier on Security
H
Heimdal Security Blog
V2EX - 技术
V2EX - 技术
V
V2EX
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Secure Thoughts
Latest news
Latest news
Help Net Security
Help Net Security
Jina AI
Jina AI
Stack Overflow Blog
Stack Overflow Blog
The Cloudflare Blog
V
Vulnerabilities – Threatpost
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org

Open Design Blog

Best AI Design Agents in 2026: An Honest, Tested Guide Best AI Prototyping Tools in 2026: An Honest, Tested Guide Best AI Design Tools in 2026: An Honest, Tested Guide Best Bolt.new Alternatives in 2026: An Honest Comparison Best Design-to-Code Tools in 2026: An Honest, Tested Guide Best Figma Alternatives in 2026: An Honest, Tested Guide How to Use Claude Code for Frontend Design (2026 Guide) Best Lovable Alternatives in 2026: An Honest Comparison Best v0 Alternatives in 2026: An Honest Comparison Open Design is coming to Osaka / Kyoto Open Design 0.12.0: your brand is a design system Vibe Design Tools: An Honest Guide to What Works Vibe Design vs Vibe Coding: Where They Split and Why It Matters Vibe Design with Google Stitch: What It Nails, Where It Traps You What Is Vibe Design? The 2026 Guide to Designing by Intent Open Design 0.11.0: the Bazaar Open Design 0.10.0: the all-in-one design workspace Open Design 0.9.0: design for everyone The open-source alternative to Figma Open Design 0.8.0: everything is a plugin The layout layer the canvas used to hide How to port a Figma workflow into an Open Design plugin BYOK reality check: 5 things that break in Open Design today 31 skills, 72 systems: how the Open Design library works BYOK design workflow: run Claude, Codex, or Qwen on your own key Why we built Open Design as a skill layer, not a product
The open-source alternative to Claude Design
Open Design · 2026-05-14 · via Open Design Blog

Claude Design is good. It's also closed-source, hosted-only, and bundled with a Claude subscription. Here's the honest read on when to pick it — and when the open-source path wins.

Claude Design is good. We’ve used it on real briefs. The fact that we built an open-source layer instead isn’t because Anthropic shipped a bad tool — they didn’t. It’s because closed-source, hosted-only, $20-to-$200-a-month design tooling is the wrong shape for the next decade of design work. This post is the honest read on Claude Design from a team that ships in the same category: what it is, where it locks you in, what the open-source alternative actually looks like, and which one you should pick this quarter.

What Claude Design actually is

Claude Design launched out of Anthropic Labs in April 2026. It’s a conversational design tool powered by Claude Opus 4.7: chat on the left, canvas on the right. You describe what you want, Claude generates a design, and you iterate through comments, inline edits, and prompt refinements.

It does four things well:

  • Prototypes from prose. Onboarding flows, settings pages, admin panels, checkout variants — five minutes from prompt to interactive screen.
  • Codebase awareness. Import a GitHub repo or attach a local directory and the prototypes use your real components, your token system, your conventions.
  • Brand integration. Set up a design system once and every project automatically picks up the colors, typography, and component patterns.
  • Handoff to Claude Code. The “build this” button takes the prototype to production-ready code in the same browser tab.

Exports include Canva, PDF, PPTX, HTML, and standalone URLs. Pricing is bundled — Claude Pro at $20, Max at $100–$200, Enterprise at the usual call-us tier. It’s currently a research preview for paying Claude subscribers.

If you read the official tutorial, the workflow Anthropic describes is the same one Open Design ships: a brief, a direction, an artifact, a handoff. The differences live one layer down.

Where it locks you in

Claude Design carries four pieces of lock-in worth naming upfront, because the marketing pages don’t.

The model is fixed. Every render goes through Claude. Not Claude or a model you’ve already paid for — just Claude. If your team has a contract with GPT, Gemini, or DeepSeek, or if you self-host on Ollama for sensitive briefs, those workflows don’t translate. Token cost rides Anthropic’s pricing curve forever.

The runtime is hosted. Your prompts, your design system, and your codebase context all travel to Anthropic’s servers. For agency work or pre-launch creative under NDA, that’s a procurement conversation every time. Self-hosted is not an option in the research preview, and the announcement does not commit to one.

The skills are not yours. Claude Design’s behaviour is defined by prompts and tools that live inside Anthropic. You can’t fork them, audit them, or replace one. The “skills” Anthropic is shipping in Claude Skills are adjacent but separate; the design-specific tooling is internal.

The bill is a subscription. $20–$200/month per seat is fine for a solo designer, painful for a team of twenty, and a non-starter for the dozen open-source contributors who would otherwise pick up the same workflow.

None of these are bugs in Claude Design. They are the shape of a hosted product. Anthropic optimised for the median Pro subscriber. We’re not the median Pro subscriber.

A black faceted cloud solid tethered by a dashed line to a small ground anchor and server block, on a warm editorial study plate
Hosted by default: your prompts, design system, and codebase context travel to someone else's servers.

The open-source alternative

Open Design (this site) is a different bet. It’s not a Claude Design clone — it’s a thin skill layer that turns the coding agent you already use into a design engine. The four primitives are skills, systems, adapters, and the daemon. Every skill is a SKILL.md file. Every design system is a DESIGN.md file. Every agent adapter is ~80 lines of TypeScript.

What ships in the box today:

  • 123 skills — deck generators, mobile mockups, editorial pages, Word/Excel/PPT, brand explorations
  • 148 design systems — portable Markdown versions of Linear, Vercel, Stripe, Apple, Cursor, Figma, plus a long tail
  • 16 coding-agent CLIs auto-detected on your $PATH — Claude Code, Codex, Cursor, Gemini, OpenCode, Copilot, Devin, Hermes, Pi, Kimi, Kiro, Qwen, DeepSeek TUI, Qoder, Mistral Vibe, Kilo
  • Four-step locked workflow — question form → direction picker → live plan stream → sandboxed iframe preview
  • BYOK by default — paste any OpenAI-compatible base_url and key, your tokens go straight to the provider
  • Apache-2.0, no signup, runs on pnpm tools-dev

The mental model: Claude Design is a product. Open Design is a layer.

Three black faceted polyhedra on a measured baseline, only one slotted into a bracket frame while the others sit loose, on a warm editorial study plate
Claude Design fixes the model. The open path lets you bring the one you already pay for.

Side-by-side

Claude DesignOpen Design
LicenseProprietaryApache-2.0
RuntimeHosted (Anthropic)Local daemon (pnpm tools-dev) + optional Vercel deploy
ModelsClaude onlyAny OpenAI-compatible endpoint + 16 detected CLIs
SkillsInternal123 forkable SKILL.md folders
Design systemsPer-project brand setup148 portable DESIGN.md files
Codebase contextGitHub import + localSkill-level, real working directory
Pricing$20 / $100 / $200 / EnterpriseFree; you pay your model provider directly
HandoffClaude Code (in-app)Any agent on $PATH, plus HTML / PDF / PPTX / ZIP exports
Self-hostableNoYes (laptop or Vercel)
Data pathPrompts → AnthropicPrompts → your chosen provider; nothing through us

The honest summary: Claude Design has the most polished single-product experience. Open Design trades the polished single-product surface for a library — more skills, more systems, more agents, designed to compose with the agent already on your laptop.

Three thin black slabs stacked with visible gaps like a layer stack in isometric, dimension ticks marking the gaps, an olive leaf on top, on a warm editorial study plate
A product and a layer — Open Design sits between your agent and the design work.

Who should pick what

If you are…Pick
A solo PM at a company already on Claude Pro who needs a prototype before lunchClaude Design. The $20/month is sunk; the interface is genuinely fast.
An enterprise design team where Anthropic already cleared procurementClaude Design. You’ve paid the integration cost once; spend it.
A solo designer who wants “Claude Design but free”Open Design. Free, and you own the workflow instead of renting it — point it at a model you already pay for and the first deck takes about ten minutes.
A design engineer who already drives Claude Code, Codex, or Cursor from the terminalOpen Design. Your agent is the design engine; the skill layer adds taste and structure without a new app.
Anyone who needs BYOK, model choice mid-project, or local-only for sensitive briefsOpen Design. The reality is rougher than the marketing, but the contract is the only one that actually holds.
An open-source contributor who wants to ship a new design skill the project can adoptOpen Design. Drop a folder, restart the daemon, send the PR.
A team standardising on a portable design system that survives tool churnOpen Design. DESIGN.md files outlive the tool that reads them.

The dimension that decides it for most teams isn’t quality. It’s whether you’d rather rent the workflow or own it.

What to do next

If you want to see what owning the workflow feels like before you spend a Pro subscription, run the three-command quickstart and point it at the model you already pay for. The whole thing lives in one repo and the first deck takes about ten minutes.

Try the open-source workflow.

Next step

Run the skill workflow locally

Browse the workflow library, pick a starting point, and wire it into the agent you already use. Join our Discord if you want help adapting it.