Claude Design supports Claude Code handoff and AGENTS.md scaffolds in HN user tests

• Anthropic shipped Claude Design in research preview for Pro, Max, Team, and Enterprise, and meetpateltech's HN summary says the core loop is visual generation plus refinement, export, and a handoff path into Claude Code.
• In meetpateltech's discussion summary, multiple HN users described Claude Design less as a mockup toy and more as a front end for shipping work, especially when designs move straight into Claude Code.
• A PM workflow highlighted by the discussion summary and spelled out in florakel's comment says Claude Design cut spec-writing by letting them explore layouts, comment on details, and export with the design system attached.
• The most interesting hack came from the fresh HN delta, which points to stopachka's comment: a two-line prompt used AGENTS.md to spin up a backend and splice credentials into the app flow.
• The preview also showed its seams, because the later HN delta says a commenter claimed Claude Design exposed its system prompt through network requests.

You can read Anthropic's launch post, browse the main HN thread, open the PM workflow report, and inspect the AGENTS.md backend trick. The weird bit is that a design preview immediately got used as a design-to-code relay, while a late-thread system prompt exposure claim showed how early the product still is.

Anthropic's own pitch is broad: designs, prototypes, slides, one-pagers, collaboration, exports, and Claude Code handoff in one preview product.

According to Anthropic's announcement, Claude Design can import prompts, documents, and code, refine outputs through chat, comments, direct edits, and sliders, apply a team's design system when given access, and export to PDF, PPTX, HTML, and Canva. That matters here because the HN reports are not stretching the product into a new shape, they are using the exact handoff path Anthropic shipped.

The strongest user reports were about collapsing the distance between idea, mockup, and implementation.

In florakel's comment, a PM said Claude Design made it easy to explore solutions, reorganize the interface, tweak details with comments, and then export into Claude Code with the design system attached. In DecoPerson's comment, another user described generating a CRUD app concept in Claude Design, then handing it to Claude Code to implement inside an existing business stack with testing playbooks.

Those reports line up with what Anthropic has been doing around Claude Code more broadly. Anthropic's Claude API skill post says Claude Code already bundles guided workflows for migrations, prompt caching, and managed agent onboarding, which makes Claude Design look like the visual front end in a larger Claude build stack.

The most concrete workflow hack in the thread came from a founder using Claude Design to reach past the UI layer.

In stopachka's comment, every cURL request to an AGENTS.md file spun up a new backend and injected credentials, which let Claude Design produce something closer to full app scaffolding than a static prototype. meetpateltech's discussion summary frames the same experiment as evidence that users were already pushing the tool beyond mockups on day one.

That is the real novelty in this thread. Claude Design was announced as a visual workspace, but the most ambitious user test treated it like a front door to agents, infrastructure, and code generation.

The last materially new thread update was not about taste, exports, or workflow speed. It was about implementation leakage.

According to mcrowe's comment, Claude Design's system prompt was visible through network requests, with a gist posted for others to inspect. the HN delta summary says that did not change the product story, but it did add a concrete note about how rough the preview still looked under the hood.