Quizforge
Turn any lesson plan into a quiz your class can play on phones
About
Paste a lesson plan or a page from the textbook and Quizforge writes a ten-question quiz at the right level. Students join with a code and play on their phones. The teacher sees who struggled with which question.
Used in 70 Danish classrooms. Built by a teacher with no coding background.
How it was made
Shared by the maker. Numbers are their own estimate.
- Build time
- 3 weeks
- AI spend
- $55
- Prompts
- ~190
- Written by AI
- 100%
Agents
Lovable
88% of the workThe app
Claude
12% of the workQuestion writing rules
Build recipe
The code isn’t public. This is the whole project as one prompt: paste it into your own agent to build the same thing.
Written by Claude
From the project’s code and history · 355 words
Build a web app called Quizforge: turn any lesson plan into a quiz your class can play on phones.
What it does
Paste a lesson plan or a page from the textbook and Quizforge writes a ten-question quiz at the right level. Students join with a code and play on their phones. The teacher sees who struggled with which question.
Stack
Use React, Supabase. The original was built with Lovable and Claude in 3 weeks, for about $55 in AI usage.
How it fits together
- A server-rendered web app with a small API layer
- A database for user data, with row level security on every table
- Sign-in so each person only sees their own data
Build it in this order
- Set up the project, the database and sign-in, and deploy an empty page
- Build the main screen with realistic sample data
- Connect it to real data and add the one action the app exists for
- Add the empty states and error messages a new user will hit
- Write tests for anything that touches money, dates or other people's data
A prompt that worked: Questions at the right level
From the lesson text below, write 10 multiple-choice questions for students aged 12–13. Mix: 4 recall, 4 understanding, 2 ‘apply it’. Wrong answers must be plausible mistakes a student would really make, not silly options. Keep questions under 20 words. Return as JSON.
Watch out for
- Don't build settings, teams or billing before the main screen works
- Keep the first screen useful with sample data, so the app makes sense before anyone has set it up
Done when
- A new user can sign in and get value in under two minutes
- Everything works on a phone
- Tests pass for the core logic
Before writing code, ask me up to five questions about who this learning web app is for and what the first version must do. Then work in small steps: after each one, tell me how to try it and wait for my feedback.
Discussion
3 comments · 1 built their own
Built my own version from the recipe in an evening. The build log is the most useful part for me, I'd love more detail on how you structured week two.
- Lena Vogt6 hours ago
Love how focused this is. One thing: the empty state took me a second to understand. Maybe show an example right away?
More like this
Paste a README, get honest notes on what a stranger won't understand