MCP HubMCP Hub
スキル一覧に戻る

Scale Game

mrgoonie
更新日 Today
46 閲覧
738
118
738
GitHubで表示
テストtesting

について

Scale Gameスキルは、開発者が極端なスケール(1000倍の大きさ/小ささ、瞬時/1年間)でシステムをテストし、通常運用では隠された本質的な真実を明らかにするのに役立ちます。このスキルは、ボリューム、速度、ユーザー数といった次元で負荷テストを行うことで、スケーラビリティの限界、並行処理の問題、アーキテクチャの弱点を浮き彫りにします。スケーラビリティやエッジケースに不確かさがある場合、あるいは本番環境のボリュームを想定したアーキテクチャを検証する際に、このスキルをご利用ください。

クイックインストール

Claude Code

推奨
プラグインコマンド推奨
/plugin add https://github.com/mrgoonie/claudekit-skills
Git クローン代替
git clone https://github.com/mrgoonie/claudekit-skills.git ~/.claude/skills/Scale Game

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

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
SpeedInstant vs 1 yearAsync requirements, caching needs
Users1 user vs 1B usersConcurrency issues, resource limits
DurationMilliseconds vs yearsMemory leaks, state growth
Failure rateNever fails vs always failsError 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

GitHub リポジトリ

mrgoonie/claudekit-skills
パス: .claude/skills/problem-solving/scale-game

関連スキル

content-collections

メタ

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

スキルを見る

evaluating-llms-harness

テスト

This Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.

スキルを見る

cloudflare-turnstile

メタ

This skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.

スキルを見る

webapp-testing

テスト

This Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.

スキルを見る