Scale Game
Scale Game is a testing methodology that validates system design by intentionally testing at extreme parameters, such as processing one item versus one billion items, or operating over milliseconds versus years. Use this skill when designing architecture, building new systems, or troubleshooting unexpected production failures to identify fundamental weaknesses and confirm what assumptions actually hold under stress.
git clone --depth 1 https://github.com/mrgoonie/claudekit-skills /tmp/scale-game && cp -r /tmp/scale-game/.claude/skills/problem-solving/scale-game ~/.claude/skills/scale-gameSKILL.md
# 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
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files (transcription with timestamps, summarization, speech understanding, music/sound analysis up to 9.5 hours), understand images (captioning, object detection, OCR, visual Q&A, segmentation), process videos (scene detection, Q&A, temporal analysis, YouTube URLs, up to 6 hours), extract from documents (PDF tables, forms, charts, diagrams, multi-page), generate images (text-to-image, editing, composition, refinement). Use when working with audio/video files, analyzing images or screenshots, processing PDF documents, extracting structured data from media, creating images from text prompts, or implementing multimodal AI features. Supports multiple models (Gemini 2.5/2.0) with context windows up to 2M tokens.
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.
Integrate Bunny.net services (CDN, Storage, Stream, DNS, Edge Scripting, Shield, Magic Containers, Optimizer, Database). Use when building with Bunny.net APIs, deploying to Bunny CDN, uploading files to Edge Storage, managing video streaming, configuring DNS zones, writing edge scripts, setting up WAF/DDoS protection, deploying containers, or optimizing images. Triggers on "bunny", "bunnycdn", "b-cdn", "pull zone", "edge storage", "bunny stream".
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
Stage all files and create a commit.