How do I install the Masoi Socket Contract skill?

Run npx skillmds@latest add nobodyonlyc/masoi-socket-contract in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Masoi Socket Contract safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Masoi Socket Contract?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Masoi Socket Contract free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Masoi Socket Contract?

nobodyonlyc (@nobodyonlyc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Masoi Socket Contract by nobodyonlyc

Name: Masoi Socket Contract
Author: nobodyonlyc

Masoi Socket Contract

Maintain the Ma Sói Socket.IO contract between server/index.js and client/src/hooks/useGame.js. Use when adding, renaming, removing, or changing payloads for socket events such as room_joined, role_assigned, phase_changed, night_resolved, wolf_target_updated, vote_resolved, room_reset, reconnect/resume, chat, or special-role events.

nobodyonlyc 091575e 3 files · 3.7 KB Updated Sep 17, 2026

File contents

Ma Sói Socket Contract

Workflow

Find server emits/listeners in server/index.js.
Find client listeners/actions in client/src/hooks/useGame.js.
Check UI consumers in client/src/pages/* and client/src/components/*.
Update references/events.md when the contract changes.
Preserve hidden-information boundaries in payloads.
Verify with:
- node --check server/index.js
- cd client && npm run build

Contract Rules

Every server socket.emit or io.to(...).emit used by gameplay must have a matching client listener unless intentionally one-way.
Every client socket.emit action must have a matching server handler.
Payload changes must be made server-first, then hook state, then UI.
Reconnect/resume must re-emit enough state to rebuild the current screen.
Do not expose all player roles to living non-spectator players before the game ends.

Common Files

Server handlers: server/index.js
Client socket setup: client/src/hooks/useSocket.jsx
Client game contract/state: client/src/hooks/useGame.js
Main routing by phase: client/src/App.jsx

References

Load references/events.md when changing Socket.IO payloads or reconnect behavior.

Frequently asked questions