— COLOPHON
How this site is built.
The stack, the decisions behind it, and a record of how the site has changed.
— STACK
Next.js 16
App Router · React 19
Tailwind CSS v4
OKLCH tokens · no config file
TypeScript
Strict mode · noUncheckedIndexedAccess
shadcn/ui
New-york style · Radix UI
Framer Motion
All animations
next-mdx-remote
MDX rendering · gray-matter
Supabase
Postgres · RLS · JSONB
@tabler/icons-react
Icon library
Vercel
Hosting · Analytics · Speed Insights
— DECISIONS
Show the work, not the claim
Most portfolios describe strengths. I prefer showing research, product decisions, prototypes, and trade-offs so readers can evaluate the thinking directly. The goal is not to tell people what I know, but to make the evidence visible.
Evidence over self-assessment
I avoid skill ratings and progress bars. Product work is difficult to compress into a percentage. Case studies, artifacts, and outcomes provide a more useful signal than a self-reported score.
Optimize for reading
The interface is meant to stay out of the way. Typography and spacing are decisions, but they shouldn't be the thing a reader notices. If a design choice competes with the work, the work should win.
Systems before features
I'm drawn to products where behavior, incentives, trust, and infrastructure interact. That bias shapes both the projects I choose and how I analyze them. Most interesting product problems are systems problems in disguise.
Small surface area, high signal
A portfolio does not need to contain everything. The projects here were selected because each demonstrates a different mode of thinking: research, strategy, marketplace design, decision systems, or fintech infrastructure.
Built through iteration
Nothing on this site is permanent. Ideas evolve, case studies improve, and assumptions change with new information. The portfolio is treated like a product: observe, learn, refine, repeat. The changelog at the bottom of this page is a record of that.
— CHANGELOG
Full codebase audit against design system, component, and content authoring standards.
Skills audit complete. All design system token violations, component pattern violations, and content authoring violations fixed across the codebase.
Jun 12, 2026