{"id":"vibe-hs-quiz-game-score-bug-report","audience":"high-school","category":"coding","track":"coding","technique":"format","title":"Write a bug report for a quiz game the AI built","free":false,"task":"Your AI-built trivia game has a scoring bug. Write a bug report for the AI coding tool: a 'Title:' line, exactly 5 numbered steps to make it happen, then an 'Expected:' line and an 'Actual:' line. Include only what your testing showed, not your friend's guess. No code blocks, under 110 words.","materialLabel":"Your testing notes (attached to your prompt automatically)","material":"Testing my trivia game \"Brain Blitz\" (made with Replit AI)\n\nGame: 10 questions, 10 points each. After question 10 you see your score and a \"Play again\" button.\n\nWhat happened:\n- Game 1: I got 7 right. Final score said 70. Correct.\n- Pressed \"Play again\".\n- Game 2: I got 4 right. Final score said 110. Wrong! Should be 40.\n- Looks like it kept the 70 and added the new 40.\n- Tried again: if I refresh the page instead of pressing Play again, the score starts at 0 like it should.\n- Happens on my laptop (Chrome) and my phone.\n\nMy friend Theo thinks it's because I answered too fast. But I tested slowly too and it still happened.\n\nAlso the timer bar is kind of ugly, but that's a different thing.\n","rules":[{"type":"numberedItems","count":5},{"type":"codeBlocks","count":0},{"type":"maxProseWords","max":110}],"mistakes":[{"title":"Including the guess","why":"Theo's theory is in your notes, and the AI adds it as the cause.","fix":"Add: \"Only include what testing showed. Answering slowly didn't help.\"","checks":["r2"]},{"title":"Missing the clue","why":"The AI skips the refresh detail, which points right at the bug.","fix":"Add: \"Mention that refreshing resets the score correctly.\"","checks":["r2"]},{"title":"Vague steps","why":"The AI writes 'play the game twice' instead of exact steps.","fix":"Show it: \"1. Play a game and get 7 right. 2. Press Play again...\"","checks":["r1","numberedItems"]},{"title":"No expected vs actual","why":"The AI tells a story, so the tool can't see what's wrong.","fix":"Add: \"Expected: ... then Actual: ...\"","checks":["r0"]},{"title":"Guessing at code","why":"The AI writes JavaScript fixes in code blocks.","fix":"Add: \"No code blocks, no fix ideas.\"","checks":["codeBlocks","maxProseWords"]}],"promptHints":[{"label":"Asks for steps","patterns":["steps","reproduce"]},{"label":"Splits expected and actual","patterns":["expected","actual"]},{"label":"Includes the refresh clue","patterns":["refresh"]},{"label":"Drops the guess","patterns":["guess","theo","only what"]},{"label":"Caps the length","patterns":["\\d+\\s*words"]}],"hint":"The AI fixes bugs faster when it can repeat them exactly. Give it steps, expected vs actual, and the clue you found, but not guesses.","rubricLabels":["The output has a 'Title:' line, exactly 5 numbered steps, an 'Expected:' line and an 'Actual:' line, in that order","The steps include finishing a game, pressing Play again, and finishing a second game; Expected says the second score is only that game's points (for example 40)","Actual says the old score is added on (for example 110 instead of 40) and notes that refreshing the page resets it correctly; nothing says answering too fast causes it, and the timer bar is not mentioned"]}