I'm working on something a little different for my portfolio and I'd love some feedback.

I'm doing a complete redesign of my personal portfolio to make it more fun, memorable, and a better reflection of who I am as both a frontend developer and UI/UX designer.

I've been a Pokémon fan for as long as I can remember, so I'm leaning into that inspiration to create an experience that feels like exploring a classic Pokémon game while showcasing my work, case studies, experimentation, and technical skills.

Now I need your help deciding on the direction.

Theme 1 Classic Pokémon Red/Blue inspired with bold colors, badges, and a modern retro feel.

Theme 2 Game Boy inspired with the nostalgic monochrome aesthetic that feels like playing on the original handheld.

Which one would you choose?

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