Railcode founder Yakko Majuri walks through a real agent-assisted design process—inspiration spectra, single-HTML forks, color playgrounds, and relentless iteration—showing how non-designers can steer coding agents toward tasteful product sites.
How our vibe coded website looks like a designer made it
When you think of a vibe coded website, you probably think of generic AI design slop. However, I also vibe coded this very website you're on, and well, it looks very different.
A lot of people came up to me and asked how I made the website, and even who I worked with on it. So I thought I'd talk through my creative process for building the Railcode website—not because designers are unnecessary (quite the opposite), but because coding agents made me more excited about design: I can finally make a creative vision a reality.
A whole lotta rollercoasters
The name Railcode comes from "code on rails"—apps and agents are just code, and we handle infra and guardrails. Rails + fun = rollercoaster, so the website was going to have a rollercoaster on it.
I'm not a designer, so I rely on examples and inspiration:
Browse the web for designs that I like
Tell an agent to generate a ton of designs of a thing in different styles
Useful tactics: ask for a spectrum of intensity/complexity; ask for at least 4–10 versions with some "go wild" variants that usually suck but spark ideas.
Rollercoaster Tycoon
A neon "go wild" design reminded me of Rollercoaster Tycoon. I had Fable build a mini playable component, then decided a full game was too much and iterated until I landed on a single rollercoaster I liked—then realized it needed a whole park, not a floating asset.
Going off the rails / Forks on forks
I keep everything in one HTML file until the design is ready, then turn it into React. That makes forks and side-by-side comparisons fast. I also build "playgrounds" to try colors and variables in real time (e.g., landing the exact grass tone). The hero style then dictated the rest of the site—including morphing nav colors by section.
Inspiration and process summary
I exclusively use Anthropic models for design; Fable has worked best.
One HTML file until satisfied, then componentize.
Look at lots of websites; reuse specific components as bases.
Generate many throwaway designs early; pull sparks from them.
Spectrum prompts (minimal → outlandish) plus "go wild" slots.