2.3 Complete One Minimal Change and Learn 3 Common Types of Questions

Once the project is running locally, the most worthwhile thing to do right away is not to tackle a major change, but to first complete one very small modification. The smaller, the better. Change a welcome message, revise a self-introduction, update button text, or even just replace a heading with wording that sounds more like you. What matters most here is not how impressive the result is, but that you personally go through one complete loop: I propose a change, AI helps me make it, and the local page actually changes.

This loop is especially important for beginners, because it turns “local development” from an abstract concept into muscle memory. For the first time, you will clearly understand that continuing a project locally does not mean suddenly starting to handwrite large amounts of code. It can begin with a very small action. As long as you see the page change according to your intent, all the more complex changes that come later will have something to build on.

For your first change, the smaller the better

What I recommend changing here is not the structure or the functionality, but a piece of content where the change is very easy to see. For example:

• Change the homepage one-line introduction so it sounds more like you
• Replace default button text with something more natural
• Change the chat area prompt to a more specific sentence like “You can ask me what I’ve been working on recently”

Why keep it this small? Because what you are practicing right now is not the scale of output, but your feel for the process. As long as you have gone through one full round of “propose a change -> AI makes the change -> local page updates -> I confirm the result,” you will feel much steadier when taking on bigger things later.

A very practical first task

You can directly choose something at this level:

Please help me rewrite the homepage one-line introduction so it sounds more like me.
The target copy is: A content strategist learning to build products with AI.
Please tell me which file this copy is in, and only modify this one place. Do not change any other layout or styling.

This prompt is highly valuable because it includes three things at once: goal, scope, and constraints. For AI, this is far clearer than simply saying “help me change the homepage.” For you, it also trains a crucial habit: not giving vague instructions, but clearly stating the action.

These three types of questions will keep coming up

At this point, it is also a good time to establish three types of prompts that you will use repeatedly later.

1. Understanding: What is this project structure doing?

These questions help you quickly understand the map, so the project does not feel unfamiliar every time you open it as if it were your first visit.

Please explain the current structure of this project in plain language.
Tell me roughly where the homepage entry point, chat-related code, and style-related files are.
Do not go into too much detail.

2. Locating: I want to change X, where is the code?

These questions help you find the entry point before you actually start editing.

I want to change the one-line introduction in the homepage hero section and the primary button text.
Please first tell me which files these two parts are in, then give me suggestions for the changes.

3. Constraining: Only change this one part, do not touch anything else

These questions help you keep the scope under control, especially when you do not want AI to change too much at once.

Please only modify the prompt text in the chat box. Do not change the layout, do not add new modules, and do not adjust the color scheme.

You will notice that these three prompting patterns run through nearly all the chapters that follow. They are not flashy, but they are extremely practical, because they directly correspond to the three most common actions you will take as an independent vibe coder: understand, locate, and constrain.

If you want to make this section more solid

You can complete two small tasks in a row: first change one line of copy, then change one button or one section heading. As long as both rounds go through smoothly, you will begin to feel clearly that you are no longer “watching the platform perform,” but actually driving a project forward yourself.

At this point, you already have the core set of basic actions you will use most often for ongoing revisions later on.

---

Next: Chapter Summary: Your Local Workspace Is Ready →