Prompt Engineering Guides
Writing prompts that get consistent, useful output instead of plausible noise.
Prompt engineering basics that actually change the output
Most prompt advice is folklore. These five techniques reliably change what a model produces, and it is w...
Read guideDebug a prompt that worked yesterday and does not today
When a reliable prompt starts producing rubbish, the instinct is to rewrite it. That is usually the last...
Read guideWrite a reusable prompt template your whole team can use
A prompt that only works in your hands is a prompt with your context silently baked in. Making it portab...
Read guideWritten to be followed, not skimmed
Every guide here is a procedure someone actually ran, with the steps, the time it takes and the places it goes wrong.
Numbered steps, not prose
Each guide breaks into steps with their own anchor, so you can send a colleague straight to step four. Those anchors are minted once and never move.
Levels you can read without colour
Beginner to Expert, shown as filled pips as well as a label, so the level survives a screenshot, a colourblind reader and a printout.
An honest time estimate
The minutes on each card are the sum of its steps, not a reading speed. Guides without an estimate sort last rather than first — an unknown length is not a short one.
Freshness that means something
“Updated” moves only when a person changed the content — never when someone read it. Sorting evergreen guides any other way ranks whatever was most recently opened.
Filters that admit when they are empty
Every count is measured with your other filters applied, so the number beside an option is what you will actually get. Options that cannot narrow anything are not offered.
Prerequisites up front
What you need before you start, and what you will be able to do at the end, are stated before the first step — not discovered halfway through.
