Performance Budgeting
Set and manage frame, load, memory, streaming, or bandwidth budgets before performance debt becomes structural.
Install
$ agentstack add skill-mrcalderon3d-everything-game-dev-code-performance-budgeting ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mrcalderon3d-everything-game-dev-code-performance-budgeting) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Performance Budgeting
Purpose
Set and manage frame, load, memory, streaming, or bandwidth budgets before performance debt becomes structural.
Use When
- target hardware is defined
- performance problems are emerging
- content scale is increasing
Inputs
- target platforms
- feature set
- technical architecture
- content assumptions
Process
- set budgets by platform and major runtime mode
- allocate budget ownership by system or content class
- choose representative benchmark scenarios
- review regressions at milestone checkpoints
- link descopes or optimization work to measured overages
Outputs
- budget sheet
- owner-by-budget map
- benchmark scenarios
- regression review cadence
Quality Bar
- budgets are set per system (frame time, memory, draw calls, asset sizes) against the weakest target device
- every budget has an owner and a repeatable measurement method
- regressions are caught by measurement at integration time, not discovered in QA
- budget exceptions are negotiated and recorded, not silently absorbed
Common Failure Modes
- budgets defined as totals with no per-system allocation, so no one owns overruns
- profiling only on developer hardware, missing the real target floor
- performance treated as a polish-phase task instead of a standing budget
- one-off optimizations that decay because no measurement guards them
Related Agents
- performance-reviewer
- producer
- technical-artist
Related Commands
- perf-budget
- verify
- release-check
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MRCalderon3D
- Source: MRCalderon3D/everything-game-dev-code
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.