From f5-core
Provides performance optimization strategies for caching with Redis, database queries, API pagination and compression, frontend bundle splitting and Core Web Vitals, plus scaling techniques. Targets TTFB, LCP, FID metrics.
npx claudepluginhub fujigo-software/f5-framework-claude --plugin f5-coreThis skill is limited to using the following tools:
Performance optimization knowledge for building fast, scalable applications
api/async-processing.mdapi/batch-operations.mdapi/pagination.mdapi/response-compression.mdcaching/cache-invalidation.mdcaching/caching-strategies.mdcaching/cdn-caching.mdcaching/http-caching.mdcaching/redis-caching.mddatabase/connection-pooling.mddatabase/indexing-strategies.mddatabase/n-plus-one.mddatabase/query-optimization.mdfrontend/bundle-optimization.mdfrontend/core-web-vitals.mdfrontend/image-optimization.mdfrontend/lazy-loading.mdfundamentals/benchmarking.mdfundamentals/bottleneck-analysis.mdfundamentals/performance-metrics.mdOptimizes performance in React, Next.js, NestJS apps covering frontend rendering, API response times, MongoDB queries, and AWS infrastructure like CloudFront and Lambda.
Optimizes application performance via measure-identify-fix-verify workflow. Use for Core Web Vitals, load times, regressions, or profiling bottlenecks.
Optimizes performance: audits frontend Core Web Vitals with Lighthouse, profiles backends (Node/Python/Go), tunes databases (EXPLAIN ANALYZE/indexing), load tests with k6/Gatling.
Share bugs, ideas, or general feedback.
Performance optimization knowledge for building fast, scalable applications that provide excellent user experience.
| Metric | Target | Description |
|---|---|---|
| TTFB | < 200ms | Time to First Byte |
| FCP | < 1.8s | First Contentful Paint |
| LCP | < 2.5s | Largest Contentful Paint |
| FID | < 100ms | First Input Delay |
| CLS | < 0.1 | Cumulative Layout Shift |
| API Response | < 200ms | P95 response time |
| Database Query | < 50ms | P95 query time |
| Memory Usage | < 80% | Application memory threshold |
╱╲
╱ ╲ CDN / Edge
╱────╲
╱ ╲ Application Cache
╱────────╲
╱ ╲ Database Optimization
╱────────────╲
╱ ╲ Code Optimization
╱________________╲ Infrastructure
| Operation Type | Target | Maximum |
|---|---|---|
| Static assets | < 50ms | 100ms |
| API read | < 100ms | 200ms |
| API write | < 200ms | 500ms |
| Search | < 200ms | 500ms |
| Report generation | < 2s | 5s |
| File upload | < 5s | 30s |
| Data Type | Cache Location | TTL |
|---|---|---|
| Static assets | CDN | 1 year |
| User session | Redis | 30 min |
| User profile | Redis | 1 hour |
| Product catalog | Redis + CDN | 6 hours |
| Search results | Redis | 5 min |
| Config | Memory | 24 hours |
Performance requirements should be defined in quality gates:
# .f5/quality/gates-status.yaml
gates:
G2:
performance:
api_p95_response: "< 200ms"
database_p95_query: "< 50ms"
memory_usage: "< 80%"
Performance requirements should be traceable:
// NFR-PERF-001: API response time must be under 200ms at P95
export async function getUser(id: string): Promise<User> {
// implementation
}