route /practice

Practice

The tools aren't the story. The story is the loop: how a design gets specified, built, and kept in sync with the code that ships it.

Stack

Interface & UIFigma · Adobe XD · Design systems · UI and UX design · Prototyping · Coded prototypes on Vercel · Responsive web design · Accessibility-aware design

Build & ShipHTML5 and CSS3 · Webflow · WordPress · OpenCart · Shopify

Design & BrandIllustrator · Photoshop · InDesign · Lightroom · Visual identity · Art direction · Typography · Print production

Motion & VideoAfter Effects · Premiere Pro · Cinema 4D · Post-production for web and paid social · Motion built in code nowadays too

AI in practice

Design to build

I run Claude connected to Webflow, Vercel and Figma. Most days the idea starts in Claude — I describe what I want, and an MCP connection builds it as a real file in Figma: frames, components, variables. It runs the other way too, a design that already exists in Figma pushed into a live build on Vercel, or pulled back from one. The biggest test of that loop so far: rebuilding a whole design system — components, variables, the lot — starting from a live Vercel project and reconstructing it piece by piece inside Figma.

Prototyping

I test ideas as working HTML rather than as static mockups — Claude Code mostly, other models through Antigravity or Hermes when they suit the task better. Quicker to judge, and quicker to kill. Coded prototypes get deployed to Vercel so they can be opened by a link.