Menu
Launch an AI world designer to test the NeoMud Maker editor through browser interaction
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Launch an AI playtester to play NeoMud via the WebSocket relay and report findings
Launch a QA tester to systematically find bugs, test edge cases, and audit game systems. Use when you want thorough bug-hunting beyond what playtesting covers.
Evaluate architecture decisions, propose infrastructure, assess scalability, and make technology recommendations across the full stack — from hardware to cloud to application. Use when planning new services, scaling existing ones, evaluating hosting/cloud options, designing data pipelines, or making build-vs-buy decisions.
Deploy latest code to staging, wait for CI/CD pipelines, and verify health. Use after committing changes that need to go live on staging.
Audit user data channels, PII handling, abuse vectors, and content moderation across NeoMud Platform and game servers. Zero-trust posture — all inputs are invalid until verified.
Evaluate UX flows, interactions, and conventions across NeoMud marketplace, game client, and maker. Brings real-world UX expertise from industry-leading games and platforms.
| name | worldmaker |
| description | Launch an AI world designer to test the NeoMud Maker editor through browser interaction |
| context | fork |
| agent | worldmaker |
Launch a WorldMaker session using the Playwright MCP browser tools. The worldmaker agent will open a real browser, navigate the Maker editor, take screenshots, and provide feedback from a world designer's perspective.
$ARGUMENTS
If arguments were provided above, focus your testing session on that specific area (e.g., "zone editor", "item CRUD", "NPC creation", "export flow"). Explore naturally but concentrate your effort and feedback on the requested system.
If no arguments were provided, run an exploratory session: navigate every section, try creating and editing entities, test the zone map editor, check visual polish — evaluate the editor as a new world designer would.
First, check if the Maker dev server is running:
curl -s http://localhost:5173 > /dev/null 2>&1 && echo "Maker is running" || echo "Maker is NOT running"
If the Maker is not running, inform the user that it needs to be started:
The Maker dev server is not running. Please start it first:
cd maker && npm run dev
Do NOT proceed until the Maker is confirmed running.
http://localhost:5173 using browser_navigateAfter the session is complete (after producing the report), you MUST run these cleanup commands. Do NOT skip this step:
# Delete all screenshots and world copies created during the session
rm -rf .playwright-mcp/*
This removes screenshots (page-*.png) and any world bundle copies (.nmd files) that Playwright cached during the session. These files are large and must not accumulate.