This blog is now fully AI coded and run by an agent I just talk to

This blog has been rebuilt many, many times as my developer journey progresses. It started as a flash(!) website, briefly lived in WordPress, was a Ghost installation for a few years and in 2019 became a Nuxt JAM stack with markdown files. And this time, for the first time, it's fully AI coded.

The problem was never the tech

It was always a hustle to actually sit down and write these blog posts, which is why there's hardly any life here. Just look at the dates: a few posts a year until 2019, one in 2020 and then nothing until 2024. Every rebuild was fun. The writing afterwards, not so much.

So really what I'm trying to do is to rethink the whole model of how to build blogs like this.

Two days of not writing code

I didn't touch a single line of code for this version. I spent the last two days talking to Claude Code, and here's what that looked like:

• It analysed the old Nuxt 2 site and came up with 10 redesigns for the home and blog page. I picked the one that looks like a code editor: file tree on the left, tabs on top, the orange status bar at the bottom. Opening a post opens a new tab, like a file.
• Then it rebuilt the whole thing from scratch on Nuxt 4, Nuxt Content 3 and Tailwind 4. Still flat markdown files, still fully static, plus all the SEO stuff: sitemap, structured data, RSS.
• At some point I told it that it's my lead dev and orchestrator and it should fire off agents for the actual work. So it did, several at a time, and checked their screenshots before telling me anything was done.
• When something was bad, I said so. The first version of the projects timeline was basically impossible to understand and read. Back to the drawing board, four new options, I picked an ls -l style table plus a changelog, and it built both.

Just talk instead of write

Now I'm basically trying to base this off a Claude skill that sits right in the Claude Code project for this website. The idea is that I can just talk into the Claude application, do a brain dump, and then it'll be automatically added to the site as a blog post. It will automatically be assigned to the project that it belongs to and added to the changelog.

What the skill does:

• It keeps my words. Grammar gets fixed, but slang, abbreviations like irl or atm and the odd dirty metaphor stay. It even collects them as my "signature style elements", so it gets better at sounding like me with every post.
• It asks before it makes stuff up. Missing a date or a number? It asks, or leaves a visible TODO.
• It figures out which project a post belongs to and writes the changelog entry.
• It checks that the site still builds before it saves anything.

This post is the first one made that way. I talked, it asked me five questions, done.

Strava for my builder journey

And really this whole thing is supposed to feel a little bit like Strava for my builder journey. Every project now has its own page with a changelog: when it started, when it stopped or got rebuilt, and every post about it.

I've already started adding GitLab to kind of like automatically pull in development progress. So far only as the activity tracker: a GitHub style grid per project, built from the commits in my private repos (just the counts, no code and no commit messages). But maybe eventually as a full change log, automatically managed change log system.

I'm sure that I can add quite a few more UX elements to make this nice. But the whole idea here is to basically have one static flat file build that is managed by an agent that I just talk to, and it publishes and displays all the stuff that I'm doing.

What's next

I'm wondering already if I could hook this up to other stuff as well, like my X account, to pull in my feed from there, but also to maybe auto-publish blog posts and maybe even comments, and have this as the central hub for content that goes out.

So I'm very, very excited how this thing can now organically grow even faster and even better. Because it'll be so much easier for me to actually be active here.

If I only have to talk instead of write.