The first time something you built opens on a real URL, the room gets quieter. You did it. Screenshot. Share. That feeling is honest — and incomplete.

Live is proof you can leave the chat window. It’s not yet proof you can live in the workspace for days: clarify what you meant, watch something break, fix it where the files sit, push again, improve what people actually touch.

What “craft” looks like in an AI IDE

I’m not talking about memorizing every panel. Craft here is a habit: you don’t leave the room when it gets messy. You ask better questions. You let the agent work next to your files. You learn which breaks are yours and which are the environment. That only shows up if you return — evening after evening — to the same live thing.

If you’ve already felt that shipping itch without making “developer” your whole identity, you know the shape. The week is where that bias meets a harness deep enough to reward staying.

Why Cursor first

We teach on Cursor because it’s a clear room for that loop: agent, files, terminal, deploy path in one place. The point isn’t brand loyalty. It’s learning how to work with an AI IDE until the motions feel ordinary.

Those habits travel. Clarify before you assume. Stay with the break. Improve the live app, not a fresh toy every night. When you move tools, the craft goes with you — the furniture changes; the way you sit with the work doesn’t have to.

Studio evenings

Days 3–7 aren’t a second syllabus of slides. They’re practice on your live app. Studio evenings: improve what people can already open, get called up when you’re stuck, build a little in public so the loop isn’t private forever.

I’m not promising you’ll leave as a different person. I’m saying a week of honest practice — after the first ship — is how harness depth actually lands. Chat can write. A workspace ships. A week is how you learn to stay.