performance-expert

Analyze bundle health and Core Web Vitals signals to identify frontend performance bottlenecks.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill performance-expert-mizchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-expert
Source: https://github.com/mizchi/skills/tree/main/frontend/review-perspectives/performance-expert
Command: npx skills add https://github.com/mizchi/skills --skill performance-expert-mizchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams review frontend performance during weekly AI reviews by focusing on bundle size, Core Web Vitals (LCP, CLS, INP), and image/font optimization, while identifying avoidable rework and optimization opportunities.

Core Features & Use Cases

  • Audit bundle health and size to identify excess weight and dead code.
  • Assess Core Web Vitals signals (LCP, CLS, INP) and propose targeted improvements.
  • Identify avoidable rework, layout thrashing, and heavy assets in images and fonts.
  • Evaluate dependency impact and optimization opportunities through provided signals (deps.json, similarity.json).

Quick Start

Run the weekly performance review against the client repository by inspecting the latest bundle.json and lighthouse outputs, then generate a prioritized improvement plan.

Frequently Asked Questions about performance-expert

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

FAQPage Schema
How do I analyze bundle size and Core Web Vitals for my frontend repository?

You can audit bundle health and Core Web Vitals by reading bundle.json and lighthouse.json outputs, then generating a prioritized improvement plan targeting LCP, CLS, and INP signals.

Can I automate frontend performance reviews across multiple repositories?

Yes, you can automate weekly AI reviews across diverse repositories by inspecting the latest bundle and lighthouse outputs to produce a concise, prioritized improvement plan.

What is the best way to identify heavy dependencies causing frontend performance issues?

Evaluating dependency impact through provided signals like deps.json and similarity.json identifies excess weight, dead code, and optimization opportunities to reduce avoidable rework.

Does this performance analysis tool work without pre-existing lighthouse or bundle output files?

This skill reads outputs when available, specifically requiring bundle.json, lighthouse.json, deps.json, and similarity.json files to produce a concise, prioritized report with recommended fixes.

Why does my frontend code have layout thrashing and how can I find avoidable rework?

Assessing Core Web Vitals signals and evaluating heavy assets in images and fonts identifies layout thrashing and avoidable rework, enabling targeted improvements for your frontend code.