Structured Outputs and JSON Mode Without the Retry Loop
by Laura Mbeki
Understand why models drift, then write instructions that hold across a long conversation.
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 · 22 lessons · 3h of material
4 lessons running 32m 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 lessons running 40m 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 lessons running 42m 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 lessons running 34m 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 lessons running 32m 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 · 22 lessons
3h total length
Short list, and deliberately so. If you meet these you can start today.
Prompting looks like writing and behaves like engineering. The same request phrased two ways can produce a usable answer or a confident mess, and until you understand why, every improvement feels like luck. This course replaces the luck with a working model of what is happening inside the request.
You start with the mechanics that actually govern behaviour: the context window and what competes for space in it, how the system message differs from a user turn, why examples move behaviour more than adjectives, how temperature and sampling change the shape of an answer, and why long conversations drift as earlier instructions get outweighed by recent text. Everything is demonstrated live against Claude and ChatGPT with the transcripts shown in full, including the runs that fail.
From there you build technique. Role and scope framing, explicit output contracts, few-shot examples chosen to teach the edge rather than the average, decomposition of a large request into stages, and the specific instructions that make a model admit uncertainty instead of filling the gap.
The final module is about discipline: keeping prompts in files rather than in a chat history, changing one thing at a time, and writing down what you expected before you run it. Delivery is an emailed access link to the WisdomCharms library.
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
Rosa Villanueva
Software engineer
Choosing examples that sit on the boundary of a category rather than comfortably inside it is the single change that improved my results most. Three well-picked edge cases beat fifteen obvious ones and I would never have worked that out alone.
Thomas Ashby
Backend engineer
The output contract material is strong and it has become part of how I write every prompt. The chapter on drift diagnoses the problem well and then offers mitigations that amount to restating your constraints, which I was already doing before I bought the course.
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