Skip to main content

What I use

AI Workflow
Claude

My main thinking tool. Architecture decisions, component logic, copy iteration, debugging. This entire portfolio was built with Claude Code. Not just assisted, actually built.

Cursor

Where the code actually gets written. I write less, review and guide more. The autocomplete changed what's possible as a solo designer who codes.

Design
Figma

Still where every project starts. Components, layouts, interactions. What changed isn't the start. It's the exit.

FigJam

System diagrams and flow mapping. Thinking before I touch a frame.

Development
VS Code

Where I still live for heavier projects. Extensions, settings sync, and the baseline that Cursor is built on.

Next.js (App Router)

The only framework I've shipped with in 2+ years. Server components and file-based routing are the right defaults.

Tailwind CSS

Design tokens as utilities. Consistency and theming without the fight.

shadcn/ui

Copy-paste component library built on Radix UI. The best Figma-to-code component system I've found.

TypeScript

Catches what I miss. Worth the setup every time.

Vercel

Push and it's live. Zero config, zero ops.

GitHub

Version control for decisions, not just code. Commit messages are documentation.

Writing & Thinking
Obsidian

Primary second brain. Long-form thinking, knowledge graphs, connected notes. Where ideas actually live.

Notion

Secondary: projects, writing drafts, frameworks. Good for structured lists, not for connecting ideas.

Kindle

Always reading. Non-fiction mostly, on design, systems, behavior, money.

Currently Exploring
AI-to-component pipeline

Testing where the Figma → AI → production workflow holds and where it breaks down.

Motion in code

Where Framer Motion and CSS transitions overlap. Building interactions directly instead of prototyping them.

Inspired by uses.tech, a community list of /uses pages.