← Design Game StudioCONTENT HISTORY
WHAT CHANGED
Update to Design Game Studio
Snapshot Nov 4, 2026 · 00:14 UTC · version 0.1.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Design Game Studio and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Design levels and game environments with readable objectives, pacing, difficulty, progression, and meaningful player decisions.",
"included_files": [],
"name": "level-design",
"skill_md_contents": "---\nname: level-design\ndescription: Design levels and game environments with readable objectives, pacing, difficulty, progression, and meaningful player decisions.\n---\n\n# Level Design\n\n\n1. Derive the level's teaching objective, player path, points of challenge, optional discovery, and exit state from game mechanics.\n2. Create blockouts before final art. Establish start/safe area, checkpoints, signposting, enemy/hazard placement and completion condition.\n3. For 2D, validate tile collision, jump distances and camera bounds; for 3D, validate traversal, collision geometry, line of sight, scale and navigation.\n4. Introduce new mechanics safely, then vary challenge and create a final competence test. Avoid long empty corridors and decorative rooms with no gameplay contribution.\n5. Read `../../references/level-design.md` and record a playable flow from spawn to win/lose/restart.\n6. Test with scripted walkthroughs or human playtest, include stuck-state detection and ensure the level is completable without undocumented controls.\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"
}SHA-256 of public snapshot: 3947b55c7a1aba27cbde964dacee9b3c044ebdb1866851ac42fbebeea8ab6a5d