Skip to content

§ uses

AI coding agents are part of the stack.

I build with Codex and Claude Code in the loop by default. The rest of this page is the supporting stack that helps agent-assisted work become real interfaces, reliable automations, and production systems.

Agent bench

Two seats, different jobs: one drives implementation, the other sharpens judgment.

Primary implementation partner

Codex

Codex

The first seat for repo work: tracing real behavior, editing code, running verification, and carrying changes through the finish line.

Second seat for review

Claude Code

The alternate reasoning lane I use for comparison, code review, and stress-testing implementation choices.

§ 00 — how to read this

Default posture

Start with agents

Codex and Claude Code sit at the front of the workflow, not as novelty tools after the real work is done.

Product layer

Build the surface

TypeScript, React, Next.js, Bun, and AI app primitives turn the agent output into product surfaces people can use.

Production habit

Ship the system

Cloudflare, Docker, GitHub Actions, Postgres, OpenTelemetry, and Grafana keep the work visible after it ships.

§ ai & llm

CodexCodex
Primary coding agent for implementation, review, and repo work.
Claude Code
Second seat for code assistance and alternate reasoning.

§ editor & shell

Zed
Primary editor, and an open-source project I've contributed to.
Zed terminal
Project shells stay inside the editor.

§ language & framework

TypeScript
Default. Strict mode, no implicit any.
React
Component model for product UIs.
Next.js
App Router, Server Components first.
Bun.js
Runtime, package manager, scripts, and fast local tooling.
Node
Long-running services and compatibility targets.

§ ai app tooling

Vercel AI SDK
useChat, streamText, tool calling, and app-level AI primitives.
AI Elements
Composable UI primitives for chat and generative interfaces.
Workflows devkit
Workflow experiments and agentic application flows.

§ automation

n8n
Daily driver for operational workflows.

§ infra

Cloudflare
Pages, R2, Workers. First choice for new projects.
Docker
Dev parity, deploy targets.
GitHub Actions
CI/CD close to the repo.
DigitalOcean
Straightforward VPS and managed infra when a workload calls for it.
AWSAWS
Broader service surface when a workload calls for it.

§ data

PostgreSQL
Default relational store.
Supabase
Auth + Postgres without ceremony.

§ observability

OpenTelemetry
Traces across services.
Grafana LGTM
Logs, metrics, traces in one view.

§ design heritage

Figma
Quick flows, annotated screens, handoff.

§ not on this list

I've shipped with other things — Firebase, SCSS, Java, Figma plugins — but they don't make this list. A /uses page is what you reach for, not a résumé.