playtest
Launch an AI playtester to play NeoMud via the WebSocket relay and report findings
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Launch an AI playtester to play NeoMud via the WebSocket relay and report findings
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Launch a browser-based UAT tester for the NeoMud web marketplace and WASM game client via Playwright
| name | playtest |
| description | Launch an AI playtester to play NeoMud via the WebSocket relay and report findings |
| context | fork |
| agent | playtester |
Launch a playtesting session using the WebSocket game relay. The playtester agent will read game state from text, send commands via JSON files, and provide feedback from a real player's perspective.
$ARGUMENTS
If arguments were provided above, focus your testing session on that specific area (e.g., "combat system", "character creation", "shop interactions"). Play naturally but concentrate your effort and feedback on the requested system.
If no arguments were provided, run an exploratory session: create a character, explore the world, fight monsters, check inventory, try skills — play as a curious new player would.
First, 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).
Determine which connection mode to use:
Check if already running:
[ -f scripts/telnet.lock ] && echo "Already running" || echo "Not running"
If not running, ask the user for credentials (username + password for an existing character — no registration via telnet). Then start:
# Local server (default port 4000)
node scripts/telnet-client.mjs &
# Staging
node scripts/telnet-client.mjs stage.neomud.app 4000 &
Wait a few seconds, then read scripts/telnet-recent.txt to confirm the welcome banner appeared.
The login flow is text-driven — follow the prompts:
sleep 3
# Read telnet-recent.txt — should see the welcome banner
echo -n "<username>" > scripts/telnet-command.txt
sleep 1
# Read telnet-recent.txt — should see "Password: "
echo -n "<password>" > scripts/telnet-command.txt
sleep 2
# Read telnet-recent.txt — should see room description and prompt
Check if already running by reading scripts/relay-state.json. If running and logged in, you can use the existing session.
If no relay is running, ask the user how they'd like to connect:
stage.neomud.app# Login (local server)
node scripts/game-relay.mjs <username> <password> &
# Register (local server)
node scripts/game-relay.mjs --register <username> <password> <charName> <class> [race] [gender] &
# Login (staging)
node scripts/game-relay.mjs --staging default-world &
# Register (staging)
node scripts/game-relay.mjs --staging default-world --register TestChar WARRIOR HUMAN male &
Wait a few seconds, then read scripts/relay-state.json to confirm connected and loggedIn are true.