Update to Design Game Studio

{
  "description": "Verify gameplay, usability, performance, bugs, and game feel through measured playtests and reproducible evidence.",
  "included_files": [],
  "name": "playtest-optimize",
  "skill_md_contents": "---\nname: playtest-optimize\ndescription: Verify gameplay, usability, performance, bugs, and game feel through measured playtests and reproducible evidence.\n---\n\n# Playtest Optimize\n\n\n1. Read `../../references/testing-and-evidence.md` and choose checks for actual platform and engine. Distinguish compile success, scene launch, interactive playtest and full release qualification.\n2. Run real build/import tests, then verify player input, menu, progression, collision, score, win/lose, restart, save/load, pause, resize and asset/audio loading as relevant.\n3. For 3D, review camera occlusion, clipping, collision/navigability, visual readability and frame performance under representative load.\n4. Collect evidence with timestamps in logs or test artifacts as appropriate; no invented screenshots, benchmark frames or 'playtested' claims.\n5. Profile performance before optimizing; prioritize frame-time spikes, asset bloat, overdraw, expensive physics and leaks. Report device/browser/hardware conditions for measurements.\n6. Evaluate subjective fun and difficulty through actual human players; automated agents can assess controls and pacing proxies, not certify fun.\n7. Apply a bounded fix-and-retest loop; fail the gate when essential mechanics are unverified or broken.\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"
}