scale-game

在极端条件下测试(1000倍大小差异,瞬时/一年时间)以揭示在正常尺度下隐藏的基本原理。在对可扩展性不确定、边缘情况不明确或验证生产环境架构容量时使用。

📖 中文导读:在极端条件下测试(1000倍大小差异,瞬时/一年时间)以揭示在正常尺度下隐藏的基本原理。在对可扩展性不确定、边缘情况不明确或验证生产环境架构容量时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: scale-game description: Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales. Use when uncertain about scalability, edge cases unclear, or validating architecture for production volumes. tier: e morpheme: e dewey_id: e.3.1.4 dependencies: - gremlin-brain-v2

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 Dimension Test At Extremes What It Reveals
Volume 1 item vs 1B items Algorithmic complexity limits
Speed Instant vs 1 year Async requirements, caching needs
Users 1 user vs 1B users Concurrency issues, resource limits
Duration Milliseconds vs years Memory leaks, state growth
Failure rate Never fails vs always fails Error handling adequacy

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) or expect them (chaos engineering)

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, can't rely on memory

Red Flags You Need This

  • "It works in dev" (but will it work in production?)
  • No idea where limits are
  • "Should scale fine" (without testing)
  • Surprised by production behavior

Remember

  • Extremes reveal fundamentals
  • What works at one scale fails at another
  • Test both directions (bigger AND smaller)
  • Use insights to validate architecture early