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
DREAM-O — The global registry of dreams.
I almost never remember my dreams. I wanted an app that would tell me what I dreamed last night — and the moment I imagined it working, I knew what the company behind it would actually be. So I built that company instead.
A pillow unit records every session. Twelve minutes after you wake, the company issues a record. It never explains how.
What you're allowed to see of your own dream depends on which plan you pay for. ORIGIN opens one scene a month. The rest stay in custody — described in full, never opened. Their time, their length, their size, their state. Everything except what happened. After fourteen days they're destroyed. Not for the company. For you. And the company doesn't say destroyed. It says released.
Every screen is written in that voice: procedural, patient, institutional. The product never winks. Nothing on any sheet tells you this is wrong — you work that out yourself, somewhere around the retention page.
One prompt in Flowstep produced six screens. From there it was iteration — prompt, look, correct, look again. Text overflowing, blocks colliding, things that looked fine until I zoomed in. Every screen sits on a percentage grid with four x-values and a single hairline spine at 68.4% height. No border radius, no shadows, no serifs, no accent colour anywhere in the system.
Then I connected Claude Code to Flowstep's MCP server, handed it my design guide, and asked it to audit all fourteen screens against it, one by one. A second prompt to fix what the audit found. It worked inside the Flowstep file over MCP. I went off to cook.
I came back and it was ready — I just wired a few links by hand, three clicks each. Fourteen screens for twelve sheets — the record sheet exists three times, one per plan. A path you can walk end to end.
Prototype: https://app.flowstep.ai/file?activeFileId=0a82e6e8-edfa-4dfb-ace8-dfb2e8122859
Social: https://x.com/JosIgnacio17989/status/2083406318304481732
Built with Flowstep · Claude Code over MCP
@flowstep_ai #FlowstepChallenge
Love this
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
Hi everyone! I'm Yuri, and this is my project for the Flowstep Challenge by Contra!
I have many volunteer friends around the world working in places where disasters have struck, and people need help. I often hear from them that they use different tools in their work, but they still really lack full automation to connect coordination centers with individual volunteers. This request inspired me to do this project!
I took a tool one of these volunteer organizations already uses and built out the parts it's missing:
- For coordinators (desktop) - all incoming requests with their statuses, warehouse state, the stats they actually need, and a map view of where every request is coming from.
- For volunteers (mobile) - a new request with its status, the full details, and a simple accept or decline.
Now, the fun part: how it was made. I ran Claude Code + Flowstep together over MCP. First, I wrote out a spec of everything the product needed to do and handed it to the setup. Then I went through the existing tool and documented its design system - this turned out to be the smartest thing I did, because it kept every screen consistent instead of feeling like ten different products. After that, I generated prompts in Flowstep, one dedicated prompt per user flow. I refined each screen with prompts, and honestly, most of the time it landed on the first or second try. The few tiny things left over I just nudged by hand right in Flowstep.
And I'm genuinely happy with how it came out. Doing all of this manually would've cost me a solid 6–8 hours. This took me a bit over two.
And the agent messages provided for the challenge were enough for me to finish. I was only 1 short - to adjust an icon on the last screen (hope you won’t blame for that).
🔗 The result of my work in Flowstep: https://app.flowstep.ai/file?activeFileId=0c294720-d873-4ced-b99c-e6f20f818209
Thank you all so much for checking it out, and I'd be grateful for your feedback and comments!
#FlowstepChallenge # #Flowstep #Claude #ClaudeCode #Weavy #UX/UI #ProductDesign #Saas #Dashboard
This CrisisCoord concept is brilliant.
The dashboard + mobile + warehouse flow feels so real and needed.
Love how you handled the urgency with the timers and priority system.
Great execution!
Bento reads best when the tiles vary in weight so the eye gets an anchor before it hits the dense cells; on a data-heavy dashboard like this, giving the pipeline card clear priority over the smaller metric tiles is what keeps it from feeling like a wall of equal boxes.
Latin tradition, reimagined.
Love, Coco brings Latin-inspired desserts to the Canadian market through a contemporary visual identity.
The challenge was to build a brand that communicated the quality of its ingredients and its Latin roots without relying on familiar visual clichés. Instead of recreating a traditional aesthetic, the identity needed to feel current and distinctive for a Canadian audience.
The process began by analyzing the visual codes commonly used by dessert and Latin food brands, identifying what to keep and what to avoid. This research informed a visual system built around contrasting typography, a vibrant yet refined color palette, and compositions inspired by classical still lifes.
These design decisions place the fruits at the center of the identity, highlighting the quality and origin of the ingredients while giving the brand a distinctive visual language.
That peach and melon color story feels specific to the brand's actual story, doesn't read like generic tropical at all. What was the trickiest part of translating Latin visual cues without falling back on the usual cliches?