UX
Flows, wireframes, audits, information architecture
- Figma, 7 years: Flows, wireframes, specs

- Miro, 5 years: Maps, audits, workshops

- Notion, 5 years: Specs and handoff docs

Of course. Here’s how.
Every day, as a tool rather than a shortcut: it drafts, checks and builds, and every decision about the product stays mine.
Generated screens come out generic: purple gradients, filler copy, no hierarchy. I rebuild the type, layout and states until the screen reads like a real product.
AI finds duplicate styles and drifting tokens; I decide what the system keeps. Change one token, and every component follows.
AI drafts the structure from a brief, I direct the flow and polish what people actually touch. A clickable prototype in an afternoon, not a sprint.
I ship interfaces as working code, not only Figma files: components with real states, built and deployed. This site is one of them.
Wireframes, user flows, case study write-ups and AI-assisted UX audits: contrast, tap targets and hierarchy checked before a line of code.
8 projects in Game UI
Flows, wireframes, audits, information architecture



Design systems, prototyping, visual design





Landings and web apps with specs developers can build



HUDs, inventories and menus for live 3D worlds



Interface motion, video and scenes





Where a model saves a day, not where it replaces a decision




So, shall we connect?