本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.0 KB
  • agents/openai.yaml253 B

SKILL.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:

SurfaceExamples
UITTI, interaction latency, bundle size, render count
APIp95 latency, error rate, DB query count, payload size
Jobsthroughput, max lag, retry cost, idempotency
Dataquery plan, index coverage, backfill duration
InfraCPU/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

operation:
baseline:
target_budget:
bottleneck_hypothesis:
measurement_plan:
optimization_options:
capacity_estimate:
regression_gate:
verification_commands:

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

majiayu000 のスキルをすべて見る

このスキルの問題を報告する