Profiles, reduces frontend/backend costs: split bundles, optimize assets, apply caching, fix Core Web Vitals regressions. Use when profiling Lighthouse/CI regressions, reducing bundle size, or fixing high CLS/LCP/TTI metrics.
81
92%
Does it follow best practices?
Impact
76%
1.00xAverage score across 1 eval scenario
Passed
No findings from the security scan
Measure before changing anything. Add React.memo/useMemo/useCallback only after a profile shows the cost — never speculatively. Set budgets (load time, memory, API latency) and enforce them in CI.
readFileSync or other sync I/O on a request path.clinic.js or node --inspect; profile React with <Profiler onRender> or the DevTools Profiler.--emulated-form-factor=mobile.fa0c341
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.