Claude Design: real interfaces, designed at the speed of a conversation.
I design product screens, landing pages, and flows directly in Claude Design — exploring more directions in days than a traditional process covers in weeks, then refining the strongest one into production-ready work.
Claude Design is not a mockup generator. It is a design surface that outputs working interfaces.
I design in Claude Design the way I used to design in Figma — but the artboards are real HTML, so what you review is what gets built. That changes the economics of exploration: three directions instead of one, every state designed instead of the happy path, and a handoff your engineers can open in a browser. I bring the product judgment; Claude removes the production tax.
Why teams come to me for this.
One direction gets designed because three would blow the timeline.
Flat frames hide the empty, loading, long-content, and error states.
Engineers rebuild from screenshots and the spacing drifts on day one.
Prompting without design direction returns the same template everyone else got.
Full screens designed as real markup — responsive, interactive, reviewable in a browser.
Several distinct directions in the time one usually takes, so you choose from real options.
Conversion-shaped pages with the motion and layout craft already in place.
Empty, loading, error, overflow, and permission states — not just the demo path.
Type scale, colour, grid, and motion decided deliberately and applied consistently.
Markup, tokens, and notes your front-end team can take straight into the stack.
- DirectionAgree the product goal, the audience, and the visual direction before anything is generated.
- ExploreDesign several real directions in parallel and review them live, not as flat images.
- RefineTake the strongest one to production quality — states, responsiveness, accessibility, copy.
- Hand overDeliver the files, the tokens, and a walkthrough so the build starts without translation.
Get a real, clickable product in front of users before committing engineering time.
Add design capacity without adding a hiring cycle.
Pitch with working interfaces instead of static decks.
A designer who uses Claude as a production tool, not a novelty.
The tools I design and build with, end to end.
Interfaces designed and shipped with Claude Design.
FinPay — unified invoicing & payments dashboard
Redesigned a fragmented back office into one clear operational view for finance teams.
MediCare — patient booking made effortless
A mobile experience that turned a 9-step booking flow into three taps, for all ages and abilities.
Shelfie — a storefront builder for small retailers
Simplified product listing and checkout so non-technical sellers could launch stores in an afternoon.
No. The direction, structure, and every judgment call are mine. Claude is the production surface — it removes the drawing time, not the design thinking.
A working, responsive interface you can open in a browser, plus the source files, assets, and a direction document your team builds from.
Yes. I start from your tokens, type, and components so the output sits inside your identity rather than beside it.
A first set of real screens usually lands within a week of the kickoff, and we iterate weekly from there.
See it as a real interface.
Send me the brief — I'll come back with clickable screens, not a slide of mockups.