The 60-Prompt Starter Pack for Everyday Coding
by Laura Mbeki
Nine end-to-end workflows taking a ticket from vague request to reviewed pull request.
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 · 11 lessons · 1h 25m of material
2 lessons running 12m 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.
3 lessons running 24m 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 · 11 lessons
1h 25m total length
Short list, and deliberately so. If you meet these you can start today.
Single prompts are easy. Getting a whole feature out of the door with a model beside you is a different discipline, and it is mostly about sequence. This pack is nine complete workflows, each a numbered chain of prompts with a clear stopping point and a checklist of what should exist before you move on.
The workflows cover the shapes that repeat: turning a two-line ticket into a specification with open questions, designing a small API before writing it, adding a field end to end through schema, model, validation and interface, writing a migration with a rollback, tightening error handling, preparing a pull request description, reviewing your own diff before a colleague sees it, drafting release notes, and writing the incident note when something goes wrong anyway.
Each step names its inputs, so you always know what to paste. Each step also names its failure mode, so you know what a bad answer looks like before you accept it. Two of the workflows include hand-off notes for pairing with a teammate midway through.
Eleven recorded lessons run the workflows against a small web application. The whole pack arrives as an emailed access link, in Markdown, Notion and plain text, with a printable checklist card.
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
Rebecca Osei-Bonsu
Tech lead
The claim is that the order you ask for things matters more than how you word them, and after a month of working this way I think that is right. Ticket to specification, specification to design, design to diff. Each step on its own is unremarkable and the compound effect is not.
Stefan Kraus
Senior developer
Nine workflows and I honestly use two of them. But the migrate-and-roll-back one has been valuable enough on its own: being forced to write the reversal before the change is a habit I should have picked up years ago. The other seven were not for me.
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