multiplayer
Multiplayer game development principles. Architecture, networking, synchronization.
Content Preview
--- name: multiplayer description: "Multiplayer game development principles. Architecture, networking, synchronization." risk: unknown source: community date_added: "2026-02-27" --- # Multiplayer Game Development > Networking architecture and synchronization principles. --- ## 1. Architecture Selection ### Decision Tree ``` What type of multiplayer? │ ├── Competitive / Real-time │ └── Dedicated Server (authoritative) │ ├── Cooperative / Casual │ └── Host-based (one player is server) │
How to Use
Recommended: Install to project (local)
mkdir -p .claude/skills
curl -o .claude/skills/multiplayer.md \
https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/game-development/multiplayer/SKILL.mdSkill is scoped to this project only. Add .claude/skills/ to your .gitignoreif you don't want to commit it.
Alternative: Clone full repo
git clone https://github.com/sickn33/antigravity-awesome-skillsThen reference at skills/game-development/multiplayer/SKILL.md
Related Skills
architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
architecturearchitecture
by sickn33 (Antigravity) · antigravity-awesome-skills
architecture
Architecture design skill with ADR records, system design checklists, scalability assessment, and architecture patterns
architecturearchitecture
by davepoon · buildwithclaude
architecture-decision-records
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
architecturearchitecturedecisionrecords
by sickn33 (Antigravity) · antigravity-awesome-skills
architecture-designer
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
architecture-designerarchitecturedesigner
by Jeffallan · jeffallan-claude-skills