process
AI
figma
framer
01 — MVP
Starting in Figma, not on a template
Way back before Claude Design (a few months ago, so basically forever) I heard designers share their Figma space as a portfolio and it made sense. A template site would get me online faster, but building a prototype would show how I work and how I'd hand it off. Interactive components, animated details, the full picture. But it came with workarounds. I couldn't demonstrate responsive design, so I built a device selector instead.

02 — choosing the build tool
The learning curve that turned out to be a slope
I studied my options and decided to give Framer a shot. Three weeks of part-time building, watching tutorials and playing around — and the site you’re looking at was live. These animations were supposed to be 'too complex' to pull off without a full dev team, but Framer (and I!) proved them wrong.

As the site grew, so did the use. Now I work with Claude directly: building and editing components and handling site logic. Figma is still fastest for aesthetics and Framer to structure my vision. Claude I use for animations, interactions, anything code can do. I may pull those off manually, but when they need adjustments at multiple levels, Claude is just great. It hands me components and code ready to drop into Framer.
04 — on AI and intention
AI and choosing my battles
An open prompt can give interesting results, but an intentional one with a specific goal risks nonsense. To use AI with purpose, I pull from my art direction experience: discerning and articulating the specific nuances like textures, lighting, or subtext to make an outcome extraordinary. Knowing when to reach for AI, which model to use, and when to let go—that’s where it hits different.
ai
&
me
:
the
Practice














