All terminal, all live. Same setup as Ollama PlaygroundExtraction Warm-UpCompliance QA Playground: ollama run llama3.2 (or any model you like) in a terminal tab. This page is templates and challenges to fill in with your own ideas — the notebook has the worked examples if you want to see answers first.
1. Prompt Pattern Templates — Copy, Paste, Fill In
Five reusable skeletons. Swap anything in CAPS for your own idea, paste into ollama run <model>, see what happens.
Zero-shot:
TASK. Respond in exactly FORMAT. CONTENT TO ACT ONFew-shot:
TASK DESCRIPTION. EXAMPLE INPUT 1 EXAMPLE OUTPUT 1 EXAMPLE INPUT 2 EXAMPLE OUTPUT 2 YOUR REAL INPUTChain-of-thought:
YOUR QUESTION OR PROBLEM Think step by step, showing your reasoning, then give a final answer clearly labeled.Role / persona:
You are a ROLE. Your tone is TONE. ADDITIONAL CONSTRAINT. YOUR REQUESTReflection (2 messages, same session):
>>> YOUR QUESTION (read the answer, then in the SAME session:) >>> Double-check your answer above for errors. If anything is wrong, correct it. If it's right, say so.2. Zero-Shot Sandbox 5 min
Pick a task nobody at your table has tried yet. Write it zero-shot first — no examples, no hand-holding.
>>> Classify this tweet as Positive, Negative, or Neutral: "..." >>> Write a product name for a reusable water bottle aimed at hikers. >>> Extract the date, location, and event name from: "..." >>> Rewrite this sentence to be more formal: "..."Now break it on purpose: pick one of the above and feed it something ambiguous or borderline (a genuinely mixed-sentiment tweet, a sentence with no clear date). Does it pick a reasonable interpretation, or does it ask you for clarification? (Most local models won't ask — they'll just guess. That's the tell.)
3. Few-Shot Builder 8 min
Take whatever zero-shot task you just broke above. Fix it with 2–3 examples of your own, using the few-shot template from Section 1. Specifically design your examples to cover the ambiguous case you found — that's the actual skill here, not just "add examples."
Then try this failure on purpose: write 2 examples that quietly contradict each other (e.g., two examples of borderline reviews labeled opposite ways for similar reasons). Does the model get confused, average them out, or just pick one pattern and ignore the other? There's no fix step here — just observe.
4. Chain-of-Thought Sandbox 8 min
Write or find your own multi-step riddle, word problem, or logic puzzle — something with at least 2 steps to get right. Classic sources: age/ratio word problems, "who is lying" logic puzzles, unit conversion chains.
>>> YOUR RIDDLE Answer with just the final answer. (note the answer, then:) >>> YOUR RIDDLE Think step by step, then give the final answer.Did chain-of-thought change the answer? If both were already right, your riddle wasn't hard enough to show the effect — make it harder (more steps, more red herrings) and try again.
5. Reflection in One Session 6 min
Key mechanic to notice: unlike the notebook (which makes separate, stateless API calls), ollama run's interactive chat keeps the whole conversation in context automatically. That means reflection is just... asking a follow-up question in the same window.
Try this on a topic you genuinely know well (your hometown, your major, a hobby) so you can personally judge accuracy without looking anything up. Then try /clear and ask the reflection question cold, with no first answer in context — notice it has nothing to "reflect" on anymore. That's the whole mechanism laid bare: reflection only works because the first answer is sitting right there in context to be re-examined.
6. Failure-Mode Challenges — Try to Break It 10 min
No template this time. Each card is a goal — you write the prompt. If you succeed on the first try, your prompt wasn't adversarial enough; try to make it fail worse.
Make it give you invalid JSON
Ask for structured output, but leave the format instruction vague or buried in a long request. Then verify: would json.loads() actually parse what you got?
Make it agree with something false
State a wrong "fact" as if you're certain of it, then ask a question that assumes it's true. Does it correct you, or build on your false premise?
Give it 6+ instructions in one paragraph and see how many survive
Bury the instructions in natural prose (not a numbered list). Count afterward: how many of your 6+ requirements actually show up in the output?
Give it an instruction with no clear referent
Something like "fix the second one" or "make it more like the other style" with nothing established earlier in the conversation for "the second one" or "the other style" to point to. What does it invent to be helpful?
Ask for something specific enough that it can't possibly know it accurately
A statistic, a citation, a very recent event, an obscure combination of facts. Does it hedge honestly, or answer with confident, specific-sounding, made-up detail?
Compare notes with your table — did everyone's model fail the same challenges, or did some models resist things others fell for?
7. Prompt Battle — Two Models, Same Prompt 5 min
Open two terminal tabs side by side:
# tab A ollama run gemma2:2b # tab B ollama run qwen2.5:7b # or llama3.2, phi3:mini — whatever else you havePaste the exact same prompt into both — ideally one of your Section 6 challenge prompts. Does the bigger/different model resist an attack the smaller one fell for? Does either one surprise you by failing something the other got right?
Wrap-Up
Write down, in one sentence each: (1) one prompt pattern from Section 1 you'll actually reuse, and (2) one failure mode from Section 6 you managed to trigger, with the exact prompt that did it. Bring both to the next session — Week 3's applied prompting work (slides-week3.html) and the Agentic Systems reflection material build directly on what you find here.