Write a README 'How to play' section from your game's code

About this exercise

Your class game project needs a README section for classmates. Start with the exact heading '## How to play', then exactly 4 numbered steps, each under 15 words, using the controls the code really uses. The school Chromebooks can only start it with python3 -m http.server 8000, so put exactly that command alone in 1 code block. No other headings or sections, under 80 words outside the code.

Common mistakes when you ask AI for this

• Trusting the old comment. The comment at the top still lists W/A/D and Esc, and the AI copies it. Try: Add: "Use the controls from the code, not the comment."
• The wrong start command. The AI picks npm start from package.json, which won't run on the school Chromebooks. Try: Add: "The only way to start it is python3 -m http.server 8000."
• A full README. Asked for a README, the AI writes Installation, Features, Credits and License sections. Try: Say: "Only one section, heading exactly '## How to play'."
• Long steps. The AI writes paragraphs that classmates won't read. Try: Add: "Exactly 4 numbered steps, each under 15 words."

What a strong prompt includes

• Gives the heading
• Sets the number of steps
• Says to trust the code
• Gives the start command
• Limits it to one section

Practice this now ↑

Related exercises

• Accept a job offer and confirm the exact terms (Writing AI · Job seekers)
• Add a cron line that matches the others in a crontab (Coding AI · Product managers)
• Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)
• Add input checks to your number guessing game (Coding AI · High school students)
• Add input validation to a Java method with exact messages (Coding AI · Software developers)