Colophon

How this site (and its terminal) was built.

Tech Stack

  • Next.js 16 (App Router), React 19, TypeScript
  • Tailwind CSS v4, with @tailwindcss/typography for the blog and about-me pages
  • react-markdown + remark-gfm for markdown content, gray-matter for frontmatter
  • react-pdf for the in-browser resume viewer
  • react-icons for iconography
  • Geist Sans / Geist Mono via next/font
  • Vercel Analytics + Speed Insights, deployed on Vercel

What Claude Wrote

Mostly the terminal you saw on the splash page: the boot sequence, the extensible command system, the draggable project windows, the CRT-styled screen and its scrollbar, and a lot of the smaller interaction details (focus handling, faking SIGINT (Ctrl+C) closing a window that kind of thing).

It wasn't a one-shot "build me a terminal" prompt. It was a long back-and-forth: design the mechanics first, with a design document, implement, then test it for real and fix what actually broke.

Claude also helped with plain CSS and layout tweaks elsewhere on the site along the way — this page included.

Why Let an AI Write Part of My Portfolio?

Because this is how I actually build things now. Pretending otherwise on the one page that's supposed to represent my work honestly would be a little silly.

The interesting skill on display here isn't "typed every character myself".

Claude can do a lot of it faster, and at this point, I don't remember all of the syntax and boilerplate I used to write myself.

it's knowing what to build, directing the implementation, and catching the parts that were wrong or needed a second pass. That's the job now. This page is just the part of the portfolio that says so out loud.