MR
Mayur Rathi
@mayurrathi
⭐ 40.7k GitHub stars

Performance Profiling

Performance Profiling is an code AI skill with a core value of Performance profiling principles. It helps developers solve real-world problems in the code domain, boosting efficiency, automating repetitive tasks, and optimizing workflows.

Performance profiling principles. Measurement, analysis, and optimization techniques.

Last verified on: 2026-07-07

Quick Facts

Category code
Works With Claude
Source sickn33/antigravity-awesome-skills
Stars ⭐ 40.7k
Last Verified 2026-07-07
Risk Level Low
mkdir -p ./skills/performance-profiling && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/performance-profiling/SKILL.md -o ./skills/performance-profiling/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# Performance Profiling


> Measure, analyze, optimize - in that order.


🔧 Runtime Scripts


**Execute these for automated profiling:**


| Script | Purpose | Usage |

|--------|---------|-------|

| `scripts/lighthouse_audit.py` | Lighthouse performance audit | `python scripts/lighthouse_audit.py https://example.com` |


---


1. Core Web Vitals


Targets


| Metric | Good | Poor | Measures |

|--------|------|------|----------|

| **LCP** | < 2.5s | > 4.0s | Loading |

| **INP** | < 200ms | > 500ms | Interactivity |

| **CLS** | < 0.1 | > 0.25 | Stability |


When to Measure


| Stage | Tool |

|-------|------|

| Development | Local Lighthouse |

| CI/CD | Lighthouse CI |

| Production | RUM (Real User Monitoring) |


---


2. Profiling Workflow


The 4-Step Process


text
1. BASELINE → Measure current state
2. IDENTIFY → Find the bottleneck
3. FIX → Make targeted change
4. VALIDATE → Confirm improvement

Profiling Tool Selection


| Problem | Tool |

|---------|------|

| Page load | Lighthouse |

| Bundle size | Bundle analyzer |

| Runtime | DevTools Performance |

| Memory | DevTools Memory |

| Network | DevTools Network |


---


3. Bundle Analysis


What to Look For


| Issue | Indicator |

|-------|-----------|

| Large dependencies | Top of bundle |

| Duplicate code | Multiple chunks |

| Unused code | Low coverage |

| Missing splits | Single large chunk |


Optimization Actions


| Finding | Action |

|---------|--------|

| Big library | Import specific modules |

| Duplicate deps | Dedupe, update versions |

| Route in main | Code split |

| Unused exports | Tree shake |


---


4. Runtime Profiling


Performance Tab Analysis


| Pattern | Meaning |

|---------|---------|

| Long tasks (>50ms) | UI blocking |

| Many small tasks | Possible batching opportunity |

| Layout/paint | Rendering bottleneck |

| Script | JavaScript execution |


Memory Tab Analysis


| Pattern | Meaning |

|---------|---------|

| Growing heap | Possible leak |

| Large retained | Check references |

| Detached DOM | Not cleaned up |


---


5. Common Bottlenecks


By Symptom


| Symptom | Likely Cause |

|---------|--------------|

| Slow initial load | Large JS, render blocking |

| Slow interactions | Heavy event handlers |

| Jank during scroll | Layout thrashing |

| Growing memory | Leaks, retained refs |


---


6. Quick Win Priorities


| Priority | Action | Impact |

|----------|--------|--------|

| 1 | Enable compression | High |

| 2 | Lazy load images | High |

| 3 | Code split routes | High |

| 4 | Cache static assets | Medium |

| 5 | Optimize images | Medium |


---


7. Anti-Patterns


| ❌ Don't | ✅ Do |

|----------|-------|

| Guess at problems | Profile first |

| Micro-optimize | Fix biggest issue |

| Optimize early | Optimize when needed |

| Ignore real users | Use RUM data |


---


> **Remember:** The fastest code is code that doesn't run. Remove before optimizing.


When to Use

This skill is applicable to execute the workflow or actions described in the overview.

🎯 Best For

  • Claude users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • Code quality improvement
  • Best practice enforcement

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Performance Profiling to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is Performance Profiling compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Performance Profiling?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Performance Profiling?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/performance-profiling/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills