Guide for analyzing and improving application performance including identifying bottlenecks, implementing caching, and optimizing queries. This skill should be used when reviewing performance issues or optimizing code.
View on GitHubcharlesjones-dev/claude-code-plugins-dev
ai-performance
plugins/ai-performance/skills/performance-auditing/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/charlesjones-dev/claude-code-plugins-dev/blob/main/plugins/ai-performance/skills/performance-auditing/SKILL.md -a claude-code --skill performance-auditingInstallation paths:
.claude/skills/performance-auditing/# Performance Audit Skill This skill provides elite performance engineering expertise for making applications lightning-fast through systematic optimization. ## When to Use This Skill Invoke this skill when: - Analyzing slow page loads or response times - Identifying performance bottlenecks in code execution - Designing and implementing caching strategies - Optimizing database queries and preventing N+1 problems - Reducing memory consumption or investigating memory leaks - Improving asset delivery (compression, minification, bundling) - Implementing lazy loading or code splitting - Profiling and benchmarking code performance - Reviewing new features for performance implications - Establishing performance budgets for critical user journeys ## Core Performance Expertise ### 1. Performance Analysis Methodology To analyze performance issues effectively: **Measure First**: Always establish baseline metrics before optimization. Use profiling tools, timing measurements, and performance monitoring to identify actual bottlenecks rather than assumed ones. **Prioritize Impact**: Focus on optimizations that provide the greatest performance improvement relative to implementation effort. Target the critical path and high-traffic code paths first. **Consider Trade-offs**: Evaluate each optimization for its impact on code maintainability, complexity, and resource usage. Sometimes a 10% performance gain isn't worth a 50% increase in code complexity. **Validate Improvements**: After implementing optimizations, measure again to confirm actual performance gains. Be prepared to roll back changes that don't deliver meaningful improvements. ### 2. Caching Strategies To implement effective caching: - Choose the appropriate caching layer (browser cache, CDN, application cache, database query cache, computed result cache) - Implement proper cache invalidation strategies to prevent stale data issues - Use cache keys that are specific enough to avoid collisions but general enough