Skip to content
Claude Code

How I build with Claude.

The engineering is mine. AI from multiple providers fast‑tracks it.

Credentials from Anthropic

Claude Academy
23/23
All 23 courses completed · Anthropic · Oct 2026
Cyber Verification Program (active)
Approved
Approved on Anthropic’s Cyber Verification Program
See both on LinkedIn (opens in a new tab)

Specs, then agents.

The same habit as every business I’ve run: written down, tested, handed over complete. Agents just build it faster.

  1. Written first.

    Work is written down before it is built: what is being delivered, and what is deliberately out of it.

  2. Built with agents.

    Built across Claude Code and other leading AI platforms, alongside my own tooling.

    ClaudeCraft · ~46k lines · 146 files

  3. Audited.

    Then audited by reviewers.

    ClaudeCraft · 18 audits · 195 defects · 6/6 criticals fixed

  4. Handed over.

    Documented for whoever picks it up next, and handed over complete.

ClaudeCraft: one game, audited 18 times.

A full survival game, implemented by Claude from frozen specs, then audited.

ClaudeCraft in the browser: a block-built forest valley under a sunset sky
  • three.js
  • 11 biomes
  • Multiplayer relay
  • Procedural textures and sound
  • 34 acceptance suites

Agents in production.

A live SaaS with a Claude-powered chatbot builder and an AI language trainer. A voice dictation and computer control app is in development.

  • VanticTools

    SaaS

    A suite of business tools with a Claude-powered chatbot builder, on Stripe subscriptions.

  • Zannen

    AI product

    An AI language trainer for Japanese and Simplified Chinese.

  • Voice dictation and computer control

    App

    In development

A custom Claude skills suite.

  • Branded document generation
  • Product storyboard to video prompts
  • Launch film motion design
  • Course QA runnerTests course sites end to end.

What it is built with.

The platforms behind the work. Tools, not clients.

  • Claude
  • Anthropic
  • Next.js
  • React
  • TypeScript
  • Supabase
  • Vercel
  • Stripe
  • Cloudflare Workers
  • Framer
  • GSAP

Where a model earns its place.

The lines I hold on automation.

  • I don’t lead with AI.

    Some of it uses models where they genuinely earn their place. Most of it is plumbing.

  • I don’t automate judgement.

    Removing the typing is the win. Removing the thinking is the trap.

  • I don’t automate a broken process.

    I map the process as it runs, not as it’s documented, and find the manual step before I build anything.

  • Nothing goes live on trust alone.

    A new automation runs alongside the manual process until the two agree.

  • It speaks up when it needs a person.

    And stays quiet when it doesn’t. A notification should always mean something.

  • Never a black box.

    Documented in plain language, so someone competent could pick it up from the documentation alone.

AI makes it faster. I make sure it’s right.

The method, written down.

Next · Writing