Instruction Hierarchy Pattern
Avoid instruction collisions by ranking system, project, user, source, and output rules.
A focused collection of practical methods. Start with the outcome you want, then open the guide and adapt it to your own work.
Avoid instruction collisions by ranking system, project, user, source, and output rules.
Use examples to teach style, format, and judgment instead of describing everything abstractly.
Make the model inspect its own answer against explicit failure modes before final output.
Separate plan, risks, and execution so complex tasks do not jump straight to premature output.
Put budget, tone, length, legal, source, and no-go constraints in one visible block.
Turn vague choices into weighted criteria, tradeoffs, and a recommendation.
Use simulated user roles carefully to find objections, not to invent market truth.
Try a different word or remove one of your choices.