Update to Design Game Studio

{
  "description": "Design and implement modular gameplay mechanics such as movement, combat, inventory, crafting, enemies, saving, and progression.",
  "included_files": [],
  "name": "gameplay-systems",
  "skill_md_contents": "---\nname: gameplay-systems\ndescription: Design and implement modular gameplay mechanics such as movement, combat, inventory, crafting, enemies, saving, and progression.\n---\n\n# Gameplay Systems\n\n\n1. Translate feature requests into player actions, game-state transitions, preconditions, feedback and outcomes. Define invariants for health, score, ownership, inventory or quest state.\n2. Keep systems separated where useful: input, rules, physics, rendering, audio, persistence and UI. Prefer engine-native conventions over custom frameworks.\n3. For movement, verify delta-time handling, jump/coyote time if appropriate, camera behavior, collisions and boundaries. For combat, model damage, invulnerability and death/retry.\n4. For inventory/crafting, validate capacity, duplicate handling, resource costs and failure states. For saves, version data and check missing/corrupt files.\n5. Use `../../references/gameplay-quality.md` for tuning and `../../templates/acceptance-checks.md` for mechanical test cases.\n6. Implement one complete mechanic at a time; test edge cases then integrate it into a level that demonstrates it.\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"
}