dschonholtz/.claude/skills/test-multiplayer
.claude/skills/test-multiplayer/SKILL.md
# Skill: Test Multiplayer Locally Use this skill any time you need to verify multiplayer behavior in MultiMagicDungeonWeb. ## Stack - Game: `index.html` (open as `file://` — no HTTP server needed) - WS server: `server/index.js` on port 8080 - Node binary: `~/.nvm/versions/node/v22.22.0/bin/node` (shell aliases don't apply in Bash tool) ## Step 1: Start the WS server ```bash export PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH" cd /Users/douglasschonholtz/repos/MultiMagicDungeonWeb/server
tools
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add dschonholtz/MultiMagicDungeonWeb .claude/skills/test-multiplayerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 1:43 AM51.7s1 file scanned
SKILL.md
Skill: Test Multiplayer Locally
Use this skill any time you need to verify multiplayer behavior in MultiMagicDungeonWeb.
Stack
- Game:
index.html(open asfile://— no HTTP server needed) - WS server:
server/index.json port 8080 - Node binary:
~/.nvm/versions/node/v22.22.0/bin/node(shell aliases don't apply in Bash tool)
Step 1: Start the WS server
export PATH="$HOME/.nvm/versions/node/v22.22.0/bin:$PATH"
cd /Users/douglasschonholtz/repos/MultiMagicDungeonWeb/server
npm install --silent
pkill -f 'node.*index.js' 2>/dev/null; sleep 0.5
node --watch index.js &
WS_PID=$!
sleep 1 && lsof -i :8080 | grep LISTEN && echo "Server up at ws://localhost:8080"
Step 2: Open two browser tabs
Tell the user to open in two separate tabs:
file:///Users/douglasschonholtz/repos/MultiMagicDungeonWeb/index.html
Step 3: What to verify
Join flow
- Both tabs auto-connect (no blocking modal)
- Each tab gets a unique
playerId welcomemessage arrives withspawnPoint,sessionId,dungeonSeed- The other tab shows a remote player
Movement sync
- Move in Tab A → remote player in Tab B moves (slight lerp lag at 20hz)
- DevTools → Network → WS to watch
player_movemessages
Spell cast
- Cast in Tab A → Tab B shows the projectile
spell_castmessage includestype,position,direction,ownerId
Disconnect
- Close Tab A → Tab B's remote player disappears (
player_leave)
Step 3b: Screenshot verification (MANDATORY)
After verifying the above, take a screenshot of EACH tab and explicitly describe what you see:
Tab A screenshot — describe: Is the scene rendering? Is there a player visible? Any console errors? Tab B screenshot — describe: Is the remote player model visible? Correct position/color? Any visual anomalies?
Do NOT report "multiplayer working" unless you have taken screenshots of both tabs and confirmed the remote player model is visible in each. Claiming success without visual confirmation is how bugs get shipped.
Step 4: Stop server
kill $WS_PID 2>/dev/null || pkill -f 'node.*index.js'
Common gotchas
- Port 8080 in use:
lsof -ti :8080 | xargs killbefore starting nodenot found: use the full nvm path above- Both tabs same session: by design — SessionManager assigns up to 8 players per session
Related Skills
dschonholtz/.claude/skills/websocket-protocol
tools
VerifiedTrustedCommunity
# Skill: Extend the WebSocket Protocol Use this when adding a new message type. Both client and server must be updated together. ## Message flow ``` Client → Server: join, move, spell_cast, rename, [new type] Server → Client: welcome, player_join, player_leave, player_move, spell_cast, player_rename, [new type] ``` ## Step 1: Define the message before coding Document these before touching any file: - **Name**: snake_case - **Direction**: client→server, server→client, or
SKILL.mdUpdated Apr 17, 2026
dschonholtz/.claude/skills/threejs-feature
development
VerifiedTrustedCommunity
# Skill: Add a Three.js Feature to MultiMagicDungeonWeb This game is a **single monolithic `index.html`** — no build step, no bundler. Everything lives in one file. ## File structure inside index.html ``` <html> <head> ... styles ... </head> <body> <!-- HUD overlay divs: #hud, #rename-panel, etc. --> <canvas id="c"></canvas> <script type="module"> // === CONSTANTS (WS_URL, PLAYER_SPEED, HP_MAX, etc.) === // === GLOBALS (scene, camera, renderer, clock) === //
SKILL.mdUpdated Apr 17, 2026
dschonholtz/threejs-builder
development
VerifiedTrustedCommunity
Creates simple Three.js web apps with scene setup, lighting, geometries, materials, animations, and responsive rendering. Use for: "Create a threejs scene/app/showcase" or when user wants 3D web content. Supports ES modules, modern Three.js r150+ APIs.
SKILL.mdUpdated Apr 17, 2026
dschonholtz/.claude/skills/task-workflow
development
VerifiedTrustedCommunity
# Skill: Task Workflow Use this checklist for every non-trivial piece of work. Four steps, always in order. Never skip or merge steps. --- ## Step 1 — Plan _(requires user approval before any code is written)_ - [ ] Create `tasks/active/NNN-short-title.md` from `tasks/TEMPLATE.md` - [ ] Document 2–3 options with pros/cons - [ ] Pick the best option and explain why, clearly - [ ] Write numbered, measurable **success criteria** (not "looks better" — testable outcomes) - [ ] Write a **testing s
SKILL.mdUpdated Apr 17, 2026