一键在 Manus 中运行任何 Skill

masoi-socket-contract

星标0

分支0

更新时间2026年5月28日 15:22

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

nobodyonlyc

nobodyonlyc/masoi

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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.

同仓库更多 Skills

同仓库

masoi-be-testing

nobodyonlyc/masoi

Create and maintain backend unit tests, integration tests, and API tests for Ma Sói server. Covers gameEngine.js pure functions, Socket.IO handler logic, Redis/PostgreSQL data layer, authentication, room lifecycle, and timer-driven resolution. Use when adding server-side test coverage, debugging server logic, or verifying backend changes.

2026-06-040

masoi-devops

nobodyonlyc/masoi

Manage Ma Sói Docker configuration, deployment, infrastructure, environment variables, Nginx reverse proxy, health checks, and CI/CD. Use when modifying docker-compose files, Dockerfiles, nginx.conf, .env files, or preparing for VPS/cloud deployment.

2026-06-040

masoi-e2e-testing

nobodyonlyc/masoi

Create and maintain automated tests for Ma Sói game engine, night/vote resolution, Socket.IO event contracts, race conditions, and role-specific edge cases. Use when adding test coverage, debugging flaky behavior, verifying concurrent action handling, or setting up CI testing.

2026-06-040

masoi-perf-security

nobodyonlyc/masoi

Audit Ma Sói server and client for performance bottlenecks, memory leaks, security vulnerabilities, rate limiting, input validation, CORS policy, timer cleanup, and room zombie detection. Use when changing socket handlers, setTimeout/setInterval patterns, Redis/PostgreSQL queries, authentication, or deploying to production.

2026-06-040

masoi-role-designer

nobodyonlyc/masoi

Design and integrate new roles into Ma Sói Online. Provides templates, file checklists, balance guidelines, and integration patterns for adding roles across server game engine, socket handlers, client hooks, UI components, and documentation. Use when planning, implementing, or reviewing new character roles.

2026-06-040

masoi-gameplay-qa

nobodyonlyc/masoi

Generate manual QA scenarios and acceptance checks for Ma Sói gameplay across player counts, role setups, night actions, vote resolution, special roles, timers, chat, and end-game history. Use before or after gameplay changes to define concrete test rooms and expected outcomes.

2026-05-280

name	masoi-socket-contract
description	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.

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.