メニュー
Use for latency, throughput, CPU, memory, allocations, large datasets, hot loops, serialization, database performance, concurrency, backpressure, caching, or capacity planning.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | performance-engineering |
| description | Use for latency, throughput, CPU, memory, allocations, large datasets, hot loops, serialization, database performance, concurrency, backpressure, caching, or capacity planning. |
For each performance-critical function, document:
Stop and request explicit design review before adding unsafe memory, lock-free algorithms, custom allocators, unbounded caches, or weaker durability/security semantics.
Use when adding modules, dependencies, services, integrations, APIs, persistence, events, queues, or refactoring boundaries. Verifies dependency direction, cohesion, contracts, cycles, and ADR needs.
Use when adding or changing production modules, APIs, jobs, workflows, database operations, external calls, queues, caches, or operational failure behavior.
Use before merging or deploying a substantial feature, service, migration, infrastructure change, performance change, or reliability/security-sensitive fix.
Use for security-sensitive code, external input, authentication, authorization, APIs, uploads, webhooks, secrets, cryptography, dependencies, infrastructure, or pre-merge security review.
Use to design tests for new behavior, bug fixes, refactors, APIs, migrations, security controls, concurrency, failure handling, observability, accessibility, or performance-sensitive code.
Enforces OWASP-style secure coding, CSP/header preservation, secret hygiene, safe rendering, cookie/privacy rules, and client/server boundaries while building or reviewing Velarro routes, components, forms, modals, drawers, cookies, metadata helpers, image integrations, third-party integrations, headers, middleware, config files, or any code that touches user input or browser security.
