01 / 01 · StoryAgentic coding

Building this site

Most of my work is confidential legal software, kept behind NDAs. This is the first thing I can show you, and the first public site I've built with agentic coding. I gave it the same care I'd give anything I ship.

Year
2026
Role
Staff Software Engineer
Platform
Hugo, plain CSS, Go
Topic
Agentic coding

An AI coding agent can write a page in seconds. That’s the fun part, and also the catch: a quick fix here, an untested tweak there, and before long nobody can say why the page looks the way it does.

I’m used to work where every change needs a clear reason, so I treated Claude Code like a new teammate. We agreed on a short spec first, wrote the test before the code, shipped one small change at a time, and noted every time the plan changed.

Here’s how it went, one decision per step, in the order it happened: what I picked, and why.

  1. 01 Ground rules
  2. 02 Look and feel
  3. 03 Voice
  4. 04 Light and low maintenance
  5. 05 Measure, then fix the spec
  6. 06 Self-hosted fonts
  7. 07 Resume as a page
  8. 08 Footer and motion

01 Ground rules

Before the first prompt, I wrote down how I like to work, and Claude Code reads it at the start of every session.

Keep spend as close to $0 as possible: free tiers and local tools first, and say what a choice costs before I commit to it. Agree on a short spec, then a step-by-step plan, before any code. Show each test failing for the right reason, then break the code on purpose to prove the test notices. One logical change per commit, on a branch, never straight to main. Pick the lighter tool with fewer moving parts. And never put a secret on a command line, in a log or on disk.

None of this is new. It’s what I’d ask of any teammate, written down so the agent can’t forget it.

02 Look and feel

I asked Google’s AI Mode to “show me a fun and technical website”. It pointed me to Awwwards’ technology showcase, where I found Lucas Lima’s portfolio. I loved how calm and steady it felt, so I asked Claude Code to recreate its layout system: the pill nav, type scale and tile grid. The words and images here are my own. (How we measured it)

03 Voice

I wanted a downloadable resume with my contact details, without handing them to every scanner and bot. So I was thinking through magic links, and I needed a message to tell people their link was on its way.

Claude suggested “Thanks. If it’s approved, you’ll get an email.” Accurate, but a little cold. So while Claude worked on something else, I asked Google’s AI for something “friendlier and fun but still secure”. It came back with several options, each with a note on why it worked and how it would feel to read. I picked my favourite: “Got it! We’re taking a look—keep an eye on your inbox for an update.”

That line became the voice for the whole site: warm, clear about what happens next, and no more detail than you need. So the rules are: sound like a helpful teammate, not a legal disclaimer. Be plain about what happens to your data. And claim nothing a test can’t keep true. Every page and commit message gets checked against it, including this one.

04 Light and low maintenance

I asked for the lightest stack that could do the job. Hugo is a single Go binary, and plain CSS and HTML don’t need a bundler. Skipping Node means there’s no package tree to audit, no build tool to keep current, and nothing to install on a new machine except Hugo.

I did think about Tailwind, to match another project of mine. So we measured first: my plain CSS came to 3.0 KB gzipped, against 3.2 KB for the Tailwind build. No size win, and it would have added a 112 MB binary and a build step. Plain CSS it is.

05 Measure, then fix the spec

At first I described the reference site to Claude in plain language: calm, warm greys, big type, pill-shaped links. Claude built exactly what I described, and it didn’t feel like the site I loved. Words like “calm” and “big” left too much room for guessing. The code wasn’t the problem. My description was.

So we measured. Claude read the real palette, type sizes and layout straight from the reference site’s CSS, and we fixed the spec before writing another line of code. Lesson learned: look at the real thing before you write it down.

That raised my next question: how close is too close? Imitation may be the sincerest form of flattery, but I didn’t want to copy someone else’s work. So I drew a line. We’d recreate the layout system, the bones of the site, and never its words, images or brand. Those are all mine here. Well, mine with a leg up from Claude.

06 Self-hosted fonts

The easy way to add fonts is to load them from a font CDN. But then every visit would ping someone else’s server, and I’d promised no trackers and no third-party loads. So General Sans and Geist Mono are served from this site, and a test fails the build if anything tries to load from somewhere else.

The licence shaped the rest. General Sans can’t be shared or changed, so its files stay exactly as published and out of my public code. A size-matched fallback keeps the text from jumping while they load.

07 Resume as a page

My resume now lives in one data file. It renders as a page here and prints to a PDF at build time, so the two can’t drift apart. My email stays off the public page, so scrapers can’t harvest it.

The PDF had a surprise in it. My 10pt text felt cramped, and I kept adjusting the spacing to fix it. It turned out Chrome was quietly shrinking the whole page to about 78%, because the header was too wide to fit. I only spotted it while changing something else. Once it was fixed, I added a test that fails if anything is wider than the printed page, so it can’t sneak back.

What I’d tell a teammate

Write your ground rules down before the first prompt. Show the agent the real thing, not adjectives. Ask a second AI when an answer feels cold. And make every change prove itself with a test, so you never have to take the agent’s word for it.

Treat AI like a teammate, and stay curious. When something puzzles me, I ask if there’s a reason to keep it that way. Writing this story, I asked if there was a good reason to keep the reading column so narrow. There actually was, and the discussion resulted in a larger font.

The agent made me faster. The tests are why I trust what it made.

Credits & inspiration

← All stories