Free: all 16 prompts
Build real things with AI, not just a folder of demos.
I'm Jay Pozo. I build products with AI and I write down exactly how I do it: how I decide what to build, how I brief the model, how I split the work, and how I check it before anyone else sees it. That system is The Builder's Toolkit, and I'm publishing it as I go.
The first piece is ready: The Builder's Prompt Pack, all 16 prompts, in your inbox the moment you sign up.
The part nobody posts about
The model is rarely the problem.
A model will happily write code or copy for you. That part works. Builds fall apart somewhere else: the idea was never pressure-tested, the model never got enough context, the task was too big to get right in one pass, nobody reviewed the diff, and nothing was verified before it shipped.
Every one of those is a decision you make, not a setting you toggle. So this isn't another list of clever prompts to bookmark. It's the order of operations around them.
How it works
Five stages, in this order, every time.
Each stage has one outcome and produces something you can point at. Skip one and you usually find out two stages later.
Decide
You know what you're building, who it's actually for, and the smallest version that proves it works.
Prompts included, free, todayStill being documented: idea pressure-test, scope cut to one week.
Write the PRD
The build has a written spec, so the model stops guessing and you stop re-explaining yourself every session.
Prompts included, free, todayStill being documented: prd template, acceptance criteria.
Set Up the Agents
Your tools know the project: the rules, the file layout, the commands to run, and what finished looks like.
Prompts included, free, todayStill being documented: project instructions file, setup checklist.
Run the Loop
Work moves in bounded tasks. One change, one review, one verified result, then the next one.
Prompts included, free, todayStill being documented: task-splitting prompt, reviewer pass.
Verify and Ship
You check the work instead of hoping, then put it somewhere real where people can use it.
Prompts included, free, todayStill being documented: verification checklist, ship checklist.
The 16 prompts are finished and land in your inbox the moment you sign up. The templates, checklists, and annotated examples are what I'm writing up now, from builds in progress. There's no date, no pre-order, and no price on any of it yet.
Worked example
Votive, stage by stage.
Votive is an app I built with AI. It's the example I keep coming back to, because the interesting parts are the decisions, not the code. Here's what each stage actually looked like.
Stage 1
Decide
I wrote down what Votive had to do for the person using it and, more usefully, what it did not need to do in the first version. Most of that pass was cutting.
Stage 2
Write the PRD
I turned that into a short requirements doc: the screens, the rules, and what counted as done. It's the document I paste in when a session starts cold.
Stage 3
Set Up the Agents
Before asking for code I gave the tools the project: how the code is laid out, the conventions I wanted kept, and the commands to run to check their own work.
Stage 4
Run the Loop
Then one bounded task at a time. Ask for a single change, read the diff, send it back when the change reached further than I asked. Small tasks fail small.
Stage 5
Verify and Ship
The parts I could check automatically, I checked automatically. The rest I used myself on a real device before it went anywhere near other people.
What's inside
The Builder's Prompt Pack: 16 prompts, start to finish.
Not a sample. Not two prompts with the rest behind a wall. The complete set I use, covering the whole arc of a build. Every one is copy-paste, and anything in [BRACKETS] is yours to fill in.
Idea
Pressure-test what you're about to build, work out who it's really for, and cut it down to the smallest version worth shipping.
- 1Pressure-test your idea
- 2Design your this-week validation test
- 3Cut it to the smallest thing worth shipping
Build
Turn the idea into a plan you can work through, give the model enough context to be useful, and split the work into tasks that finish in one sitting.
- 4Pick your tool + model in 5 minutes
- 5Turn a vague idea into a build spec
- 6Give your AI a memory so it stops forgetting
Recovery
Read the error in plain language, find where the build went sideways, and get the one next thing to try instead of a wall of suggestions.
- 7Escape the doom loop
- 8Make a change without breaking everything else
- 9Make the AI explain code you can't read
- 10Verify a package before you install it
Shipping
Review what came back, check the parts that are easy to get wrong, and decide when it's good enough to put in front of a person.
- 11Get it live without "works on my machine"
- 12The 5-minute security pass
- 13Fix the domain / "not secure" error
- 14Switch payments from test mode to live
Launch
Say what you built in plain words, find people who already have the problem, and ask for the first real feedback.
- 15Get your first 10 users
- 16Write your launch post + one-liner
All 16 arrive in one document you can keep. The page above lists every prompt, not a sample.
How delivery works
One email address. All 16 prompts.
- You enter your email below.
- The Builder's Prompt Pack arrives right away, with a link to all 16 prompts.
- After that I send build notes when I have something useful, plus updates as more of the Toolkit gets documented. Unsubscribe from any of them.
Get the 16 prompts
Free, and the whole pack. Nothing is held back for a paid version.
About Jay
I teach from builds that are still in progress.
I've written software for years. AI didn't change what I know how to do, it changed how fast I can do it, and it got me through the parts I'm genuinely bad at, like design and marketing.
What I write here comes out of products I'm actively building, including the parts where I got it wrong and had to back out a decision. I'm not interested in looking like someone who never makes a mess. The method is more useful with the mess left in.
Questions
Straight answers.
- Is it actually free?
- Yes. All 16 prompts, sent as soon as you enter your email. Nothing to pay, no card, no trial.
- Is this only for coders?
- No, but I won't pretend it's effortless either. The prompts are plain English and you can use them the day you get them. Following the whole system through to a shipped product means learning some technical things along the way, and I explain them when they come up.
- What tools do I need?
- The process is tool-agnostic. It's about context, scope, review, and verification, which apply to any model or agent you're using. My examples reference the tools I currently build with, and you can swap in yours.
- Is The Complete Builder's Toolkit available?
- Not yet. I'm documenting it from builds that are happening right now, and I'd rather ship it late than sell you an outline. When it's finished and someone other than me has run it end to end, I'll say so.
- What happens after I sign up?
- You get one email with the 16 prompts. After that, I send build notes when I have something worth sending, and updates as Toolkit modules get finished. Unsubscribe any time.
The Complete Builder's Toolkit is the paid product I'm working toward. It isn't for sale and it has no price yet, so there's nothing to decide about it today.
Start with the 16 prompts.
The Builder's Prompt Pack, complete and free, in your inbox as soon as you enter your email.