Your AI made an app.
Where do you start?
You know what you want to change, but not which file controls it. Ask your assistant to show you around before it starts editing.
Give your assistant one clear goal.
Start with your own app and a small change. For example: “I want to change the heading on my homepage. Show me which file controls it. Don’t change anything yet.”
Your assistant needs to see the project files. If it cannot open them, ask what it needs from you. Don’t share passwords, secret keys or someone else’s private work.
Ask. Look. Then make a small change.
Ask where the change belongs.
Tell your assistant what you want to change. Ask it to name the file and show you the part it plans to edit.
Check that you’re in the right place.
Open that file if your tool lets you. Look for words you recognize, such as your page heading. If you can’t find them, ask the assistant to explain before going further.
Try one change and look at the page.
Keep a backup. Ask for one small change, then open your app’s preview. Check what changed and what stayed the same. A message from the assistant saying “done” is not the final check.
Want a ready-made example?
Try a project estimate tool. You can enter your tasks, hours and rate, then copy or download an estimate. No install or code reading is needed.
Optional: inspect a small project and its code checks
This older teaching sample is a small task-list program, not a visual app. You can read its files without installing anything. Running its commands needs Node.js 22 or newer, a tool that runs JavaScript outside a browser.
Download the sample projectThe sample question
“Which file decides which tasks still need to be done?”
The answer is src/tasks.js. The program starts in src/index.js, then uses that file to choose the unfinished tasks.
export function unfinishedTitles(tasks) {
return tasks.filter(task => task.done !== true).map(task => task.title);
}
What the checks found
The supplied run has 4 tests passed, 0 failed. A test is an automatic check of one piece of behavior; four passing tests do not prove the whole app works.
From the extracted sample folder, the commands are:
node src/index.js node --test --test-reporter=tap
The program prints:
Read the project notes Find the entry point
A task still counts as unfinished if it has no “done” value. The checks include this case. The program does not save tasks or use accounts.
Read the saved test output
Executed with v22.23.4 Command: node --test --test-reporter=tap TAP version 13 # Subtest: keeps unfinished tasks, including a task without a done flag ok 1 - keeps unfinished tasks, including a task without a done flag --- duration_ms: 0.655166 type: 'test' ... # Subtest: omits a task explicitly marked done ok 2 - omits a task explicitly marked done --- duration_ms: 0.071114 type: 'test' ... # Subtest: handles an empty list ok 3 - handles an empty list --- duration_ms: 0.044895 type: 'test' ... # Subtest: does not mutate the supplied records ok 4 - does not mutate the supplied records --- duration_ms: 0.087525 type: 'test' ... 1..4 # tests 4 # suites 0 # pass 4 # fail 0 # cancelled 0 # skipped 0 # todo 0 # duration_ms 36.821009
This is a teaching sample with saved local results, not a customer story or a guarantee about your own app. Suggested checks count as done only after you run them and look at the result.
Keep the habit when you switch projects.
Confirm which app your assistant can see. Explain what you want, make a small change and try it. Start fresh with the new app’s files instead of assuming they match your last project.