Scale Game
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales
What this skill does
# 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
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.