{"id":80089,"plugin_id":"plugins_6aea3d430b4c8191a4423700cf3bc0fa","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:14:25.293Z","digest":"de6dae41c408cff1295be541c661c4793719a98f486472155a78b0252498e9dd","against":null,"payload":{"description":"Turn a game concept into a playable loop, progression model, state transitions, and scoped acceptance criteria.","included_files":[],"name":"game-design","skill_md_contents":"---\nname: game-design\ndescription: Turn a game concept into a playable loop, progression model, state transitions, and scoped acceptance criteria.\n---\n\n# Game Design\n\n\n1. Define fantasy, player agency, target session duration, intended feeling, core verbs, reward signals, and failure/retry.\n2. Write a two-sentence **core loop**: player action -> world response -> reward/risk -> next decision. Avoid systems that do not reinforce it.\n3. Specify game states: launch, gameplay, paused, won, lost, restarted, saved/loaded when in scope. Define deterministic level/score transitions and scoring rules.\n4. Separate must-have vertical-slice mechanics from optional production expansion. Set one measurable completion condition for each.\n5. Model difficulty with observable parameters: time, speed, enemy cadence, spawn counts, health, level length; avoid promising game is 'fun' without human playtesting.\n6. Address onboarding, discoverability, feedback loops and accessible options. Use `../../references/gameplay-quality.md` and `../../templates/game-brief.md`.\n7. Produce a compact game-design spec, state chart in prose, feature priority and test criteria. If asked to build, pass to engine-specific workflow rather than stopping at design.\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":{}}