language-performance-safety

What problem does it solve?

It prevents performance regressions and safety bugs by forcing language- and runtime-specific changes to be validated with evidence rather than intuition.

Core Features & Use Cases

• Evidence-first performance validation: requires profiling, traces, allocation logs, and system-level benchmarks to justify optimizations.
• Runtime safety guardrails: covers allocation/GC behavior, event-loop and scheduler interaction, async cancellation, blocking work, and unsafe/FFI invariants.
• Bounded resource practices: mandates explicit ceilings for queues, collections, batches, pagination windows, retry accumulators, caches, and fan-out to avoid OOM and denial-of-service patterns.

Quick Start

Ask the skill to evaluate your proposed hot-path or safety-critical change and return the measurement plan, required evidence, and accept/reject criteria.