{"id":77660,"plugin_id":"plugins_6ae8d0ba8e808191a5a7ac9a01d005f8","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:29.066Z","digest":"b1b54dfe9e9765b8552ecd738cb95a2a6e0e1038d3f1e1d5de9c341ed37b2f27","against":null,"payload":{"description":"Implement or modify a playable browser 2D game in Phaser, including scenes, physics, input, and a browser build.","included_files":[],"name":"build-2d-phaser","skill_md_contents":"---\nname: build-2d-phaser\ndescription: Implement or modify a playable browser 2D game in Phaser, including scenes, physics, input, and a browser build.\n---\n\n# Build 2D Phaser\n\n\n1. Read `../../references/phaser.md` and official versioned Phaser docs. Phaser 4 is 2D-focused; check current APIs instead of copying outdated Phaser 3 examples uncritically.\n2. Use the project’s existing build system or scaffold an official Phaser/Vite/TypeScript project when tools/network are available; don't invent installs. Set a baseline before editing.\n3. Create a minimal scene with render loop, deterministic game state, keyboard input plus touch when mobile is a target, collision, feedback and reset. Ensure canvas fits viewport without distortion or illegible text.\n4. Keep assets importable and consistent; use generated geometric textures until authorized assets are ready. Do not depend on unstable CDN assets to make a deliverable runnable.\n5. Isolate mechanics from presentation where practical and avoid fragile one-file megascenes for projects with multiple systems.\n6. Validate `npm` installation and build with actual commands when available; run browser smoke tests using real key/touch interactions and watch console/errors.\n7. Check win, lose, pause, restart, focus loss and resize. Record an evidence log and exact files changed.\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":{}}