performance-capacity
Plan, diagnose, and verify performance budgets, latency targets, load tests, capacity estimates, bottleneck analysis, caching strategy, query efficiency, queue throughput, and regression gates. Use when a feature may be slow, a system must scale, a performance regression is suspected, or release readiness depends on throughput, cost, memory, CPU, or response time.
git clone --depth 1 https://github.com/majiayu000/spellbook /tmp/performance-capacity && cp -r /tmp/performance-capacity/skills/performance-capacity ~/.claude/skills/performance-capacitySKILL.md
# Performance Capacity ## Purpose Use this skill to make performance measurable before optimizing. It turns vague "make it faster" work into budgets, probes, bottleneck hypotheses, and regression gates. ## Baseline First Before changing code, capture: 1. User-facing operation or background job under test. 2. Current p50/p95/p99 latency or throughput. 3. Data size and concurrency assumptions. 4. Resource limits: CPU, memory, IO, network, database, queue. 5. Existing cache behavior and invalidation rules. 6. Cost or quota constraints. If no baseline can be gathered, state the nearest measurable proxy and its limitations. ## Budget Design Define budgets by surface: | Surface | Examples | |---|---| | UI | TTI, interaction latency, bundle size, render count | | API | p95 latency, error rate, DB query count, payload size | | Jobs | throughput, max lag, retry cost, idempotency | | Data | query plan, index coverage, backfill duration | | Infra | CPU/RSS, concurrency, autoscaling, cost per request | ## Optimization Rules - Optimize the measured bottleneck, not the most familiar code. - Prefer algorithmic, query, batching, and cache correctness fixes before capacity-only fixes. - Define cache invalidation and stale-data tolerance. - Add a regression test, benchmark, or dashboard check for risky paths. - Do not trade correctness, authorization, or tenant isolation for speed. ## Output Shape ```text operation: baseline: target_budget: bottleneck_hypothesis: measurement_plan: optimization_options: capacity_estimate: regression_gate: verification_commands: ```
Audit AND optimize a CLAUDE.md / AGENTS.md instruction file — score it against the five high-leverage patterns, flag anti-patterns, then apply approved fixes in place. Use when the user says 优化 CLAUDE.md / 优化 AGENTS.md / optimize my agent doc / 帮我改 claudemd, or after an audit when they want the fixes applied (not just reported).
Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.
Evidence-driven architecture research for understanding real systems and making technical decisions. Use when doing architecture landscape studies, source-backed system archaeology, build-vs-buy or adopt/adapt/build decisions, open-source and commercial comparisons, revisiting an earlier architecture choice, or handling requests such as 架构调研, 架构选型, 竞品架构, 技术尽调, 同类方案, 开源替代, how is X built, and what should we learn from X. Do not use for small mechanical changes, market-only discovery, or detailed design after the technology direction is already fixed.
Ask Grok or Gemini via opencli (browser-session based, no API cost). Use when the user says "问 grok", "问 gemini", "ask grok", "ask gemini", "用 grok 查", "grok 怎么看", "让 gemini 分析", or wants a second opinion from Grok/Gemini without paying API tokens. Routes to opencli which drives the already-logged-in Chrome session.