← Design Game StudioCONTENT HISTORY

Update to Design Game Studio

Snapshot Nov 4, 2026 · 00:14 UTC · version 0.1.2

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create, extend, or debug a Godot 2D/3D project using GDScript and editor/headless verification where supported.",
  "included_files": [],
  "name": "build-godot",
  "skill_md_contents": "---\nname: build-godot\ndescription: Create, extend, or debug a Godot 2D/3D project using GDScript and editor/headless verification where supported.\n---\n\n# Build Godot\n\n\n1. Read `../../references/godot.md` and determine installed Godot version, project format, GDScript versus C#, target exports and available editor/templates.\n2. Respect existing project.godot, scenes, resources and autoloads. Set a baseline and inspect signals, node paths and input actions before changing them.\n3. Implement a minimal playable scene using appropriate CharacterBody2D/3D, input mapping, collisions, camera and a win/lose/restart mechanism. Avoid outdated APIs copied from Godot 3.\n4. Model reusable scenes, resource references and signal connections explicitly. Do not hardcode fragile absolute node paths.\n5. Run `godot --headless --path PROJECT --editor --quit` or version-appropriate import/parse commands when installed, then actual gameplay input tests if a display is available.\n6. Only claim exports after necessary export templates/presets exist and commands complete successfully; web exports and C# availability must be checked separately.\n7. Deliver the editable Godot project, controls, scene map, test output and any missing engine/export prerequisites.\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: 5162b84c3abb320b4cf2fcd4e50602762893995f43fc5d2afbec1f7fe9db942c