domains / families / software-engineering / multiplayer
multiplayer
authentic
Multiplayer game development principles. Architecture, networking, synchronization.
When to use
- Use when selecting multiplayer authority, synchronizing state, testing latency compensation, or preventing inventory duplication.
When not to use
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Skill page
Source