Eng performance

Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.From its SKILL.md

Install

npx -y skills add tjboudreaux/cc-engineering-skills --skill eng-performance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.6 KB, as published. Nobody here has run it

Treat budgets (frame time, network round-trips, server CPU, on-chain gas) as first-class requirements.
Prevent regressions by profiling early, not after user complaints.

Existing SLAs/budgets per platform (FPS, TTI, API latency, contract gas caps).
Representative workloads, datasets, replays, or load scripts.
Tooling: profilers, flamegraphs, shader analyzers, gas estimators, Lighthouse, etc.

Establish baseline
- Capture metrics for the current implementation under realistic load/device tiers.
Design with budgets
- Choose data structures, rendering strategies, and contract patterns aligned with constraints.
- Consider caching, pagination, batching, and compression aggressively.
Measure iteratively
- After each significant change, run targeted benchmarks or simulations.
- Track results in the PR/issue; highlight deltas and why they are acceptable.
Optimize where it matters
- Focus on user-facing bottlenecks; avoid premature micro-optimizations.
- For web3, minimize storage writes and external calls; for mobile, monitor battery/thermal impact.

Benchmarks or profiling output attached, showing no regression (or justified improvements).
Budgets documented; alarms/alerts configured if applicable.
For regressions that cannot be fixed immediately, open a follow-up issue with owner, impact, and mitigation.