저는 프롬프트 엔지니어링 게임을 만들었습니다. 모든 튜토리얼에서 비트 (Beat) 를 수행하여 학습한다고 생각하는 이유는 다음과 같습니다.

Every guide on prompt engineering teaches you theory.
Read this, memorize that, here are 10 tips.

The problem? You never actually write prompts.

So I built a game: 10 challenges, each one forces you to
use a specific technique — zero-shot, few-shot, chain of
thought, role prompting, constraints, and more.

You write a prompt → real LLM responds → second LLM
evaluates whether you used the right technique. Not just
whether the output looks okay — whether your prompt
caused it correctly.

Stack: Next.js 14, Groq, Supabase, Upstash Redis, Vercel

Try it free: thepromptgame.vercel.app

What technique do you think is hardest to learn hands-on?