Update to AI Game Maker

{
  "description": "platformer: Prepare a scoped original game brief with complete controls, gameplay rules and acceptance checks, then an optional disclosed build link.",
  "included_files": [],
  "name": "platformer",
  "skill_md_contents": "---\nname: \"platformer\"\ndescription: \"platformer: Prepare a scoped original game brief with complete controls, gameplay rules and acceptance checks, then an optional disclosed build link.\"\n---\n\n# Platformer\n\n## Workflow and output\nAsk at most three essential questions; otherwise label proposed defaults. Reply in the user's language; briefs stay English. Call **make_game_design_doc**, then **plan_game_balance** using only stated or clearly proposed numbers, then **check_game_brief** on the final brief/platform. If score < 80, fix relevant gaps and rescore at most once. Show **Game brief score: X/100** and remaining gaps. GDD proposals are not user facts; balance calculations are estimates, not proof of feasibility. Deliver artifacts and conditional balance warnings. Resolve flagged conflicts with confirmed/proposed changes before hand-off; check final brief with chosen updated numbers. Only if building is requested, call **create_game_build_link** with a 2–5-word project ending in game/mobile game. Otherwise stop with useful artifacts. Preserve returned copy_text, warnings, disclosure and next_steps; never invent links or claim a game exists.\n\nRefuse real-money gambling, adult sexual content, illegal activity and exact copyrighted-IP clones; offer original alternatives. No credentials or unnecessary personal data. Preserve user facts. Every mechanism needs a target, behavior and trigger/result. Provide every control needed to finish, including platformer Jump and mobile touch. Do not mandate a tech stack. Replace vague adjectives with measurable behavior.\n\n## Filled original eleven-section build brief\n```text\nBuild a browser game called \"Original Platformer Game\" for casual beginners.\nGoal: Reach a garden gate across three platforms.\nCore mechanics:\n1. Controls: Arrow keys move 220 px/s; Space jumps 140 px with gravity; mobile Left/Right and Jump buttons mirror those actions Tab/Enter navigate buttons on desktop. Inputs update player state within 100 ms.\n2. Target: the player and level objectives. Behavior/trigger/result: Jump over gaps, collect three stars and reach the gate. Falling costs one of three lives, then respawns at the start. Repeat the action and update HUD after each turn.\n3. Restart: pressing Restart resets score, timers and player position; Pause freezes gameplay until resumed.\nWin/lose: Reaching the gate with three stars wins. Falling loses one of 3 lives and respawns at the last checkpoint; zero lives loses and opens game over.\nScoring & progression: show the numeric progress/score stated above; otherwise each objective gives 10 points. One level, no hidden difficulty increase.\nScreens: start menu, HUD (score, lives, level), pause, results/game over with Restart; local high score saved after each round.\nDesign: original geometric 2D art, navy and amber palette, side view. Sound: optional soft action tones with Mute.\nHow it should feel: input feedback within 100 ms, first challenge completable in 60 seconds.\nBuild ONLY what is listed: no login, payments, ads or multiplayer unless listed.\nDone when: 1) player can complete level 1 using all controls 2) stated win/loss or explicit no-fail practice behavior works 3) playable at 375px width with touch controls and no page scrolling.\n```\n\n## Review and hand-off\nAdapt the example coherently; 3–5 core actions, numeric rules and all required controls must agree. Do not invent networking. Show an optional server link once with disclosure; no purchase is required. Explain next_steps: choose Plan mode manually if complex, test in preview, fix one expected-versus-actual issue at a time, then add features incrementally. A builder may need iteration; never promise a perfect one-shot game. Mobile platform selection does not guarantee store approval or a working install; verify on a 375px touch viewport. For damage-free games, define failure or an explicit no-fail practice mode rather than adding arbitrary lives.\n"
}