Vague or generic output
Add a clear task, audience, context and output format. Start with Elements.
Stop collecting magic phrases. Learn to define the task, supply useful context, constrain the output and test whether the prompt still works on the next example.
JR Academy has 102 Prompt Engineering chapters. A flat directory makes the first decision harder, so this page identifies eight core gates and keeps the remaining lessons in a collapsible reference library. Every existing chapter URL remains unchanged.
Most users do not need an advanced framework first. Diagnose the output, then add only the missing structure.
Add a clear task, audience, context and output format. Start with Elements.
Add examples and a validation rule. Move to Few-shot and Evaluation.
Split it into a chain and keep each handoff inspectable.
Use one real task throughout the route. Each gate adds a reusable prompt, test result or safety rule to the same playbook.
Complete and save this evidence in the chapter workspace.
02 · StructureComplete and save this evidence in the chapter workspace.
03 · BaselineComplete and save this evidence in the chapter workspace.
04 · TeachComplete and save this evidence in the chapter workspace.
05 · ChainComplete and save this evidence in the chapter workspace.
06 · EvaluateComplete and save this evidence in the chapter workspace.
07 · ProtectComplete and save this evidence in the chapter workspace.
08 · StandardiseComplete and save this evidence in the chapter workspace.
The core route teaches the method. These entry points help you solve writing, extraction, coding, reasoning, image and Agent problems without browsing 102 titles.
Control audience, length, evidence and output shape.
REFERENCE ENTRYTurn documents into fields that can be checked or processed.
REFERENCE ENTRYSpecify environment, constraints, tests and acceptable changes.
REFERENCE ENTRYChoose decomposition and verification without requesting hidden reasoning.
REFERENCE ENTRYControl subject, composition, light, text and destination.
REFERENCE ENTRYKnow when a prompt is enough and when the system needs state or tools.
All existing chapters remain linked for search discovery and returning learners. Groups stay collapsed until you need them.
A Prompt Playbook records more than the final wording. It preserves the task, inputs, test cases, failure modes and handoff rules.
Yes, but the useful skill is no longer memorising keywords. Simple questions need less technique; structured output, batch processing, tool use and team workflows still need someone to design the task boundary, input sources, output contract and evaluation cases. This track teaches those transferable decisions.
No. Prompting is essentially describing tasks in natural language - the key is breaking down requirements clearly. However, knowing some JSON and API concepts helps when you reach the Agent and Tool Use sections.
Model-specific parameters and preferences change. The engineering decisions around task, context, constraints, output format, examples and evaluation do not disappear together. The track separates transferable methods from model-specific tactics; when you switch models, rerun the test set before tuning details.
Prompt Lab is an interactive practice area. Write a prompt for a defined task, inspect the result, then revise it against output format, factual and constraint checks. It is designed for method validation and does not require coding first.
The core route has eight gates. Practise one real task for 30 to 60 minutes a day, complete the foundation first, then open the writing, coding, image or Agent library when the work requires it. Completion means delivering a tested Prompt Playbook, not reading all 102 chapters.