Built with AI — Peter Nanos

This site was built entirely through conversation. No code was written by hand, no developer was hired, no template was purchased. Every design decision, every line of CSS, every content edit happened through a dialogue with Claude — Anthropic's AI.

The technical term floating around for this is vibe coding — a phrase coined by AI researcher Andrej Karpathy in early 2025 to describe building software by describing what you want in plain language and letting an AI handle the implementation. You bring the taste, the judgment, and the domain knowledge. The AI brings the execution.

What that actually looked like

The first version went live in a single day. The conversation covered everything: choosing a font (we landed on Fraunces for the name, Inter for body text), writing and rewriting the bio until it sounded like me and not a LinkedIn summary, debating whether to use company logos or typographic wordmarks, and fixing a mobile layout issue on an iPhone 12 Pro in real time. The site has kept evolving since — restructuring how the career story flows, generating dynamic social preview images, and passing a full WCAG 2 Level AA accessibility audit.

Claude wrote every line of code. I wrote every word of copy. That division of labor is the whole point.

The stack is deliberately plain: Next.js 16 with the App Router, React 19, deployed on Vercel from a GitHub repo. Typography is Fraunces, Inter, and JetBrains Mono, loaded through Next's font system. Styling is plain CSS with custom properties — no Tailwind, no CSS-in-JS, no component library. Vercel handles analytics and speed insights, and the social preview image is generated dynamically at the edge. Claude reads and writes files and runs commands directly on my machine through an MCP server called Desktop Commander — so I never had to touch a keyboard for anything technical.

What I brought to it

Taste. Judgment. The ability to say “that feels off” or “the name is too far right” or “that's a little douchey, rewrite it.” The ability to tell the AI that my bio shouldn't rattle off where I've been — it should answer the question of what I actually do and why it matters.

The line “it's not enough to be busy, you have to make yourself useful”— that came from me. No AI wrote that. The AI's job was to find the right place for it.

What this means for operators and executives

The barrier to building software is no longer technical. It's clarity of thought. If you can articulate what you want, describe what's wrong with what you're looking at, and make decisions under ambiguity — you can build production-quality software without writing a single line of code.

That's not a small thing. That's a fundamental shift in who gets to build.

Want to try it yourself?

Here's the prompt that started this site. Copy it, point it at your own project, and see what happens.

“I want to build a personal website. I'm [your name], a [your role] with a background in [your domain]. My audience is [who you want to find you]. The goal of the site is [what you want it to do for you]. I have no coding experience. Let's start from scratch — help me set up the project and then we'll build it together conversation by conversation.”

Start with Claude. Enable the Desktop Commander integration so it can access your machine directly. Then just describe what you want.