sickn33/antigravity-awesome-skills/performance-optimizer
- community
Checking that the SKILL.md file is still in the repository.
Identifies and fixes performance bottlenecks in code, databases, and APIs. Measures before and after to prove improvements.
Install
npx vskill@latest install sickn33/antigravity-awesome-skills/performance-optimizerSKILL.md
Performance Optimizer
Find and fix performance bottlenecks. Measure, optimize, verify. Make it fast.
When to Use This Skill
- App is slow or laggy
- User complains about performance
- Page load times are high
- API responses are slow
- Database queries take too long
- User mentions "slow", "lag", "performance", or "optimize"
The Optimization Process
1. Measure First
Never optimize without measuring:
What to measure:
- Page load time
- API response time
- Database query time
- Function execution time
- Memory usage
- Network requests
2. Find the Bottleneck
Use profiling tools to find the slow parts:
Browser:
Node.js:
Database:
3. Optimize
Fix the slowest thing first (biggest impact).
Common Optimizations
Database Queries
Problem: N+1 Queries
Problem: Missing Index
Problem: SELECT *
Problem: No Pagination
API Performance
Problem: No Caching
Problem: Sequential Operations
Problem: Large Payloads
Frontend Performance
Problem: Unnecessary Re-renders
Problem: Large Bundle
Problem: No Code Splitting
Problem: Unoptimized Images
Algorithm Optimization
Problem: Inefficient Algorithm
Problem: Repeated Calculations
Memory Optimization
Problem: Memory Leak
Problem: Large Data in Memory
Correctness and benchmark boundaries
The two findDuplicates examples have different output semantics: the nested loop repeats an item per matching pair, while the Set version emits each duplicated value once (and equality differs for NaN). Define the required contract before changing algorithms. The stats cache is suitable only for shared public data; user/tenant-specific results need authorized keys and invalidation. Streaming must handle errors/backpressure and asynchronous processing. EXPLAIN ANALYZE executes the query; approve target/load before use. All timings/sizes below are illustrative, not observed results: compare representative repeated runs with workload/environment/sample statistics and regression checks.
Measuring Impact
Always measure before and after:
Performance Budgets
Set targets:
Tools
Browser:
- Chrome DevTools Performance tab
- Lighthouse (audit)
- Network tab (waterfall)
Node.js:
node --prof(profiling)clinic(diagnostics)autocannon(load testing)
Database:
EXPLAIN ANALYZE(query plans)- Slow query log
- Database profiler
Monitoring:
- New Relic
- Datadog
- Sentry Performance
Quick Wins
Easy optimizations with big impact:
- Add database indexes on frequently queried columns
- Enable gzip compression on server
- Add caching for expensive operations
- Lazy load images and heavy components
- Use CDN for static assets
- Minify and compress JavaScript/CSS
- Remove unused dependencies
- Use pagination instead of loading all data
- Optimize images (WebP, proper sizing)
- Enable HTTP/2 on server
Optimization Checklist
- [ ] Measured current performance
- [ ] Identified bottleneck
- [ ] Applied optimization
- [ ] Measured improvement
- [ ] Verified functionality still works
- [ ] No new bugs introduced
- [ ] Documented the change
When NOT to Optimize
- Premature optimization (optimize when it's actually slow)
- Micro-optimizations (save 1ms when page takes 5 seconds)
- Readable code is more important than tiny speed gains
- If it's already fast enough
Key Principles
- Measure before optimizing
- Fix the biggest bottleneck first
- Measure after to prove improvement
- Don't sacrifice readability for tiny gains
- Profile in production-like environment
- Consider the 80/20 rule (20% of code causes 80% of slowness)
Related Skills
@database-design- Query optimization@codebase-audit-pre-push- Code review@bug-hunter- Debugging
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/performance-optimizer/SKILL.md
Popularity
- Repository stars
- 24,249
- Repository forks
- 4,172
- Repository npm downloads, 7 days
- 12,395
- 7-day trend score
- 71
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 17 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/sickn33/antigravity-awesome-skills/performance-optimizer)