The Practice
↓ Where Are You
Vibe Code with intention

If you can speak, you can code. Tell AI what you want to make. Ask questions. Give feedback until it feels right. That's it. That's vibe coding.

This guide helps you slow down so what you make actually feels like you.

Start with the pauses → Start where you are →
You are the creatorKnow before you buildStay at the centerShare from truthHow do you want this to feelYou are the creatorKnow before you buildStay at the centerShare from truthHow do you want this to feel
The Practice
Okie

Three pauses that keep you at the center.

Use them in sequence or jump to the one that resonates.

If you want to use AI to create something meaningful, your first job isn't to prompt. It's to arrive. Instead of letting AI take the lead, show up as the creative director and project manager: the one who knows what they want, how they want it to feel, and how they're going to get it done.

  • Inventory: Before you add anything new, collect what already exists. What have you made, written, said, or started that connects to this idea?
  • Reflect: Why can't you let this idea go? Why you, why now? How does this idea move you toward the world you want to inhabit? What do you want to change or make possible for the people you'll share it with?
  • Decide: Given all of that, what's the first thing to create? A resource, a website, an app, an experience? Get specific. The clearer you are here, the easier everything else becomes. If it's still not clear, spend more time reflecting.
  • Set the Vibe: How do you want this to feel for the person receiving it? Gather everything that captures that feeling: words, textures, colors, references, examples. Share it all with the AI so it really understands what you're going for.
  • Plan: Map out a timeline, then double it so it's spacious. Build a project tracker so you know what stage you're in and can see progress happening. Create a filing system with clear names so you can organize your outputs, especially the ones you may want to return to later.

Once you start, it is easy to fall into reaction mode with these tools: ask, receive, respond, repeat. But you do not have to move at the speed of the tool. How you feel in the process matters. The world you want to create for others starts now, in how you do this. It should feel good to make.

  • Pause: Everything on this site is an invitation to pause, but it's worth emphasizing here because it matters that much. Pausing is what keeps you in control. Between each output, stop and check in: Do I still feel good doing this? Am I still here? And if you feel foggy, overwhelmed, or just spent, stop altogether. The work will be there when you come back.
  • Feedback: Be specific about what is and is not working, ideally in plain, blunt language. Batch your feedback so you are not making one tiny change at a time. And instead of just reacting, ask for options. "This is what I want it to feel like/what I want it to do. Give me three ways to get there." That is the director move.
  • Redirect: If you have been going back and forth for a minute and it is still not landing, you might need to regroup. Go back to your original notes. Ask yourself what you actually want, for real. If the answer has changed, that is okay. Start again from there.
  • Save the Hits: The tools have memory, but it's unreliable and they produce so much that things get lost. If something lands particularly well — a sentence, a plan, a layout — save it somewhere outside the tool, ideally in the filing system set up in the Arrive step. That way you have what you need even when the tools go down or forget.

You made the thing. Now it is time to move it into the world. Some people share too fast, before it is really done. Others never share at all because something always needs fixing. This pause is about finding the place between those two: knowing when it is actually done and sharing it in a way that feels true to you.

  • Vibe Check: Before you call it done, step back and take in the whole thing. Do you recognize yourself in it? Does your body say yes? If something feels off, trust that and fix it. If it feels right, trust that too and move on.
  • Usability Check: Once it feels like you, there is the practical layer. Can people actually find it and use it? Think through things like your domain, links, mobile experience, meta description, OG image, and favicon. These steps take longer than you think. Leave enough time for them.
  • Claim It as Done: At some point, you have to make the call. If it feels good but you are still making changes, ask yourself honestly: is this making it better or just different? If it is just different, stop. Save those changes for version two.
  • Share: If going on Instagram makes you want to die, do not go there right now just because you made something. Think about the places that feel natural and good to show up in. Make a simple plan: where, when, how. Then share it. It may feel awkward. Do it anyway.
  • Let It Go: You made it. You shared it. That was your job, and you did it. Now release it fully. Do something special to celebrate. Get some good rest. And when you are ready, start making the next thing.
Where Are You Right Now?

Find the statement
that meets you.

Use the arrows to navigate.

01
I have too many ideas and don't know where to start.
Yes, that's me →

I have too many ideas and don't know where to start.

You're swirly. That's not an AI problem.

This is a discernment moment. Before you go to the tool, you need to sit with yourself. What do you actually want to make? Not what you could make. What is yours to make? What won't let you rest if you keep it inside? If you can't answer that, it's not time to build. It's time to write, talk, walk, dream. Let the thing find its shape in you first.

02
I know what I want to build but don't want it feeling AI-generated.
Yes, that's me →

I know what I want to build but don't want it feeling AI-generated.

Yes, listen to that. How do you want it to feel?

That instinct is your creative voice protecting itself. AI-generated feels like it could have been made by anyone, for anyone. So get specific. How do you want this to feel for the person receiving it? And how do you want to feel making it? Get clear on what you will let the tool help with and what only you will touch, like the stories you share or the examples you give. Write all of that down and bring it into every session. Let it ground every decision you make.

03
I started building but I keep getting lost in the process.
Yes, that's me →

I started building but I keep getting lost in the process.

You need to project manage.

Before you go further, build out your systems. A clear timeline, twice as long as you think so it's spacious. A project tracker so you can see where you are, what is done, what is next, and where you keep getting stalled. A folder with clear file names so nothing gets lost. The tool will forget things and fail at times. You are the one responsible for making sure this actually gets done.

04
I keep prompting and it's still not getting what I want.
Yes, that's me →

I keep prompting and it's still not getting what I want.

Something deeper may be off.

Usually, this means you are not clear enough on your vision to prompt well. Stop trying to prompt your way through confusion. Go back and clarify what you actually want. See if anything has changed. Be honest: this may not be the right time to make it, or it may not be yours to make after all. If you are clear and it still is not landing, your skills may need to level up. Learn from others how to use the tool better, then come back stronger. And if you are still getting nowhere, let it go for now. What is yours will come back.

05
I built the thing but I don't know if it's ready to share.
Yes, that's me →

I built the thing but I don't know if it's ready to share.

Do a vibe check. Then handle the practical.

First: does it feel like you? Do you recognize yourself in it? If something feels off, fix it before anything else. If it feels right, move to usability. Is it findable? Does it work on mobile? Is the domain clean? Is the link easy to share? You can also ask a trusted person to look at it, ideally someone who knows your vision well and can give honest feedback without leaving their fingerprints all over it. Then make the call.

06
I shared it and now I'm spiraling about how it's landing.
Yes, that's me →

I shared it and now I'm spiraling about how it's landing.

You did your job. Let it go.

The urge to check and refresh and see what folks are saying is natural. You just put something real into the world. But what happens next is not yours to control. Who finds it, how they receive it, what it becomes, all of that is out of your hands. Do not stress yourself out over metrics or reception. You followed through. That is the success. Go do something you enjoy.

01 / 06
If You Take Only One Thing

As you move through the process, keep asking yourself:

How do I want
this to feel?
Follow that.
Want More?
Full Version

Vibe Code Expanded Guide

A more detailed version of this with all the processes, prompts, and resources is in the works. Add your name to the waitlist to get an email when it drops.

Join the Waitlist →
Practice

Pause Between Prompts

A practice for staying yourself while using AI, and the larger home for the ideas on this page.

Explore the Practice →
Support

Creative Companion Sessions

Bring your idea, your questions, your stuck points. We'll figure it out together.

Book a Session →
Hey, Okie here. 👋 Okie

I'm not a software engineer or developer. I'm a contemplative and experience designer who got curious about AI and started using these tools to make things. If you're still like 'but who ARE you', here's my personal website :)

I've always wanted to create digital experiences (I really do love buying domains haha), but I used to get stalled when it came time to actually build the website. Now, because of vibe coding, I can finally make my thinking visible in ways other people can step into with this site being one example.

This changed everything for me, and I want to spread the gospel.

That said, the ideas in this guide are best suited for simple, accessible digital products. If you're building something that handles personal information, sensitive data, or advanced functionality, you'll need more skills and stronger security measures than this guide covers. The tools can help you figure out what those are, but it's good to know the limits going in.

As I encourage more people to use these tools, I am also grappling with the environmental and societal impact and I am still unresolved. These tools have changed my work and my life in real ways over the last couple of years, and I'm not going to pretend otherwise. But there is a real cost here that we do not fully understand yet. My current stance is to do my best to use them intentionally. Not just to make random things, but to make things that actually matter to me and that I believe make the world better. I reserve the right to change my mind. If I do, I'll let y'all know.

Lastly, this guide is a beginning. I'm working on a deeper paid version with more detailed processes, examples, prompts, and a full list of the tools I use. If you want that, join the waitlist at the bottom of the page. That will also motivate me to finish it.

Ok, enough framing. Close this and dive in!