Structure first.
Interface second.

I’ve spent my career in products where the details carry real weight.

Banking, payroll, web3 — domains where a confusing screen isn’t an annoyance, it’s a support ticket, a compliance question, or somebody’s money. I design the structure first and the interface second, and because I write front-end code, what I hand off is what ships.

• Turn fuzzy requirements into flows engineers can build
• Design systems that still hold up ten features later
• Prototype in code when a picture isn't enough
• Sweat the states nobody screenshots — errors, edge cases, empty screens