enter-world
Launch the Adventure Engine application for an adventure project. Use when the user wants to "enter" a world, "start" or "launch" an adventure session, or begin interactive gameplay. Fires off the application in the background using the current working directory as the adventure project root.
When & Why to Use This Skill
The 'enter-world' Claude skill automates the deployment and initialization of the Adventure Engine application. It streamlines the workflow for developers and players by handling backend server startup, environment validation, and browser orchestration, allowing users to transition from a project directory to an interactive gameplay session with a single command.
Use Cases
- Interactive Gameplay Launch: Instantly start an adventure session by triggering the engine directly from the project root within Claude.
- Headless Environment Testing: Deploy the Adventure Engine on remote or headless servers using the --no-browser flag to verify backend stability.
- Automated Project Validation: Use the skill to automatically check for valid project structures and dependencies before booting the local development server.
- Background Process Management: Run the adventure application as a detached background process, allowing for continuous gameplay while keeping the terminal free for other tasks.
| name | enter-world |
|---|---|
| description | Launch the Adventure Engine application for an adventure project. Use when the user wants to "enter" a world, "start" or "launch" an adventure session, or begin interactive gameplay. Fires off the application in the background using the current working directory as the adventure project root. |
Enter World
Launch the Adventure Engine application to begin an interactive adventure session.
Usage
- Ensure the current working directory contains a valid adventure project
- Run the launcher script which will boot the Adventure Engine application in fire-and-forget mode:
bash "${CLAUDE_PLUGIN_ROOT}/skills/enter-world/scripts/launch-world.sh" "$PWD"
To skip opening a browser (useful for remote/headless servers):
bash "${CLAUDE_PLUGIN_ROOT}/skills/enter-world/scripts/launch-world.sh" --no-browser "$PWD"
The script launches the application asynchronously - control returns immediately to Claude Code while the adventure application runs independently. Output is written to .adventure-engine.log in the project directory.
Script Location
The launcher script is at: skills/enter-world/scripts/launch-world.sh
What the Script Does
- Validates the adventure project directory
- Starts the backend server using
bun run start - Waits for server health check (up to 30 seconds)
- Opens the default browser to
http://localhost:3000(unless--no-browseris specified) - Logs server PID for later shutdown
- Detaches from the terminal (fire and forget)
- All output is logged to
.adventure-engine.login the project directory