{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif6s4szxldu6k2jyncx3gpmpluk7drwgideago26zwyapgpi37lxq",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mqegcrbuyle2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreia554oshf44uuooueez63oqccbyw5e4rahkbjjhk57c4bmmkg7qyq"
    },
    "mimeType": "image/webp",
    "size": 77784
  },
  "path": "/git_blame_nobody/i-built-a-prompt-engineering-game-heres-why-i-think-learning-by-doing-beats-every-tutorial-1gki",
  "publishedAt": "2026-07-11T10:00:18.000Z",
  "site": "https://dev.to",
  "tags": [
    "ai",
    "webdev",
    "showdev",
    "javascript",
    "thepromptgame.vercel.app"
  ],
  "textContent": "\n\nEvery guide on prompt engineering teaches you theory.\nRead this, memorize that, here are 10 tips.\n\nThe problem? You never actually write prompts.\n\nSo I built a game: 10 challenges, each one forces you to\nuse a specific technique — zero-shot, few-shot, chain of\nthought, role prompting, constraints, and more.\n\nYou write a prompt → real LLM responds → second LLM\nevaluates whether you used the right technique. Not just\nwhether the output looks okay — whether your prompt\ncaused it correctly.\n\n**Stack** : Next.js 14, Groq, Supabase, Upstash Redis, Vercel\n\n**Try it free:** thepromptgame.vercel.app\n\nWhat technique do you think is hardest to learn hands-on?",
  "title": "I built a prompt engineering game — here's why I think learning by doing beats every tutorial"
}