The 60-Prompt Starter Pack for Everyday Coding
by Laura Mbeki
One hundred and twenty prompts that turn untested code into a suite you can trust.
LM Created by Laura Mbeki
Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.
5 modules · 9 lessons · 1h 10m of material
1 lesson running 7m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
2 lessons running 14m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
2 lessons running 16m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
2 lessons running 18m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
2 lessons running 15m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
5 modules · 9 lessons
1h 10m total length
Short list, and deliberately so. If you meet these you can start today.
Models write tests eagerly and badly. Left alone they produce a wall of assertions that all pass, cover the happy path twice, and mock the very thing you needed to verify. This library exists to get useful tests out of them instead.
The one hundred and twenty prompts are organised by what you are trying to protect: pure functions, code with time or randomness in it, HTTP boundaries, database access, background jobs, and legacy code with no seams at all. For each situation there is a prompt that first asks the model to describe the behaviour in words, then to list the cases worth testing including the unpleasant ones, and only then to write code. That order is the whole trick.
Python examples use pytest, TypeScript examples use Vitest, and both sets include prompts for property-based thinking, fixtures that do not turn into a second application, and turning a real bug report into a regression test. There is also a set for the opposite job: reading a test suite you inherited and asking the model which tests are lying to you.
Nine recorded lessons apply the library to two small codebases. Everything is delivered by an emailed access link, in Markdown, Notion and plain text.
Still unsure about something? Write to misteryjj100@gmail.com and a human answers, usually the same working day.
Reviews are written by people who bought this course. We publish the critical ones too.
4.5
Rated 4.5 out of 5Course rating · 2 reviews
Julia Marchetti
Backend engineer
Ask a model to write tests for a file and you get assertions that mirror the implementation line for line. Make it enumerate behaviours, then cases, then code, and you get something that would genuinely fail if the logic broke. Same tool, completely different result, purely from the ordering.
Kasper Lindgren
Full-stack developer
The Python side is excellent, especially the fixtures and the material on cutting a seam into legacy code. The TypeScript prompts read as though they were written second: nothing on typed mocks, and barely an acknowledgement that runners other than Jest exist.
Prompt engineer and AI workflow designer
Laura went independent after seven years of agency work and now designs the prompt libraries that sit behind other people's products. She treats prompting as engineering: versioned prompts, a held-out evaluation set, a regression run before anything ships, and a token budget you have to hit. Her packs are the ones she uses with her own clients — briefing, rewriting, summarising, review — rather than sanitised examples, and each comes with notes on where it fails. She keeps every pack working across ChatGPT, Claude and a small open model, so the technique outlives the model.
One-time payment · lifetime access