A Hacker News thread this week asking developers which design tools they use with Claude Code turned into something more useful than the usual tooling survey: a reasonably specific map of how serious practitioners are structuring their agentic workflows in early 2026.
The short answer, from the replies, is Figma and Excalidraw upstream, MCP integrations throughout, and CLAUDE.md files doing heavier lifting than most would have predicted.
On the design input side, several commenters described exporting Figma frames or Excalidraw diagrams directly as context for Claude Code sessions — using visual artefacts as grounding material rather than translating them into prose specifications first. The workflow skips a translation step that has historically introduced ambiguity, and a handful of respondents noted it has changed how their design-to-code handoffs work in practice.
The Model Context Protocol thread runs through most of the more sophisticated setups. Commenters pointed to MCP servers pulling in live component library state, design tokens, and documentation as active context sources. The agent reads the system as it currently exists rather than working from a snapshot that someone last updated months ago.
What drew the most replies, though, was CLAUDE.md. The thread surfaced a growing practice of treating these project-scoped instruction files as genuine design artefacts: encoding conventions, architectural constraints, and workflow rules before a session starts. The framing that kept appearing across replies was that you are not prompting Claude Code so much as configuring an environment for it — and the configuration work is where a lot of the actual design thinking now lives.
The more unexpected finding is how many non-engineers are showing up in these workflows. Several commenters described screenshot-to-code pipelines where designers feed UI frames directly into Claude Code sessions and receive production-ready component code without a developer handoff. Reliability at production quality was contested in the replies, but the pattern is established enough that dedicated tooling is being built around it.
For a toolchain that barely existed eighteen months ago, the diversity of integrations on display in the thread suggests the workflow layer around Claude Code is consolidating quickly — and that the work of designing for an agent is becoming its own discipline.