frontend-performance-review
Review React or web UI implementation for user-visible performance issues. Use when building or optimizing React/Next.js pages, components, data fetching, or bundles.
SKILL.mdskills/frontend-performance-review/SKILL.md
GitHubFrontend Performance Review
Prioritize measured user impact and avoid mechanical micro-optimization.
- Trace the route/component render path and identify waterfalls, redundant requests, large bundles, expensive computations, and avoidable rerenders.
- Check server/client boundaries, streaming, caching, hydration, image delivery, and code splitting as relevant to the framework.
- Prefer parallel data loading when dependencies allow it; do not parallelize dependent operations.
- Reduce client JavaScript and defer non-critical work without harming accessibility or correctness.
- Inspect list rendering, memoization, state placement, and expensive visual updates only when evidence suggests they matter.
- Establish before/after evidence with profiler, build output, network trace, or reproducible benchmark.
- Check that optimization does not introduce stale data, race conditions, layout shift, or harder-to-maintain code.
Follow current project/framework documentation. Do not claim a speedup without comparable measurements. This skill is a review checklist, not a substitute for profiling.