Name: tanking2
Author: Y-R-U

Imported from Y-R-U/Y-R-U.github.io (gms/3d/tanking2/AGENTS.md). Install upstream with npx skills add Y-R-U/Y-R-U.github.io --skill tanking2. Copyright stays with the author.

Tanking II

Read README.md for the progression and file responsibilities. This is a separate game from ../tanking/; preserve the original and its save.

Vanilla ES modules, bundled Three.js r160, no build step or CDN requests.
Keep the opening extremely small: one betta purchase, one meal, then the funded second tank. Do not expose the full shop, tool dock, or journey menu at boot.
New species, abilities, modes, and keepsakes must be gated in state.js, not just hidden in the UI. Missions must route to mission.tankIndex through {mission:true}.
Old tanks continue earning. The first fish has a permanent meal caretaker after chapter one. Adventures use temporary tanks and return rewards without replacing the gallery. Offline progress is capped and safe.
state.js and data.js are DOM-free. Keep UI changes in ui.js/CSS, Three.js work in scene/fish/post modules, and audio in audio.js.
Keep runtime assets local and include their licenses. Prefer procedural fish and plants; reference photos are inspiration rather than gameplay backgrounds.
Run Node tests for simulation/progression changes and the relevant browser regression for UI/integration work. Validate actual rendering and small-screen controls before claiming visual or performance success.
Do not overwrite unrelated changes in the site registry or other games. Tanking II's registry key and screenshot name are tanking2.

Install tanking2 and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "y-r-u-y-r-u-github-io-tanking2", "kind": "skill", "name": "tanking2", "description": "Read `README.md` for the progression and file responsibilities. This is a separate game from `../tanking/`; preserve the original and its save.", "publisher": "Y-R-U", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Read `README.md` for the progression and file responsibilities. This is a separate game from `../tanking/`; preserve the original and its save." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/Y-R-U/Y-R-U.github.io", "path": "gms/3d/tanking2/AGENTS.md", "ref": "fdc6be45fe5a2871750a412d3958d91487940e26", "url": "https://github.com/Y-R-U/Y-R-U.github.io/blob/fdc6be45fe5a2871750a412d3958d91487940e26/gms/3d/tanking2/AGENTS.md", "key": "Y-R-U/Y-R-U.github.io/gms/3d/tanking2/AGENTS.md" } }, "instructions": "# Tanking II\n\nRead `README.md` for the progression and file responsibilities. This is a separate game from `../tanking/`; preserve the original and its save.\n\n- Vanilla ES modules, bundled Three.js r160, no build step or CDN requests.\n- Keep the opening extremely small: one betta purchase, one meal, then the funded second tank. Do not expose the full shop, tool dock, or journey menu at boot.\n- New species, abilities, modes, and keepsakes must be gated in `state.js`, not just hidden in the UI. Missions must route to `mission.tankIndex` through `{mission:true}`.\n- Old tanks continue earning. The", "cost": { "context_tokens": 356 } }

tanking2

About

Tanking II

Use it

Install tanking2 and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews