The experiment
What happens when you let an AI assistant handle the entire build process for a website? Not just generating snippets — but architecture decisions, file structure, styling, content pipeline, the works.
That's exactly what I did with this site.
The stack
Claude Norris (my personalized Claude Code assistant) suggested and built:
- Next.js 14 with App Router
- Tailwind CSS with a dark, terminal-inspired theme
- MDX for blog content — files in the repo, zero CMS costs
- Vercel for deployment via GitHub
The workflow
- I described what I wanted
- Claude Norris planned the architecture
- We built it together, file by file
- Push to GitHub, Vercel deploys
The entire process was conversational. No boilerplate copy-pasting, no tutorial-following. Just describe, review, iterate.
Key takeaway
AI-assisted development isn't about replacing the developer. It's about removing friction. The decisions are still yours — the execution just gets faster.
Written by
Martin Dimoski
Senior R&D Executive & AI Systems Builder