How to start (the practical version)

From zero to a running app you did not write by hand. Budget about 30–60 minutes for your first project.

What you need to start

1. 1

   Pick a tiny idea you actually want

   Something small you'd use yourself, that can be finished in an afternoon. Examples: a bot that reminds you to drink water, a page that tracks a hobby, a small tool for a repetitive task. Avoid 'an app like Instagram' for your first try.

   Tip: If you can describe it in one sentence, it's the right size.

2. 2

   Get an AI account with token billing

   Create an account on an AI provider (e.g. one that supports coding agents), add a payment method (pay-per-token), and create an API key. You pay only for what you use — a small project costs a few dollars at most.

   Tip: Keep the key somewhere safe. You will NOT paste it into the AI chat.

3. 3

   Install an editor and a coding agent

   Install VS Code (free) from code.visualstudio.com, then add a coding agent. Two easy paths: a CLI agent like Claude Code or Cline, or a desktop AI app (ChatGPT / Claude desktop) that can read/write files in a folder.

   Tip: Most first-timers do fine with just a desktop AI app and no terminal.

4. 4

   Create a folder and write your rules

   Make a new folder for the project (e.g. ~/water-bot). Create a file called RULES.md in it and paste the starter prompt below. This is your 'master prompt' — the agent will follow it in every step.

   Tip: Save a copy of the rules: you'll reuse them and share them later.

5. 5

   Give the first instruction

   Tell the agent: open the project folder, read RULES.md, and follow it from step 1. Don't code anything by hand — let it create the files.

   Tip: Example: 'Start. Read RULES.md and build the first working version.'

6. 6

   Run what it built and test it

   Ask the agent how to start the app, then run the command it gives you (often something like npm run dev or docker compose up). Open it in the browser and actually try it.

   Tip: If it errors, paste the error back — let the agent fix it.

7. 7

   Iterate with feedback

   Test, then tell the agent what to change ('make the reminder send a second message at 18:00', 'the button is too big'). Each round is a few minutes.

   Tip: One request at a time keeps it fast and predictable.

8. 8

   Track the cost and share it

   Keep an eye on your provider usage. When it works, submit it here so others can copy your rules and see what it really cost.

   Tip: A card is just idea + demo + rules + token cost.

# Project rules (paste into RULES.md)

## Role
You are the Lead Engineer. I am the Product Architect: I describe what I
want and give feedback. I never write code by hand.

## Project
[One sentence: what you want to build.]

## Constraints
- Minimal, working first version in this session.
- No secrets in code: use a .env file for keys.
- Explain what you will do, then build file by file.
- After each step, tell me exactly how to test it (one command).

## Done
The app runs and I can see/use it.