addy-performance-optimization

Diagnoses and fixes frontend and backend performance bottlenecks using measurement-driven workflows.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill addy-performance-optimization-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-performance-optimization
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/addy-performance-optimization
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill addy-performance-optimization-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Slow applications hurt user experience and conversion, but optimizing without measurement wastes effort on the wrong things. This Skill enforces a measure-first workflow so you fix the actual bottleneck — whether it's Core Web Vitals, N+1 queries, or oversized bundles — and verify the fix with real numbers. ## Core Features & Use Cases - Measure-Identify-Fix-Verify-Guard Workflow: A five-step process that establishes baselines with synthetic (Lighthouse, DevTools) and RUM (web-vitals, CrUX) data before touching code. - Anti-Pattern Fixes with Code Examples: Ready-to-apply fixes for N+1 queries, unbounded fetching, unoptimized images, unnecessary React re-renders, large bundles, and missing caching. - Performance Budgets & CI Enforcement: Concrete budgets (JS < 200KB gzipped, API p95 < 200ms, Lighthouse ≥ 90) with bundlesize and Lighthouse CI commands. - Use Case: Your product page has an LCP of 4.5s. Use this Skill to trace the network waterfall, identify a render-blocking hero image, apply responsive AVIF/srcset markup with fetchpriority, and re-measure to confirm the improvement beats run-to-run variance. ## Quick Start Ask the agent to profile the slow page load on your app, identify the bottleneck, and propose a measured fix using the performance optimization skill.

Frequently Asked Questions about addy-performance-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve Core Web Vitals scores like LCP and INP?▼

Improve Core Web Vitals by measuring first with Lighthouse and the web-vitals library, then targeting the specific bottleneck. For LCP, optimize hero images with AVIF, srcset, and fetchpriority; for INP, break up long tasks over 50ms on the main thread.

How to fix N+1 query problems in a backend API?▼

Fix N+1 queries by replacing per-record lookups with a single query using joins or eager loading, such as Prisma's include option. Also paginate list endpoints with take and skip instead of fetching unbounded result sets.

What is a good performance budget for a web app?▼

A solid budget is JavaScript under 200KB gzipped for initial load, CSS under 50KB, images under 200KB above the fold, API p95 response under 200ms, and a Lighthouse performance score of at least 90. Enforce it in CI with bundlesize and Lighthouse CI.

Should I use React.memo and useMemo everywhere to speed up React?▼

No, overusing React.memo and useMemo is as harmful as underusing them. Apply memoization only where profiling shows expensive re-renders or computations, and verify the change actually improves measured interaction times.

When should I not optimize application performance?▼

Do not optimize before you have profiling evidence of a real problem. Premature optimization adds complexity that costs more than the performance it gains, and neutral changes that don't beat baseline variance should be reverted, not kept.