Day 4 of 10 25 minGoalContextDone criteria
Good coding prompts read like a good ticket. State the goal, point to the right files, give constraints and examples, and say how you'll know it's done. Learn the pattern, then practise turning vague requests into precise ones.
By the end of today you can
- Use the four parts of a coding prompt, goal, context, constraints and done criteria
- Point the assistant at the right files, docs and examples
- Ask for a plan or questions before code on bigger tasks
- Iterate with specific feedback instead of starting over
- Recognise when to stop prompting and write the code yourself
What's inside
- 5 sections
- 2 diagrams and mind maps
- 5-question quiz
- 1The four parts
- 2From vague to precise
- 3Give it the right context
- 4Bigger tasks: plan first
- 5Iterate with specific feedback
Sign in free to read this lesson
Get the full lesson with diagrams, runnable code and the quiz. Your progress is saved across devices.
Sign in free