I'm Jacob. I design complex software from zero to one, then build it.

I brief AI like a new hire: clear scope, a first pass I push back on, then I own what ships.

1. Research

   I run raw interview notes and survey responses through Claude and ChatGPT to find what I'd miss reading them cold: the theme that repeats, the bias baked into a question, the structural problem hiding behind a feature request. Mobbin's MCP pulls in real product patterns for the same pass.

2. Explore

   Midjourney and Figma AI take me from a blank page to a wall of directions in an afternoon: mood boards, style studies, layout variations. I throw most of it away and develop the two or three that earn it.

3. Prototype

   Cursor, Claude Code and v0 turn a direction into something real: working frontend, not a flat comp. What I hand off clicks, scrolls and responds like the shipped product will.

4. Systems

   AI audits documentation, maps a component library and drafts hand-off specs faster than I can alone. It doesn't touch Auto Layout or rename a variable without me watching: that discipline stays mine. The system I built for ALT connects straight to Claude, so the team can keep building on it.

5. Build

   I build in code with Claude Code: this portfolio, the chat on it, Atlas Radio and Zinebin all came out of it. Codex built BonsaiQR with me.

6. Check

   AI's first pass is never the last one. I run accessibility checks, QA, code review and a pass through every detail by hand before anything ships. You can't fully trust the output, so I don't.

7. What stays mine

   Direction, taste and the final call, every time. AI fills gaps and moves fast. It doesn't drive.

ToolsClaude, ChatGPT, Claude Code, Claude Skills, MCP servers, Codex, Cursor, v0, Midjourney, Figma AI, Figma, Miro, Craft, Perplexity

Ask JacobLLM how I work ✦