Design tools are competing on 'one sentence, one image'—but Replit's latest release goes the other way. Instead of pushing you to write prompts, it hands you a stack of 'next step' suggestion cards.
What launched
In an update on August 4 (original blog post dated July 29), Replit upgraded the old Canvas into Replit Design. A project now has side-by-side Design / Build entries in the top bar, with no exports needed within the same project. Select a generated design frame and a "Suggested next steps" card floats up beside it—each suggestion is a single sentence, and clicking it generates a new frame while leaving the original untouched. It's a fork, not an overwrite. Official docs describe three categories of suggestions: change the look, add a missing section, or change context (e.g., a mobile viewport).
Correcting a misreading: it is not prompt-free
Official documentation opens with "generate design frames from prompts." The first frame still must come from one of four sources: a prompt, a template, an import (Figma / URL / screenshot / Claude), or a design system. Suggestion cards are a second step built on top of existing output, and they derive only from the frame you selected—Replit does not read your behavior or environment. The docs say the feature solves "facing a blank prompt box and not knowing what to ask for," not "never having to speak." Chat and suggestions work together; the docs explicitly note "Chat isn't just for polish."
The real differentiator: no handoff
The difference isn't "being good at design"—it's that there is no handoff. v0 and Figma Make still require dropping finished mockups into another tool; Replit Design frames become a running app via the Build tab in the same project, or can re-skin an existing app. Cursor and Claude Code are code-side agents lacking a canvas and visual forking, so they aren't direct competitors—Claude even offers a "Send to Replit" channel, pointing toward Claude handing work off to Replit.
What's genuinely new
The genuinely new element is making "fork + side-by-side comparison" the default. Wrong path? No undo needed—two versions sit side by side and you pick. This suits non-designers' cognitive strengths: people are good at choosing between two options, bad at describing something from scratch. Design systems are materialized as tokens.json + CSS variables + DESIGN.md, readable by both humans and models—more executable than a brand-guidelines PDF.
Limitations and caveats
- Mock frames on the canvas look like real pages but store no data and connect to no external services.
- Applying a design system to an existing app genuinely regenerates the entire styling layer; Replit shows a time/cost warning first, though specific quotas are unpublished.
- Mobbin is built in with 600,000+ real interfaces and 1,000+ apps (per Replit's own figures), but inspiration doesn't become code—docs state "Inspiration adds no code to your project."
- Creating a new app from a design frame requires Core ($25/month) or Pro ($100/month); the launch page's "available to all users today" is easy to misread.
- Browser only. No independent large-scale third-party testing seen yet.
- Official blog: https://replit.com/blog/introducing-replit-design
- Official docs (what it is): https://docs.replit.com/design/what-is-replit-design
- Official docs (suggestion cards): https://docs.replit.com/design/explore-suggestions
- Third-party review (billing/model list cross-checked): https://best.xiaohu.ai/article/replit-design/