.agent/skills/game-development/multiplayer/SKILL.md
Multiplayer game development principles. Architecture, networking, synchronization.
npx skillsauth add CongDon1207/AGENTS.md multiplayerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Networking architecture and synchronization principles.
What type of multiplayer?
│
├── Competitive / Real-time
│ └── Dedicated Server (authoritative)
│
├── Cooperative / Casual
│ └── Host-based (one player is server)
│
├── Turn-based
│ └── Client-server (simple)
│
└── Massive (MMO)
└── Distributed servers
| Architecture | Latency | Cost | Security | |--------------|---------|------|----------| | Dedicated | Low | High | Strong | | P2P | Variable | Low | Weak | | Host-based | Medium | Low | Medium |
| Approach | Sync What | Best For | |----------|-----------|----------| | State Sync | Game state | Simple, few objects | | Input Sync | Player inputs | Action games | | Hybrid | Both | Most games |
| Technique | Purpose | |-----------|---------| | Prediction | Client predicts server | | Interpolation | Smooth remote players | | Reconciliation | Fix mispredictions | | Lag compensation | Rewind for hit detection |
| Technique | Savings | |-----------|---------| | Delta compression | Send only changes | | Quantization | Reduce precision | | Priority | Important data first | | Area of interest | Only nearby entities |
| Type | Rate | |------|------| | Position | 20-60 Hz | | Health | On change | | Inventory | On change | | Chat | On send |
Client: "I hit the enemy"
Server: Validate → did projectile actually hit?
→ was player in valid state?
→ was timing possible?
| Cheat | Prevention | |-------|------------| | Speed hack | Server validates movement | | Aimbot | Server validates sight line | | Item dupe | Server owns inventory | | Wall hack | Don't send hidden data |
| Factor | Impact | |--------|--------| | Skill | Fair matches | | Latency | Playable connection | | Wait time | Player patience | | Party size | Group play |
| ❌ Don't | ✅ Do | |----------|-------| | Trust the client | Server is authority | | Send everything | Send only necessary | | Ignore latency | Design for 100-200ms | | Sync exact positions | Interpolate/predict |
Remember: Never trust the client. The server is the source of truth.
development
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications, OR when they provide screenshots/images/designs to replicate or draw inspiration from. For screenshot inputs, extracts design guidelines first using ai-multimodal analysis, then implements code following those guidelines. Generates creative, polished code that avoids generic AI aesthetics.
development
Use when the user asks to investigate, understand, explore, or explain how a feature works, asks about existing logic, or wants to understand code flow. Triggers on keywords like "how does", "explain", "investigate", "understand", "what does", "where is", "how works", "logic flow", "trace", "explore feature".
development
Use when the user asks to implement a new feature, enhancement, add functionality, build something new, or create new capabilities. Triggers on keywords like "implement", "add feature", "build", "create new", "develop", "enhancement".
development
Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".