Orchard Counting Adventure Game Builder Prompt

Use this orchard counting adventure prompt to create an original result with clear constraints, then review the output against the acceptance checks below.

This prompt asks a coding agent for a small early-math game. The orchard cover is concept art, not a tested screenshot. Review the activities with an educator before classroom use.

orchard counting adventure prompt

Build an offline-first browser game for ages roughly four to six called Orchard Counting Adventure. Make three short activities: count a set of 1–10 apples, drag the requested number into a basket, and combine two groups for sums up to 10. One activity should take under two minutes. Use large illustrated objects with enough spacing for touch, distinct shapes as well as colors, optional spoken instructions only if local speech synthesis is available, and no penalty timer. Feedback must show the correct counting method after an error rather than just saying wrong. Provide a start screen, adult-accessible settings for difficulty and sound, a simple progress summary and a reset button. Do not collect names, analytics or personal data; use only local storage for settings and progress. Implement keyboard navigation, clear focus states and a reduced-motion option. Keep all art original and avoid ads, accounts and network dependencies. Include a README explaining how counting problems are generated and a checklist for manual testing on phone and desktop.

Minimum acceptance checks

• Each count matches the number of visible apples, including after a retry.
• Addition answers and distractors are mathematically correct for sums to 10.
• A child can finish every activity using touch; keyboard use also works.
• No personal information or network request is needed to play.

Run and review the result

Test the visible object counts yourself, particularly when apples overlap or move. The generated game is a prototype until an educator checks clarity and age fit.

This page provides the build prompt and original concept art. It does not include a verified playable demo. Browse more AI Craft Pad prompts.

Five-step build and review workflow

1. Define the orchard counting adventure game goal, the player action, and the one mechanic that must feel good before adding more content.
2. Build a small playable opening area with visible controls, readable feedback, and a clear way to recover from mistakes.
3. Extend the same rules through the remaining scenes or levels, checking that art, input, and difficulty stay consistent.
4. Test keyboard or touch input, accessibility settings, save behavior, and offline loading where the brief requires them.
5. Play from a clean start through the ending, fix broken states, and package the source with honest run instructions.

When publishing the orchard counting adventure result, review keyboard controls and readable feedback with the MDN game development guide. Test the final output and revise any weak detail before reuse.