The 60-Prompt Starter Pack for Everyday Coding
by Laura Mbeki
Forty production-shaped system prompts for assistants, agents and internal developer tools.
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.
4 modules · 5 lessons · 40m 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.
1 lesson running 11m 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.
1 lesson running 8m 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.
4 modules · 5 lessons
40m total length
Short list, and deliberately so. If you meet these you can start today.
A system prompt is the part of an AI feature you cannot see in the screenshot and cannot skip in the build. This pack gives you forty of them, already shaped the way production system prompts end up looking after a few painful weeks: a role line, a hard scope boundary, an explicit refusal policy, an output contract, and a short worked example.
The templates cover the shapes developers keep rebuilding. A support assistant that must never invent a policy. A code explainer bound to one repository. A structured extractor that returns strict JSON. A triage agent that decides between three tools and stops. A migration helper with read-only access. Each one names its variables clearly, marks which lines are safety-relevant, and includes notes on what breaks when you delete them.
You also get the counter-examples: eight system prompts that look reasonable and fail in predictable ways, annotated with why. Reading those is usually faster than discovering the same failures in your own logs.
Delivered as Markdown, a Notion import and a YAML file suitable for checking into a repository. The access link is emailed immediately after checkout and includes every later revision.
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.
5.0
Rated 5.0 out of 5Course rating · 2 reviews
Ingvar Solberg
Platform engineer
Eight prompts that went wrong in production, printed with the transcript and the fix alongside. That section taught me more than the forty working templates did, because it shows you what a failure looks like from the outside before you have diagnosed it.
Sarah Whitmore
Software engineer
Our support triage assistant kept inventing ticket statuses that do not exist. One template plus the scope-narrowing advice on adapting it sorted the problem in an afternoon; on my own I would have iterated for days.
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