→Docs

Docs written for your agent.

Paste one prompt into Claude Code, Codex or any coding agent. It reads these docs, sets up SimEngine, builds a first scene and proves it works. No API key, no MCP server: the engine is a local CLI that speaks JSON.

Works with
01Paste this into your agentOpen as text ↗Claude CodeTerminal, opens your SimEngine cloneClaude Code on the webCloud session, no GPU for capturesCodexDesktop appChatGPTAsk about SimEngine · web searchThe prompt is pre-filled, never sent for you. App links need the app installed.
Set up SimEngine and build my first verified scene with it. Read https://indiega.me/simengine/llms.txt and https://indiega.me/simengine/agent-guide.md first, then AGENTS.md in the SimEngine checkout. Get the checkout with git clone https://github.com/romainsimon/SimEngine.git (keep it outside my project). The repository is private until the first distributable milestone: if the clone fails with "Repository not found" or asks for credentials, stop and tell me I need access, do not look for copies elsewhere. SimEngine is a local C++20 / Vulkan 1.3 engine driven from the command line: there is no hosted API, no API key and no MCP server. Every tool prints one JSON document per command; classify results by exit code, then by error.code. 1. Setup. On Linux run ./tools/setup.sh --install-missing; on Windows 11 (Visual Studio 2022 C++ x64, CMake 3.28+, Ninja, Python 3.12+) run tools/setup.ps1. Expect zero failures among the selected CTest tests and report skips separately. Show me the smoke summary JSON naming my Vulkan device, or the structured BLOCKED outcome. 2. Discover. Run simengine_host --capabilities and tell me the scenario schema version, the commands, components and modules this build has. Use nothing that is not listed. 3. Create. Follow the simengine-create-project skill (https://indiega.me/simengine/skills/simengine-create-project/SKILL.md): create my project OUTSIDE the engine checkout, check it, run it and verify it. Expect PASS, 3 of 3 expectations, three PNG captures and a manifest.json. 4. Change. Follow the simengine-modify-scene skill: add one object, move it with a scheduled command, add an expectation for where it ends, then check, run and verify again. Prove the change: the new final_state_sha256 differs, the new expectation passed and the new capture shows the object. 5. On failure, follow simengine-run-capture-diagnose: report the exit code, failure.code, failure.step and failure.message verbatim, fix only my project files, and say plainly if the render is BLOCKED_ENVIRONMENT (no Vulkan device). Never edit engine sources, tests or examples to get a pass, and never fake a capture. SimEngine is pre-release. This workflow covers headless scenarios and captures, not general gameplay authoring. Textured static assets and a separate native SDK are implemented; the reviewed external Relay Yard preview exercises input, a game loop and directional shadows. Do not infer scenario commands from those native features. General rigid-body gameplay and audio remain unavailable here. Finish with a short report: commands run, exit codes, digests, PNG paths, and what SimEngine could not do. For refactors preserve expected state; presentation changes can change pixels without changing the simulation digest.

Needs a checkout of github.com/romainsimon/SimEngine, private until the first distributable milestone. SimEngine is pre-release, and the prompt tells your agent exactly what it cannot do yet.

02Read the docs

03Plain files for agents

MCP? Not needed, and none exists yet. Every SimEngine tool already returns typed JSON with coded errors, so any agent with a shell can drive it directly.