From “I have an idea” to “here is the link”

A guided conversation, not a form. You talk about what you enjoy, what frustrates you and who else has that problem, until there is something specific enough to build.

• You end with: a project blueprint — problem, users, scope and what success looks like.
• Planned length: one sitting.
• The trap it avoids: picking a project so vague it can never be finished.

Features get proposed, and you cut them. Then the user journey, then the screens, then a working prototype you can click through, with every component explained in plain language.

• You end with: a running prototype and a walkthrough you can follow.
• You decide: which three features matter, and what the product is for.
• The AI does: the first draft of the build, which you then interrogate.

This phase is designed so that five people use it while you watch and say nothing. You find out which parts are obvious to you and nobody else, and you change the product rather than explaining it harder.

• You are meant to end with: a list of real problems and the fixes you chose to make.
• The skill: hearing criticism of your work without arguing with it.

This phase is designed to put your project online at a real URL. You are meant to learn what a deployment is, what can break in public, and how to put a change out safely.

• You are meant to end with: a live link you can send to anyone.
• The skill: shipping, which is the part most courses skip.

You are meant to write up what you built, record what you did yourself, and present it. Your project page is meant to become a credential anyone can verify.

• You end with: a public project page and a verification link for employers.
• The skill: explaining your own work to someone who was not there.