performance

Identifies performance bottlenecks using a measurement-first approach across frontend and backend.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/Barryrn/saas-setup --skill performance-barryrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance
Source: https://github.com/Barryrn/saas-setup/tree/main/.claude/skills/performance
Command: npx skills add https://github.com/Barryrn/saas-setup --skill performance-barryrn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams measure performance bottlenecks and drive improvements by adopting a measurement-first approach, reducing guesswork and wasted optimization.

Core Features & Use Cases

  • Instrumentation guidance for frontend and backend workloads.
  • Performance budgeting and goal-setting to align teams on targets.
  • Real-world use cases including speeding initial load, reducing latency for APIs, and improving perceived performance with skeleton screens and optimistic updates.

Quick Start

Measure current performance, identify the top bottlenecks, and apply targeted optimizations with instrumentation and budgets.

Frequently Asked Questions about performance

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

FAQPage Schema
How do I identify frontend performance bottlenecks using a measurement-first approach?

To identify frontend performance bottlenecks, measure current metrics like FCP, LCP, TTI, and CLS using profiling tools, then apply targeted optimizations such as code-splitting and skeleton screens.

What is the best way to reduce API latency and database query bottlenecks?

Reduce API latency and database query bottlenecks by instrumenting backend workloads to measure p95 and p99 response times, then applying targeted caching patterns to optimize slow queries.

How does performance budgeting align teams on optimization goals?

Performance budgeting aligns teams on optimization goals by setting strict metric targets for pages and APIs, reducing guesswork and ensuring targeted improvements for real speed.

Can I improve perceived performance for initial page loads without heavy refactoring?

Improve perceived performance for initial page loads by implementing skeleton screens and optimistic updates, which provide visual feedback to users while content is still loading.

Does this approach work for both frontend and backend workloads?

Yes, this measurement-first approach works across both frontend and backend workloads, prescribing specific metrics and tooling guidance for profiling pages, APIs, and database queries.

Why should I measure performance before applying optimizations?

You should measure performance before applying optimizations to eliminate guesswork and wasted effort, ensuring you directly target the actual bottlenecks slowing down your pages and APIs.