Hey, P2P’ers! 👋🏾 Before I tell AI, ‘Go fix it!’ 😂 I want to be clear about what I need and how we’ll know it worked. That’s where PPCD helps: • Purpose: What do I want to improve, and why? • Place: Where in the app should the change happen? • Click: What exactly should AI do? • Verified Done: How will we check the change worked? For example: ‘Make the sign-up button easier to see on the welcome screen. Keep the rest of the layout the same. Then show me how to preview and check it.’ Your turn: Pick one change you want to make and jot down its Purpose, Place, Click, and Verified Done.

Hey, P2P’ers! 👋🏾 When we’re building, it’s easy to spend all our energy on the app and then realize we’re not sure who to show it to. 😅 You don’t need a crowd to get useful feedback. Start with one person who has the problem your app is meant to help with. Give them one small task to try, then listen to what they say. Which part feels hardest right now: finding the right person, asking them to try your app, or knowing what to ask afterward?

What’s up, P2P’ers! 👋🏾 I wanted to see if I could get Claude Code to build something and have Codex check the work. So I gave them separate jobs, put them in the same workspace, and kept the final say for myself. Y’all, it worked! 😂 I turned that experiment into a free, eight-lesson mini-course. Professor Shay and Byte will walk you through setting up both tools, giving them their jobs, and checking the results yourself. We’ll start with one little test file so you can see the whole thing work. 👉🏾 Open the course in our Classroom Are y’all with me? 👀

Y’all, I saw a playbook with six things to think through before asking AI to build an app: 1. What should it do? What problem are you solving, and who is it for? 2. What does it need? Any tools or services it needs to work with? 3. What’s the flow? What does someone do first, next, and after that? 4. What should it look like? Think about the screens and how people will use them. 5. What information does it need to keep? This matters if your app saves things like accounts, payments, or user details. 6. What should we build and test first? A small first step can save a lot of backtracking 😂 Now, I’m not saying we need six fancy documents before every build. That can become a whole project by itself! 😅 But when Katy is ready to build from the prompt we give her, this list can help us check whether we’ve explained enough. We can ask her to organize the pieces we’re missing, review the plan, then let her build. For a small app, a few clear notes may be plenty. For an app that saves information or handles payments, it helps to think through those details first. Save this for your next build. Which one do you usually figure out last? Are y’all with me? 👀 Oh yeh, Katy is (LOVABLE)💜

Hey, builders! 👋🏾 When an AI makes a change and the screen still isn’t quite right, you don’t always have to start over. Show it the screen and point to one thing you want changed. ‘Keep the layout, but make this button easier to see.’ One clear adjustment gives you a better chance of getting the result you meant, without sending your app on a whole new adventure. 😂 What’s one screen in your app you’d like to fine-tune?