← ClaudeAtlas

performance-reviewlisted

Use as a review dimension on any diff that could cost startup time, frames, memory, battery, bandwidth or bundle size — by code-reviewer during review and by web-developer and test-automation-engineer before claiming a UI or harness ticket done. The studio's position is that this is a dimension with existing auditors behind it, not a standing role.
vmobifystudio/app-dev-team · ★ 4 · Code & Development · score 74
Install: claude install-skill vmobifystudio/app-dev-team
# Performance review Performance is a budget, and a budget only exists if something can exceed it. The budgets live in `docs/20-architecture.md` §8; if that section is empty, that is the finding. Spawn the platform auditor first and fold its findings in — `axiom:swiftui-performance-analyzer`, `axiom:swift-performance-analyzer`, `axiom:memory-auditor`, `axiom:energy-auditor` on Apple platforms. **All external and optional** (separate plugins) — missing → record `N/A: <tool> — not installed`, walk the list below by hand, never file the absence as a defect. ## Measure, then read the diff **A performance finding with no number is an opinion.** Every finding names: the metric, the value, the budget it is measured against, the device or environment, and the build. Where you could not measure, the verdict is `CANNOT EVALUATE` — not a guess dressed as a warning. ## The dimensions | Dimension | Budget it spends | What to look for in a diff | |---|---|---| | Startup | cold launch to first interaction | work moved into app init, eager singletons, sync I/O on the launch path | | Frames | 60/120fps, jank-free scroll | layout or allocation per frame, unbounded list without recycling, expensive work in a view body | | Memory | peak and steady-state | full-size images held, unbounded caches, retain cycles, accumulating observers | | Battery / energy | background and foreground drain | polling instead of push, wake locks, continuous location, timers that never stop | | Network | bytes a