Individual skill

game-dev

Build, extend, and verify playable browser games, optionally using SandBase for generated concept art and game assets. Use for substantial 2D or 3D web-game work; use a general frontend workflow for non-game interactive sites.

marketing/game-dev/SKILL.md

Read pinned source

Source commit cbab58188611e626ccaf54ac346b437d12ea4729

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
210
Repository last updated
Sep 26, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Game Dev

Turn a game brief into a playable, visually coherent browser game. Keep the game code, deterministic asset processing, builds, and tests local. Use SandBase only for optional generative assets that the user requests.

Read [the SandBase API map](references/sandbase-api-map.md) before generating concept art, textures, sprites, backgrounds, or other AI media.

## Establish the build target

Before implementation, resolve only the choices that materially affect the architecture:

- genre, player goal, failure and success conditions;
- input methods and target devices;
- 2D or 3D presentation, camera, aspect ratio, and art direction;
- required mechanics, content scope, and accessibility expectations;
Back to top