The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Claude code one shotted this, design + dev,
Are designers cooked?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
Recent designs we tested for GoodMo Studio, which one do you prefer?
9 votes
Ends in 15h
Being a designer feels like a superpower. Build a prototype? Nope. A fully working app? Yes! Here’s what I made:
Leela is a 2,000-year-old Indian board game with 72 squares, one question, and one die. You roll to enter, move through named inner states, and write a reflection at each square.
Existing versions are either flat, digitised boards or feature-heavy wellness suites. I wanted to make a quieter one.
How I built it:
→ Flowstep MCP wired into Claude Code, Created Flowstep screens directly on canvas and implemented changes from the canvas and using Figma, Design MD file inside of Flowstep is a gem, helps to create cohesive design fast
→ Three complete design iterations before the visual language felt right: a night-sky version, a minimal one, and finally the aura direction that shipped.
→ A playable build deployed on Vercel with the real rules: roll a six to enter, three sixes burn, land exactly on square 68 to complete the game, and landing on square 72 sends you back to 51, music on/off, record or type settings.
→ An optional AI guide running behind a serverless function, so the API key never reaches the browser. The game is fully playable without it.
🎉 Link: Flowstep
🎮 Play: https://leelagame.vercel.app
Linkedin Post: link
Built with Flowstep, Claude Code via MCP, and Vercel.
#FlowstepChallenge
can't wait to try out this game, a 2000 year old game with 72 squares seems like a real challenge, I don't know but my mind is telling me "SUDOKU STRATEGY" 😂. I love also how many screens you have and the consistency that you respected.
I built a ghost-hunting game. Then I used MCP to design everything that comes after it.
PHI HUNTER: FIRST NIGHT is finished and playable. You use light to reveal what's
hiding, mark it with three Sigils, survive what it does next, bind it, and archive it.
One person, one encounter, one night.
A first encounter isn't a product. A product needs an archive, a map, equipment, a
reason to come back tomorrow night. That's where a solo creator normally stops —
not because the ideas run out, but because designing a connected system by hand is
where the time goes.
So I designed it through Flowstep over MCP, from my editor. I never opened the design
tool by hand.
WHAT I LEARNED ABOUT SPEED
Speed wasn't the hard part. Precision was.
My first plan was wrong. Sixteen screens with a shop, a wallet and a payment flow —
things this game had never been about — plus a colour palette I wrote from memory
that existed nowhere in the product. A tool this fast builds the wrong thing just as
quickly as the right one.
So I went to the source. The game has a frozen design-token file: fourteen colours,
eight geometry values, motion timings. I moved it into Flowstep value for value.
Nothing was redrawn to match — it was transferred. The same design system running
against two different rendering targets.
Then one request. Seven connected screens. One message.
WHAT MCP COULDN'T DO
It wasn't all clean. Wrong images, clipped text. And the toolset has no way to link
screens, so I'm not going to pretend this is a clickable prototype.
For that I used a browser agent — also over MCP — to open the real canvas, compare
versions, throw away the weaker set and fix what was actually broken. Two agents,
one job: one designing, one inspecting.
AND IT ENDED BACK IN MCP
The last fix I didn't expect. One screen wouldn't respond to any prompt. So I pulled
that screen out as code, corrected it in my editor, and sent it back in.
It accepted it. No regeneration. No credits spent.
The design tool returns real code and takes real code back. That's not a black box.
That's a workflow.
The first night is finished. Everything after it is labelled a concept on every
screen, because the point was never to look further along than I am.
MCP didn't design this for me. It removed the reason a solo creator stops after the
first night.
Play the first night — it runs in your browser, no install:
The seven connected screens, designed through MCP:
@flowstep #flowstepchallenge
