Stage 3 · Lesson 5 of 7
Prompt templates for everyday tasks
Most of your prompts will be one of a few kinds: explain this code, fix this bug, add this feature, without changing behaviour. A template for each makes you include the context and the check every time. An explain prompt asks for an explanation plus questions to test you, and no code changes.
A bug prompt gives the symptom, expected behaviour and steps to reproduce, and asks for a failing test before the fix. A feature prompt is . A refactor prompt insists every existing test passes unchanged. Keep your templates in a notes file or save them as reusable prompts in your tool.
Common trapcopying templates from the internet that end without a check, so they produce confident code you still have to verify by hand.
A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- CoursePaidGrokking Prompt Engineering for Software Engineers
Design Gurus · Beginner · Subscription
A structured course on prompting for engineering work: specs, context, examples and iteration
- GuideFreeAnthropic Prompt Engineering Documentation
Anthropic
Free and model-agnostic in spirit: be clear and direct, give examples, let the model think
Keep handy
Also worth your time
When to plan, how to edit a plan, and starting over from the plan instead of patching