performance

Performance - Core Web Vitals, bundle size. Use when optimizing speed.

⭐4stars🔀3forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill is a specialized performance optimization suite designed for modern web development, particularly within the Next.js and Vercel ecosystems. It focuses on auditing and improving Core Web Vitals (LCP, CLS, INP) and reducing JavaScript bundle sizes. By analyzing critical rendering paths and identifying architectural bottlenecks, the skill helps developers eliminate latency, improve SEO rankings, and ensure a seamless, 'instant' user experience.

Use Cases

  • Core Web Vitals Optimization: Diagnosing and fixing performance issues to meet strict thresholds for Largest Contentful Paint (LCP < 2.5s), Cumulative Layout Shift (CLS < 0.1), and Interaction to Next Paint (INP < 200ms).
  • Bundle Size Reduction: Identifying bloated dependencies and unoptimized code within Bun or Next.js projects to decrease load times and improve interactivity.
  • Critical Path Analysis: Auditing the rendering sequence to remove blocking resources and prioritize the delivery of visible content to the user.
  • Performance Regression Testing: Establishing monitoring patterns to detect when new features or architectural changes negatively impact site speed or engagement metrics.
  • Infrastructure Bottleneck Identification: Analyzing slow database queries and server-side execution times to optimize the full-stack performance of Vercel-hosted applications.
nameperformance
descriptionPerformance - Core Web Vitals, bundle size. Use when optimizing speed.

Performance Guideline

Tech Stack

  • Framework: Next.js (SSR/ISR/Static)
  • Platform: Vercel
  • Tooling: Bun

Non-Negotiables

  • Core Web Vitals must meet thresholds (LCP < 2.5s, CLS < 0.1, INP < 200ms)
  • Performance regressions must be detectable

Context

Performance is a feature. Slow products feel broken, even when they're correct. Users don't read loading spinners — they leave. Every 100ms of latency costs engagement.

Don't just measure — understand. Where does time go? What's blocking the critical path? What would make the product feel instant? Sometimes small architectural changes have bigger impact than optimization.

Driving Questions

  • What makes the product feel slow to users?
  • Where are the biggest bottlenecks in the critical user journeys?
  • What's in the critical rendering path that shouldn't be?
  • How large is the JavaScript bundle, and what's bloating it?
  • What database queries are slow, and why?
  • If we could make one thing 10x faster, what would have the most impact?