Prompt Engineering Fundamentals: Write Instructions Models Follow
by Laura Mbeki
Design tool schemas a model calls correctly, and handle the failures when it does not.
PR Created by Priya Raman
Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.
6 modules · 36 lessons · 4h 45m of material
6 lessons running 44m 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.
6 lessons running 50m 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.
6 lessons running 48m 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.
6 lessons running 52m 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.
6 lessons running 46m 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.
6 lessons running 45m 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.
6 modules · 36 lessons
4h 45m total length
Short list, and deliberately so. If you meet these you can start today.
A model that can only produce text is a very expensive autocomplete. Tool use is what turns it into something that can look things up, calculate properly, and change the state of your system, which is also exactly why it deserves careful engineering.
The course opens with the request and response cycle in detail: how a tool definition reaches the model, what a tool call looks like coming back, how results are returned, and how a multi-step exchange is assembled turn by turn. You implement the loop by hand before any framework appears, because debugging a framework you do not understand is miserable.
Most of the course is about schema design, since that is where correctness is won. Descriptions written for a reader who cannot ask a clarifying question. Enums that make an invalid call impossible. Required arguments that prevent silent defaults. Tools split by intent rather than by convenience. You will study why a model chooses the wrong tool and how naming, ordering and description length shift that choice.
The last third is failure engineering: malformed arguments, repeated identical calls, tools that time out, partial success, idempotency for anything that writes, and the difference between a tool that reports and a tool that acts. You finish with a working assistant that queries a database, calls an external API and refuses cleanly when it should.
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.
3.5
Rated 3.5 out of 5Course rating · 2 reviews
Ana Beatriz Moreira
Software engineer
Writing the loop manually before touching any SDK is the right way round, because you end up understanding what the abstraction is hiding from you. The highlight is the chapter where two similar tool descriptions get rewritten until the model stops confusing them.
Fionn Murphy
Backend engineer
Schema design and failure engineering are both worth the money. The multi-step section, though, keeps everything in one in-process dictionary and never addresses what happens when a tool call spans two requests or the worker restarts halfway through, which is the exact situation I am in. I bought this for that chapter and finished it with the same question I started with.
Applied AI and machine-learning engineer
Priya builds language-model features for a document-heavy SaaS product, which means she has taken retrieval and fine-tuning from a promising notebook to something on call at three in the morning. She teaches the mathematics only where it changes a decision you are about to make, and spends the rest of the time on data quality, evaluation and the cost of an agent that loops. Her courses run on a laptop and a modest API budget, so nobody has to rent a cluster to follow along. She publishes reproducible notebooks alongside every module.
One-time payment · lifetime access