Skip to content

DangQuangSE/team-development-skills / .agents/skills/problem-solving/scale-game

Scale Game

Verified

Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales

Scale Game

Overview

Test your approach at extreme scales to find what breaks and what surprisingly survives.

Core principle: Extremes expose fundamental truths hidden at normal scales.

Quick Reference

Scale DimensionTest At ExtremesWhat It Reveals
Volume1 item vs 1B itemsAlgorithmic complexity limits, index needs
SpeedInstant vs year-longAsync requirements, caching needs, timeouts
Users1 user vs 1B usersConcurrency issues, resource limits, auth bottlenecks
DurationMilliseconds vs yearsMemory leaks, state growth, data rot
Failure rateNever fails vs always failsError handling adequacy, retry logic
Data size1 byte vs 1TBStorage strategy, streaming vs buffering

Process

  1. Pick dimension — What could vary extremely?
  2. Test minimum — What if this was 1000x smaller/faster/fewer?
  3. Test maximum — What if this was 1000x bigger/slower/more?
  4. Note what breaks — Where do limits appear?
  5. Note what survives — What's fundamentally sound?

Examples

Example 1: Error Handling

Normal scale: "Handle errors when they occur" works fine At 1B scale: Error volume overwhelms logging, crashes system Reveals: Need to make errors impossible (type systems, contracts) or expect them (chaos engineering, circuit breakers)

Example 2: Synchronous APIs

Normal scale: Direct function calls work At global scale: Network latency makes synchronous calls unusable Reveals: Async/messaging becomes survival requirement, not optimization

Example 3: In-Memory State

Normal duration: Works for hours/days At years: Memory grows unbounded, eventual crash Reveals: Need persistence or periodic cleanup — cannot rely on process memory

Example 4: Single DB Write Path

Normal load: One writer, no contention At 10k concurrent writes: Deadlocks, lock contention, queue buildup Reveals: Need optimistic locking, write batching, or event sourcing

Red Flags You Need This

  • "It works in dev" (but will it work under production load?)
  • No idea where the limits are
  • "Should scale fine" (without testing or analysis)
  • Surprised by production behavior
  • First time this code will see real users

Remember

  • Extremes reveal fundamentals
  • What works at one scale often fails at another
  • Test both directions (bigger AND smaller)
  • Use insights to validate architecture early — cheaper to change now
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall