mcpField
G
godogen

godogen

github.com/htdtDevelopment7.2k115 installsUpdated 2w ago
Repository

About godogen

godogen is a skill for generating and updating Babylon.js browser games from natural-language requests. It organizes work into planning, implementation, and visual verification in the browser.

Key features

  1. 01Generates and updates games from natural language
  2. 02Plans and executes work in stages
  3. 03Plans and generates game assets
  4. 04Iterates with Vite hot reload
  5. 05Verifies visuals with browser screenshots or video

Use cases

  1. 01Build a Babylon.js game from a description
  2. 02Resume tasks recorded in an existing PLAN.md
  3. 03Plan and generate game assets
  4. 04Inspect the game in a browser

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/htdt/godogen --skill godogen

After installing, type/godogenin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

architecture.md
capture.md
decomposer.md
quirks.md
scaffold.md
scene-generation.md
task-execution.md

Details

From the project README

Babylon Game Generator

Generate and update Babylon.js browser games from natural language.

Capabilities

Read each stage file from ${GODOGEN_SKILL_DIR}/ only when you reach that stage.

FilePurposeWhen to read
visual-target.mdGenerate reference imagePipeline start
decomposer.mdDecompose into task planAfter visual target
scaffold.mdVite/Babylon project shellAfter decomposition
architecture.mdBabylon gameplay architecture stanceBefore designing game code
asset-planner.mdBudget and plan assetsIf budget provided
asset-gen.mdAsset generation CLI refWhen generating assets
rembg.mdBackground removalOnly when an asset needs transparency removed
task-execution.mdTask workflow + commandsBefore first task
quirks.mdBabylon/browser gotchasBefore writing code
scene-generation.mdScene/world implementation patternsWhen creating or replacing the playable scene
capture.mdBrowser screenshot/video captureBefore screenshots or video
(babylon-help skill)Babylon/Vite/browser API lookupFor Babylon-specific questions

Pipeline

User request
    |
    +- Check if PLAN.md exists (resume check)
    |   +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md, ASSETS.md if present -> skip to task execution
    |   +- If no: continue with fresh pipeline below
    |
    +- Generate visual target -> reference.png + ASSETS.md (art direction only)
    +- Analyze risks + define verification criteria -> PLAN.md
    +- Scaffold/refresh Vite project -> package.json + src/ + STRUCTURE.md
    |
    +- If budget provided (and no asset tables in ASSETS.md):
    |   +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments
    |
    +- Start/keep Vite dev server running at http://127.0.0.1:5173
    +- Execute risk slices first, then main build
    +- Use browser screenshots frequently while iterating
    +- If final presentation media is required:
        +- Record browser video to screenshots/result/{N}/video.mp4

Assets

If a budget is provided, generating proper assets is part of the task. Use asset-planner.md / asset-gen.md before falling back to procedural stand-ins.

Runtime-loaded assets belong under src/assets/** when imported by TypeScript, or public/** only when a stable direct URL is needed. Keep reference images, prompts, source sidecars, and debug captures outside runtime asset paths.

Execution

Read task-execution.md before starting. Keep npm run dev alive when possible. Vite hot reload should be the normal inner loop:

  1. Edit src/game/** or src/assets/**.
  2. Let the scene reload in the already-open browser.
  3. Capture or inspect the browser.
  4. Run npm run check before larger edits and npm run build before final media.

Chrome/Chromium and WebGL2 are required. If either is missing, stop and report the missing dependency rather than working around it. Hardware GPU acceleration is preferred — the capture script logs a prominent warning when WebGL2 falls back to a software renderer (SwiftShader, llvmpipe, lavapipe, etc) but still completes the capture. On a host with a GPU, treat that warning as a misconfiguration to fix; on a GPU-less host the warning is informational and the run still proves the task at reduced quality.

Babylon Help

Use babylon-help for Babylon API questions, examples, loader behavior, Vite integration, browser capture issues, or exact import paths. Prefer the installed npm package sources/types for the current project version, then official docs.

Context Hygiene

Keep important state in files:

  • PLAN.md — task statuses and verification criteria
  • STRUCTURE.md — architecture reference
  • MEMORY.md — discoveries, quirks, workarounds, what worked or failed
  • ASSETS.md — asset manifest with paths and generation details

After completing each task, update the relevant state files. Commit after verified task slices when the repo policy or user asks for commits.

Visual Verification

Do not trust code alone. Verify visible work in the browser with screenshots or recorded video. When code and media disagree, trust the media. If a requirement is not visible in browser capture, treat it as unfinished.

Comments

Markdown supported