picky-performance

Identify and quantify web application performance bottlenecks with scored reports and fixes.

5|Updated Jan 28, 2026

Search Tags:#performance #frontend #optimization #audit #lighthouse #core-web-vitals

Ready to run

npx skills add https://github.com/kiruna-labs/picky-skills --skill picky-performance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: picky-performance
Source: https://github.com/kiruna-labs/picky-skills/tree/main/picky-performance
Command: npx skills add https://github.com/kiruna-labs/picky-skills --skill picky-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Picky-performance identifies and quantifies performance bottlenecks in web applications, delivering a prioritized set of exact fixes with measurable impact.

Core Features & Use Cases

Core Web Vitals focus: LCP, INP, CLS, TTFB, FCP, and TTI measurement with actionable improvements.
Exhaustiveness: bundle size analysis, code splitting, caching strategies, image/font optimization, and runtime performance.
Use Case: A developer pushes a new build and receives a scored report detailing where to optimize and how many milliseconds or kilobytes will be saved, enabling fast, iterative improvements.

Quick Start

Run a picky-performance audit on your project to generate a scored report with exact measurements and fixes.

Frequently Asked Questions about picky-performance

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

FAQPage Schema

How do I audit my web application for Core Web Vitals and identify exact fixes?▼

To audit Core Web Vitals, you can run a performance audit that measures LCP, INP, CLS, TTFB, FCP, and TTI, returning a scored report with file:line references and recommended code changes to resolve bottlenecks.

What is the best way to find frontend performance bottlenecks in a web app?▼

The best way to find frontend performance bottlenecks is through runtime and network profiling that quantifies issues like large bundle sizes and poor caching, providing a prioritized list of fixes with measurable millisecond or kilobyte savings.

Do I need Chrome DevTools to measure Lighthouse scores for frontend optimization?▼

Yes, you need Chrome DevTools MCP to run Lighthouse measurements for frontend optimization, which enables the audit to capture precise runtime metrics and generate actionable improvements for your web application.

How does runtime profiling help with optimizing web application assets?▼

Runtime profiling identifies and quantifies network and rendering bottlenecks, allowing you to target specific asset optimizations like code splitting, image and font delivery, and caching strategies to reduce overall load times.

Can I get specific code recommendations for improving Core Web Vitals like LCP and INP?▼

Yes, you can get specific code recommendations for improving Core Web Vitals like LCP and INP, as the audit outputs precise file:line references alongside suggested code changes to achieve measurable performance gains.

Why does my web app have a poor Lighthouse performance score despite code splitting?▼

A poor Lighthouse performance score despite code splitting may result from unoptimized runtime execution, inadequate caching strategies, or heavy image and font assets, which a comprehensive performance audit can identify and quantify.