cadence_learn
start_with_ai / level 08 of 10 · building ▶ 20 min

ship a thing people can use.

Every level so far made AI useful to you. This one makes something other people can touch. You'll describe a small tool into existence, share it with one person, and cross the line most people never cross: from user to builder.

after this level you'll be able to
  • Build a working interactive tool by describing it — no code
  • Iterate it like a builder: test, adjust, test again
  • Ship it — a link someone else can open, use, and react to
the whole idea

describing software into existence

the one sentence

Modern AI chats can build small working apps from a description — a quiz, a calculator, a decision-maker — live in the chat, shareable by link. The skill isn't code. It's describing what you want precisely — which is what you've trained for seven levels.

Ask your AI to "build an interactive quiz app" and it won't describe one — it will make one, running, right there (look for artifacts / canvas / apps in your AI's features). Buttons that click, scores that count. The gap between "I have an idea" and "try mine" has collapsed to one good description. What's left is the part that was always the real skill: knowing exactly what you want.

what to build

small, one job, for someone specific

Good first tools share three traits: small (one screen), one job (it does a single thing well), for someone specific (you know exactly who opens it and why).

too big for today

"A social network for my school." "An app like Spotify but better." Real ambitions — wrong first rep.

perfect for today

"A revision quiz for Friday's biology test." "A 'which film tonight' picker for my friends." "A split-the-bill calculator that handles the person who only had a starter."

do it now

build → iterate → ship

your turn 15 minutes
  1. Pick your tool — one of the three above, or your own (small, one job, someone specific).
  2. Describe it properly. Role, task, format — same recipe, bigger canvas:
    the build prompt — edit the bracketsBuild me a small interactive app: [what it is, e.g. a revision quiz for GCSE biology, topic: cells]. Who uses it: [e.g. me and two classmates, on our phones]. It should: [the one job, concretely — e.g. ask 10 multiple-choice questions one at a time, explain the answer after each, show a score at the end with what to revise]. Look and feel: [e.g. dark, bold, big touch-friendly buttons]. Build the whole thing working — don't describe it, make it.
  3. Iterate twice — like a builder. Use it for 60 seconds, then change what annoyed you: "the questions are too easy — pull from this material:" (paste your Level 03 notes) · "add a retry for the ones I missed." Watch it rebuild. That loop is what building actually is.
  4. Ship it. Share the link (or the screen) with one real person. Watch them use it without your help. Note the first thing they find confusing — that note is v2, and wanting to build v2 is the feeling this whole level was for.
say the words

"I built this." Not "I got AI to make this" — you decided what it does, who it's for, what was wrong with v1, and what v2 needs. That's the builder's share of the work, and it was all you. AI was the power tool.

level complete

three things to carry into level 09

01

Description is the skill

Precise wants in, working software out. Seven levels of prompting just became building.

02

The loop is the craft

Use it → find the annoyance → change it → again. Builders just loop faster.

03

Shipped beats perfect

One real user beats ten imagined features. Their confusion is your roadmap.

Stuck? Peter reads these personally and replies to your email.
Ask Peter →