From the course: Getting Started with Vibe Coding

Adding structure to the vibes

From the course: Getting Started with Vibe Coding

Start my 1-month free trial Buy for my team

Adding structure to the vibes

“

- There are many different ways to add structure to vibes. Here, I'm going to show you one where we have three documents: a specification, a blueprint, and the to-dos. I'm going to share all three of these with you and a shared GitHub, so you can code along with me on this journey of building a prototype application. So we have specification, blueprint, and roadmap. We'll always start with the specification, which covers the what. What are we trying to build? In that process, we'll do a reverse interview with AI. AI will ask us questions, and it'll extract out our ideas from our head, making something that's implicit explicit. Once we've done the reverse interview with the AI, we're then going to have a long conversation of what we're trying to create, the what. We'll then synthesize that into a specification with the help of AI. So we'll have a document that is something we can pass off to an AI to build. So that's the first step, specification. So the second step is the blueprint. So this is the how. How are we actually going to build the specification? In this step, again, we're going to use AI to assist us. So we're going to take the spec as the starting point, and the AI will use that specification as a ingredient to then build the overall blueprint, which is going to be another markdown file. So that's our second piece. And then our third piece is a roadmap. So this is going to act as a checklist. So it's going to be a bunch of to-dos that our AI is going to reference throughout the building process to know exactly what it's done in the past and what it's going to do in the future. Now that we understand the three documents and their importance, let's move forward with planning our application.

Contents