원클릭으로 Manus에서 모든 스킬 실행

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 저장소 열기 Creator 저장소 보기

다운로드

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.