Most AI-native devs stop at "it works." I obsess over one thing that separates a working site from one that actually converts: visual hierarchy.
Every landing page I build with Claude Code + Next.js follows the same principle. The visitor's eye needs to land on exactly one thing first. Then flow to the second. Then the CTA.
On the skincare brand site I shipped last month, the hero had a full-bleed product shot, a 4-word headline, and one button. That's it. No competing elements. The client wanted to add a second CTA, a banner, and a testimonial carousel above the fold. I pushed back.
Here's the rule I follow: if everything is important, nothing is.
I build every section by asking three questions:
What's the single action I want someone to take here?
What's the minimum context they need to take it?
What can I remove?
This works whether it's a restaurant page with a reservation CTA, a fashion brand selling scarcity, or a mobile detailing business that just needs the phone to ring.
AI tools let me ship in 48 hours to 7 days. But speed without visual hierarchy just means you built a bad site faster.
I’ve been razzmatazzing and flibbertigibbeting with Claude Code and somehow ended up with a new yels.dev.
It finally feels like me: simple on the surface, slightly complicated underneath, and very much alive.
You can see who I am, what I do, the work behind Herodot, RaptorLabs, CyberLink Security and Solmint, plus a selection of projects I’ve built across AI, cybersecurity, Web3, product systems, education, archives, and experimental digital spaces.
The simple-on-the-surface, layered-underneath idea comes through so clearly in the presentation. I especially like how the project archive turns the site into something to explore rather than just a résumé of links.
Smart filtering and search are doing different jobs here: filtering narrows what the shopper already knows they want, search recovers the visit when they don't have the right words for it.
Recent work for Avallon AI, a YC-backed startup building AI infrastructure for hospitality.
The challenge was explaining a technical product in a way that feels clear to hotel operators, partners and technical teams.
The website was structured around the product story, core capabilities, use cases and proof. Each section helps visitors understand what Avallon does, where it fits and why it matters.
Framer was used to move quickly while giving the team full control after launch. Reusable components and CMS collections make it easier to publish new content, expand the website and keep everything consistent.
The scope included:
• Website design
• Framer development
• Responsive layouts
• CMS architecture
• Custom code
• SEO setup
• Analytics and conversion tracking
The result is a clearer product story and a flexible marketing system that can grow with the company.