Build your first project

Create a small project with a defined goal, files, acceptance checks and a finish line.

Beginner note

A README is a plain-text project guide, usually saved as README.md. It explains what the project is and how to work with it.

Understand

What this step is for.

Small first projects teach more than ambitious prompts. Define a narrow user problem, a few files and objective checks. Avoid asking AI to build a complete app without acceptance criteria.

Keep the scope small enough that you can inspect the result yourself. AI can accelerate the work, but it should not erase the distinction between a suggestion, a changed file, a successful build and a verified product.

Do this

Take one concrete action.

Create a project with a README containing Goal, Non-goals and Done when. Build one visible feature. Test it manually and record the result.

Beginner walkthrough

Build a complete two-file project you can copy exactly

Create Documents\my-first-ai-project. Create README.md containing:
Goal: Show a page with a working button.
Non-goals: Accounts, database, internet connection.
Done when: Clicking the button changes the message to It works.

Create index.html and paste:

<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>My first AI project</title>
<h1>My first AI project</h1>
<button id="test">Test it</button>
<p id="message">Not tested yet</p>
<script>
document.querySelector('#test').addEventListener('click', () => {
  document.querySelector('#message').textContent = 'It works';
});
</script>
</html>

Save both files, double-click index.html, then click Test it. “Not tested yet” must change to “It works”. Add Result: PASS to README.

Safe follow-up: change only the button text from Test it to Run test. Save and refresh. Confirm the new button text appears, click it and confirm the message still changes to It works. If either check fails, undo only that text change and save again.

Success: the acceptance test still passes after one small reversible change.

Practice

Turn the idea into evidence.

Ask another person, or yourself after a short break, to read only README and test the page. Record whether the stated Done-when condition is obvious without extra explanation.

Verify

Do not move on until this is true.

A fresh person could read the README and determine whether the project meets its stated finish line.

From Nyfir Studios

Why we use this principle.

Nyfir Studios treats generated output and verified output as different states. Development work on local AI, Android software and bookkeeping workflows has repeatedly shown that recoverable state, explicit tests and clear product status are more useful than simply producing more output.

← Previous Next step →