{"id":80090,"plugin_id":"plugins_6aea3d430b4c8191a4423700cf3bc0fa","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:14:25.306Z","digest":"6cd2c5dba2fb1c9207d595a4360ac642d5fc3095e52160b109a8aed544408781","against":null,"payload":{"description":"Build a playable game from a natural-language idea, organizing the core game loop, engine, assets, and actual verification.","included_files":[],"name":"game-from-idea","skill_md_contents":"---\nname: game-from-idea\ndescription: Build a playable game from a natural-language idea, organizing the core game loop, engine, assets, and actual verification.\n---\n\n# Game From Idea\n\n\n## End-to-end workflow\n1. Create a concise playable brief using `../../templates/game-brief.md`; require a player verb, challenge, feedback, success/failure condition, and restart. If missing, derive a minimal plausible version.\n2. Route through `select-engine` and record why the engine/platform is appropriate. Avoid automatic Unity/Unreal selection for simple browser games.\n3. Use `game-design` and `game-art-direction` to establish mechanics and coherent visual language. Define keyboard/gamepad/touch needs; accessibility; no mandatory network unless the concept requires it.\n4. Build the **first vertical slice**: launch/title or immediate start, core interaction, game state, a meaningful goal, failure/success, restart. Include pause and sound toggles where relevant.\n5. Add one level/scene, smallest useful content set, simple but consistent artwork, and feedback sounds. Defer large maps, shops, inventory, online accounts, and elaborate progression until the core loop is playable.\n6. Run a real executable smoke check if environment allows it. For browser games, capture browser errors and test keyboard/touch; for desktop use editor/headless checks plus interactive verification when available.\n7. Independently review against acceptance criteria, repair failures, then package source, setup instructions, build artifacts actually produced and evidence.\n8. When execution tools are missing, provide complete source files in a deliverable format where possible and clear unverified run instructions. Never report a functioning preview that wasn't run.\n## Deliverable contract\nProvide playable scope, engine, project tree, assets and licenses, implemented mechanics, controls, exact test commands and results, remaining defects and next expansion options. Read `../../references/testing-and-evidence.md`.\n\n## Execution truth and safeguards\n- A skill is an instruction workflow, not a remotely running game engine or a separately running AI agent. Inspect tools and repo state before claiming execution.\n- Preserve existing projects, names, dependencies, save formats, and user work unless a change is explicitly requested. Obtain approval for deployment, payments, destructive edits, publication, and major third-party connections.\n- Avoid reproducing protected commercial characters, levels, dialogue, soundtracks, logos, or copyrighted assets unless authorized. For assets, record origin and license. Read `../../references/security-and-rights.md`.\n- Report what was implemented, what was actually run, what failed, and what remains unverified; never describe proposed tests as passed.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}