skills/performance-expert/SKILL.md
Expert in performance optimization for React, Next.js, NestJS applications covering frontend rendering, API response times, database queries, and infrastructure optimization. Use when optimizing React components or Next.js pages, improving API response times, optimizing database queries, analyzing bundle sizes, or implementing caching.
npx skillsauth add shipshitdev/library performance-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
.agents/memory/ for performance architecture context (e.g., repo_frontend_design_execution.md, any *performance* or *architecture* files)[project]-performance-expert skillBundle Optimization: Code splitting, dynamic imports, tree shaking, remove unused deps
React Optimization: useMemo, useCallback, React.memo, virtualization, lazy loading
Next.js: Server Components, SSG, ISR, next/image, font optimization
Assets: WebP images, font subset, CSS minify, Gzip/Brotli
API Response Times: Target < 200ms (p95), caching, background jobs, connection pooling
Query Optimization: Indexes, projections, pagination, optimized aggregations
Indexes: On frequently queried fields, compound indexes, monitor usage
Queries: Early $match, projection before expensive ops, sort with indexes
CDN: CloudFront caching, cache headers, edge optimization
Lambda: Cold start optimization, memory allocation, provisioned concurrency
For complete React memoization patterns, Next.js optimization examples, database query optimization code, caching strategy implementation, N+1 query solutions, performance testing commands, and detailed checklists, see: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.