Designer's Claude Code Workflow

I’ve recorded 23 behind-the-scenes videos so far...

...totaling 22 hours and 42 minutes.

And I’m still not done. 😅

This is exciting, but also a problem.

Nobody needs 22 hours of raw footage dumped into their lap to learn from.

This has all been created in service to a fully functioning web app optimized with Claude Code and Figma

...and going back and forth.

And finally porting everything over into a fully native Swift-based iOS app.

Fun fact... last week I polled X and Instagram about their favorite app icon and #4 surprisingly won by a landslide.

I wanted to design and build a project from scratch.

Not only to showcase how I’ve been using this for my own projects, but to do it live and in a way that you can follow along.

So the project we build in the curriculum is buildable by you...

...with some guard rails and help along the way.

Using Figma Make etc. are good tools, and I still use them for small things...

but ultimately they are a harness on top of the base intelligence layer of Claude or similar.

That’s why I believe it’s important to learn and use Claude Code directly and intelligence layers directly...

...even though it can be a little more intimidating.

So in all of these videos I’m working through and showcasing:

I’ve been designing in Figma, pushing those designs and components into React components, pulling browser output back into Figma, designing in detail, testing on real devices, changing my mind and refining the interactions, and repeating that loop until the product feels right.

That’s the part that I really care about teaching.

Because it isn’t a straightforward linear process, and I wanted to have a real project that I built with my own hands as the foundation for teaching the material.

A lot of the videos that I’ve recorded so far are me talking through decisions in real time.

A lot of them have been me quietly designing and building for long stretches of time.

Some of them are sharp and useful, but most of them are messy and raw.

They are all super useful, but none of them should be the actual curriculum.

I’m working through all of the transcripts and polishing all of this into something much more digestible.

Every single day, the expectations of a designer using AI is increasing.

I’m feel very fortunate that I learned HTML, CSS, Sass, Pug, and JavaScript long before AI showed up...

...because it gives me an even better handle on thinking through prompting, documenting, designing, and coding with AI.

And ultimately a better handle on how to teach it as well.

The more clearly you can think about structure, behavior, systems, and intent, the more powerful these tools become in your hands.

So that’s what I’m in the middle of.

A Claude Code curriculum, yes...

But abstracting as much as possible into the idea of an AI-native design and build process.

So I'll end with a few questions for you...

I read every response.