Prompt structure
- Goal: desired task
- Context: relevant background/facts
- Constraints: what to include, avoid, or prioritize
- Process: checks/steps
- Output: format, length, audience
- Evidence: sources, quotes, or unknowns to disclose
Roles, examples, delimiters, and decomposition are aids, not magic syntax. Longer prompts are not inherently better. Change one element at a time where practical and record outcomes.
Weak prompt
Plan my concert night.
Stronger prompt
Plan for the supplied venue/date using verified facts. Prioritize accessible walking and public transit. Separate facts from suggestions. Label missing information unknown rather than guessing. Return a concise itinerary and verification checklist.
Context engineering
Select, organize, label, and update relevant input. Separate instructions from quoted data; specify which source controls conflicts; summarize long material while preserving caveats; verify retrieved information; label assumptions and stale facts. Avoid sensitive information unless an approved system and task require it.
Grounding does not guarantee source correctness.
Practice
Supply conflicting fictional schedules, specify the authoritative source, and test. Then reverse authority.