Scaling Architecture
Use when the user asks about game server scaling, shards, zone servers, Agones, game server fleet autoscaling or game backend capacity. Produces fleet, persistence and region design with capacity math. Not for a single server tick loop (use authoritative-server) or generic web autoscaling (use devops-kubernetes-autoscaling).
Install
npx skills add j4flmao/agent-skills --skill scaling-architecturegit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/game/game-server/scaling-architecture ~/.claude/skills/scaling-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Scaling Architecture — Deep Engineering Guide
## Purpose
From "hundreds playing" to "a million in a weekend": how the server fleet grows without breaking determinism, latency or cost. Skill covers zone/sharding, stateless matchmaking + stateful game pods, persistence, region/edge, observability and capacity/autoscaling.
## Agent Protocol
### Trigger
"game server scaling", "sharding", "zone servers", "agones", "game server autoscaling", "game backend capacity".
### Input Context
- Concurrent user targets and regions
- Session length and state size
- Hosting (bare metal, Kubernetes/Agones, cloud fleet services)
### Output Artifact
Fleet architecture and capacity plan. No file unless requested.
### Response Format
```
Topology: {services and pods}
State: {where it lives}
Capacity: {CCU per server, buffer}
Scaling: {trigger and policy}
```
## 1. The Scale Model (Start Simple, Grow Recursively)
```
Tier 1: one game server process + one lobby = 10–200 players
Tier 2: many per-region pods; lobby → matchmaker → pod (stateful), stateless elsewhere
Tier 3: zone-sharded (an open world is units of zones), state in DB, edge relay
```
The rule: **stateful = the game pod only; everything else stateless + horizontally scalable.**
## 2. Stateless vs Stateful
| Service | State? | Scale |
|---------|--------|-------|
| login / auth | token-cache only | stateless, autoscale |
| matchmaker / queue | KV session state | stateless, replica |Details
- Skill name
scaling-architecture- Repository
- j4flmao/agent-skills
- Path
skills/game/game-server/scaling-architecture/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Scaling Architecture skill do?
Use when the user asks about game server scaling, shards, zone servers, Agones, game server fleet autoscaling or game backend capacity. Produces fleet, persistence and region design with capacity math. Not for a single server tick loop (use authoritative-server) or generic web autoscaling (use devops-kubernetes-autoscaling).
How do I install the Scaling Architecture skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill scaling-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Scaling Architecture popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Spring Boot Architecture
45j4flmao/agent-skills
Use when the user asks about Spring Boot project structure, package-by-feature, hexagonal Spring, Spring WebFlux vs MVC, Spring Data repositories or Spring profiles. Produces a Spring Boot 3/4 service layout. Not for @Transactional, AOP, security or testing recipes (use spring-boot-patterns).
Sass Machine Code
45j4flmao/agent-skills
Use when the user asks about SASS, cuobjdump -sass, nvdisasm, warp stall reasons, long scoreboard, HMMA/HGMMA, FFMA or instruction mix in Nsight Compute. Produces annotated SASS with root cause and a source-level fix. Not for writing PTX or inline asm (use ptx-assembly) or general kernel design (use cuda-programming).
Spring Boot Patterns
45j4flmao/agent-skills
Use when the user asks about Spring Boot service layer and transaction boundaries, @Transactional, constructor injection, Spring AOP, Spring Security filter chain or @DataJpaTest/@WebMvcTest. Produces Spring Boot pattern code. Not for package layout (use spring-boot-architecture).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.