I design with Claude more than Figma now

201 points · 177 comments on HN · read original →

Points and comments are a snapshot, not live.

Designer at Jane Street now uses Claude to build working prototypes instead of designing mockups in Figma.

Edwin, a designer at Jane Street, describes how Claude has replaced Figma and design documentation in his workflow. He now writes problem descriptions, uses Claude in his editor to build functional prototypes, iterates directly on working code, and shares results with users before submission. This approach eliminates intermediate work like spec docs and Figma components. Recent examples include a 2000+ line feature adding LLM prompting to JSQL input and several other user-facing prototypes. He notes this became viable after joining Jane Street, where unfamiliar technologies like OCaml and Bonsai initially seemed out of reach for technical contribution. The workflow reduces back-and-forth overhead compared to traditional design-engineering separation, though it raises questions about reviewer input and whether iteration in working code constrains creative thinking versus traditional mockup-based design.

What commenters are saying

Commenters report similar experiences replacing Figma with Claude for prototyping, though several note the designs often look generic and safe without detailed aesthetic prompting. Others suggest using Claude Design iteratively before Figma refinement, or skipping Figma entirely for production. Some express skepticism about the blog post quality and Jane Street's credibility, citing its status as an Anthropic investor and regulatory issues in India. A broader thread emerges debating whether AI hype on HN is overstated, with counters that AI has legitimately reduced low-value work and enabled non-technical users to build their own tools.