Why should I test both minimum and maximum scales?

Testing the maximum reveals resource limits and complexity bottlenecks, while testing the minimum (1000x smaller) can reveal unnecessary overhead or logic that fails in low-resource environments.

What dimensions of scaling does it analyze?

It evaluates systems across five key dimensions: Volume (items), Speed (latency), Users (concurrency), Duration (time), and Failure Rate (error frequency).

What is the primary goal of the Scale Game skill?

The primary goal is to expose fundamental architectural flaws by analyzing how code behaves at 1000x its normal operating parameters, revealing truths hidden at standard scales.

Does this skill perform actual load testing?

No, it is an analytical framework that guides Claude to help you reason through extreme scenarios and identify theoretical breaking points in your logic and design.

When should I use this skill?

Use it during the design or development phase when you are uncertain about production scalability, when edge cases are unclear, or when you need to validate architecture for high volumes.

Scale Game Problem Solving

Name: Scale Game Problem Solving
Author: laurenj3250-debug

bylaurenj3250-debug

セキュリティとテスト

Stress-tests software architecture and logic by simulating extreme operational scales to identify hidden vulnerabilities and scalability bottlenecks.

概要

The Scale Game skill empowers developers to rigorously validate their technical decisions by applying the 'Extreme Scale' mental model within Claude. By testing implementations against 1000x variations in data volume, processing speed, user concurrency, and system duration, the skill reveals fundamental truths—like algorithmic complexity limits, memory leaks, or concurrency issues—that remain invisible under normal development conditions. It serves as a powerful diagnostic tool for early architectural validation, ensuring that systems are fundamentally sound for production-grade demands before significant resources are invested in infrastructure.

主な機能

Exposes hidden memory leaks and state growth issues over long durations
Evaluates API robustness by testing instant versus year-long latency scenarios
Highlights architectural red flags before they reach production environments
Identifies algorithmic complexity limits through '1 item vs 1B items' analysis
0 GitHub stars
Simulates extreme scale dimensions including volume, speed, and concurrency

ユースケース

Testing if error-handling logic survives high-frequency failure rates or chaos engineering
Validating if a new database schema can handle 100x projected traffic growth
Determining if synchronous API calls will break under global network latency constraints

概要

主な機能

Exposes hidden memory leaks and state growth issues over long durations
Evaluates API robustness by testing instant versus year-long latency scenarios
Highlights architectural red flags before they reach production environments
Identifies algorithmic complexity limits through '1 item vs 1B items' analysis
0 GitHub stars
Simulates extreme scale dimensions including volume, speed, and concurrency

ユースケース

Testing if error-handling logic survives high-frequency failure rates or chaos engineering
Validating if a new database schema can handle 100x projected traffic growth
Determining if synchronous API calls will break under global network latency constraints