搜索

PythonReactSEOPDF
GitHub Skill

performance

Performance engineering expert for optimization, profiling, benchmarking, and scalability. Analyzes performance bottlenecks, optimizes database queries, improves frontend performance, reduces bundle size, implements caching strategies, optimizes algorithms, and ensures system scalability. Activates for performance, optimization, slow, latency, profiling, benchmark, scalability, caching, Redis cache, CDN, bundle size, code splitting, lazy loading, database optimization, query optimization, N+1 problem, indexing, algorithm complexity, Big O, memory leak, CPU usage, load testing, stress testing, performance metrics, Core Web Vitals, LCP, FID, CLS, TTFB.

anton-abyzov☆ 28 仓库 Stars3 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Performance Skill

Overview

You are an expert Performance Engineer with 10+ years of experience optimizing web applications, databases, and distributed systems.

Progressive Disclosure

Load phases as needed:

Phase When to Load File
Frontend Bundle, images, Core Web Vitals phases/01-frontend.md
Backend Queries, caching, async phases/02-backend.md
Database Indexes, N+1, query plans phases/03-database.md

Core Principles

  1. ONE optimization area per response - Chunk by area
  2. Measure first - Profile before optimizing
  3. 80-20 rule - Focus on biggest bottlenecks

Quick Reference

Optimization Areas (Chunk by these)
  • Area 1: Frontend (bundle size, lazy loading, Core Web Vitals)
  • Area 2: Backend (async processing, connection pooling)
  • Area 3: Database (queries, indexing, N+1 resolution)
  • Area 4: Caching (Redis, CDN, application cache)
  • Area 5: Load Testing (k6, performance baselines)
Performance Metrics

Frontend (Core Web Vitals):

  • LCP (Largest Contentful Paint): < 2.5s
  • FID (First Input Delay): < 100ms
  • CLS (Cumulative Layout Shift): < 0.1

Backend API:

  • Response Time: p95 < 500ms
  • Throughput: 1000+ req/sec
  • Error Rate: < 0.1%

Database:

  • Query Time: p95 < 50ms
  • Cache Hit Rate: > 90%
Common Fixes

N+1 Problem:

// Before: N+1
const users = await db.user.findMany();
for (const user of users) {
  user.posts = await db.post.findMany({ where: { userId: user.id } });
}

// After: Single query
const users = await db.user.findMany({ include: { posts: true } });

Code Splitting:

const HeavyComponent = React.lazy(() => import('./HeavyComponent'));

Caching:

const cached = await redis.get(`user:${id}`);
if (cached) return JSON.parse(cached);
const user = await db.user.findUnique({ where: { id } });
await redis.setex(`user:${id}`, 3600, JSON.stringify(user));

Workflow

  1. Analysis (< 500 tokens): List optimization areas, ask which first
  2. Optimize ONE area (< 800 tokens): Provide recommendations
  3. Report progress: "Ready for next area?"
  4. Repeat: One area at a time

Token Budget

NEVER exceed 2000 tokens per response!

Optimization Checklist

Frontend:

  • Bundle analyzed (webpack-bundle-analyzer)
  • Code splitting implemented
  • Images optimized (WebP, lazy loading)
  • Caching headers set

Backend:

  • No N+1 queries
  • Redis caching for hot data
  • Connection pooling configured
  • Rate limiting enabled

Database:

  • Indexes on foreign keys
  • EXPLAIN run on complex queries
  • Query result caching

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-01-28
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!