Menu
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.
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
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.
Launch a browser-based UAT tester for the NeoMud web marketplace and WASM game client via Playwright
| name | qa-test |
| description | 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. |
| context | fork |
| agent | qa-tester |
Launch a QA testing session. The QA tester reads source code, analyzes data files, plays the game via relay, and files GitHub issues for every bug found.
$ARGUMENTS
If arguments were provided above, focus your QA session on that specific system (e.g., "combat", "vendors", "spells", "persistence", "protocol", "inventory", "economy"). Do a deep dive — read all related code, trace error paths, test boundaries, and file bugs.
If no arguments were provided, run a full audit across all major systems.
If you plan to do live testing (not just code audit), check if the game server is running:
curl -s http://localhost:8080/health
If the health check fails, inform the user that the game server needs to be running (./gradlew :server:run).
Always rebuild the world bundle before testing:
./gradlew packageWorld --rerun-tasks
if [ -f scripts/relay.lock ]; then
kill "$(cat scripts/relay.lock)" 2>/dev/null; sleep 1
[ -f scripts/relay.lock ] && kill -9 "$(cat scripts/relay.lock)" 2>/dev/null && rm -f scripts/relay.lock scripts/relay-state.json
fi