dream-loop

# Dream Loop Skill An autonomous process for building extremely impressive visuals, especially 3D scenes (games, apps, usually browser three.js/WebGL): generate photorealistic concept art of the ideal result, build it, screenshot the live build, have a judge score screenshot vs concept against a gated ladder, and iterate until convergence. Goal: the most visually stunning result at an acceptable frame rate for the target platform (e.g. 60 fps browser, 120 fps modern mobile). This skill does NOT cover general web-app functionality, 2D UI design, or non-visual quality — only the visual-fidelity loop. ## When to Use - User says "dream loop" or asks for a game/scene/app built to a very high level of graphical fidelity. - Follow-up refinement passes on an existing visual product (see Follow-up loops below). ## Prerequisites - **Concept art**: the `image_generate` tool. If unavailable, stop and ask the user for a concept image (or an image-generation API to connect to). - **Screenshots**: `browser_exec` — serve the build locally (`python3 -m http.server` for static builds), then `new_tab(url)`, `wait_for_load()`, `capture_screenshot()`. - **Judging**: `vision_analyze` (see Judge section for the one-image-per-call workaround). - **Optional**: Blender for asset modeling — see the `blender-3d-automation` skill. `delegate_task` for parallel asset work and fresh-context judging. If you don't have the tools needed for the full loop, flag that to the user early and st...