Write, review, and refactor React and Next.js code using performance guidelines from Vercel. Prioritized rules help identify sequential data requests, oversized JavaScript bundles, unnecessary re-renders, and other opportunities to improve loading and responsiveness.
- Reviewing React components for performance issues
- Improving data fetching in Next.js pages
- Reducing JavaScript bundle size
calesthio/OpenMontage☆ 69.6KUpdated Oct 17, 2026
Write, review, or refactor React and Next.js code using prioritized performance guidelines. Address sequential data requests, large bundles of browser code, server work, and unnecessary rendering, with explanations and code examples for each rule.
- Writing React components with performance in mind
- Reviewing Next.js data fetching
- Reducing browser code size and loading time
CherryHQ/cherry-studio☆ 52.7KUpdated Oct 19, 2026
Guide Angular development, code review, and refactoring with prioritized performance rules. Review rendering efficiency, loading time, and bundle size—the amount of code delivered to browsers—alongside data fetching and server-rendered page setup.
- Writing Angular components with performance in mind
- Reviewing code for performance bottlenecks
- Reducing bundle size and loading time
sickn33/agentic-awesome-skills☆ 47.9KUpdated Oct 19, 2026
Diagnose slow Power BI reports, data refreshes, and queries through structured measurement and troubleshooting. Get recommendations for data models, DAX calculation formulas, report layouts, and infrastructure, with guidance for validating improvements and ongoing monitoring.
- Diagnose slow report pages and visual interactions
- Investigate data refresh delays
- Review slow DAX calculations and queries
github/awesome-copilot☆ 40.2KUpdated Oct 15, 2026
Run performance improvements as a measured workflow in OMX and Codex goal mode. Define an evaluation command and success criteria, make small reversible changes, and retain evidence before declaring the work complete.
- Reducing CLI startup time against a defined target
- Repeating improvements with benchmarks and regression tests
- Recording evaluation results and blockers
Yeachan-Heo/oh-my-codex☆ 33.6KUpdated Oct 18, 2026
Write, review, and refactor React and Next.js code using performance guidelines ranked by impact. Covers sequential data requests, downloaded code size, server work, and unnecessary rendering to guide concrete implementation improvements.
- Review React and Next.js code for performance issues
- Improve data fetching that waits on sequential requests
- Reduce downloaded code size and loading time
vercel-labs/agent-skills☆ 32.6KUpdated Oct 15, 2026
Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.
- Review a Handsontable branch or pull request
- Check architecture before or during core changes
- Review keyboard access and performance concerns
handsontable/handsontable☆ 22.1KUpdated Oct 19, 2026
Write and refactor C++20/23 applications, addressing memory management, concurrency, and performance bottlenecks. Produce interfaces, implementations, tests, and relevant CMake updates, then check runtime errors and measure performance before applying targeted optimizations.
- Refactoring existing code with C++20/23 features
- Investigating memory errors and undefined behavior
- Improving performance through profiling and benchmarks
Jeffallan/claude-skills☆ 11.9KUpdated Oct 17, 2026
Diagnose slow loading, high memory use, and low frame rates in USD 3D scenes. Coordinate scene structure checks, validation, optimization, and before-and-after performance comparisons, then produce a report documenting findings and changes.
- Investigating slow USD scene loading
- Diagnosing low frame rates in CAD scenes
- Investigating high GPU or system memory use
openai/plugins☆ 7.5KUpdated Oct 8, 2026
Apply Vercel Engineering’s performance guidelines when writing, reviewing, or refactoring React and Next.js code. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering using rules with explanations and code examples.
- Review React components for performance issues
- Improve data fetching in Next.js pages
- Reduce downloaded code and loading time
openai/plugins☆ 7.5KUpdated Oct 8, 2026
Write, review, and refactor React and Next.js code using performance guidelines from Vercel Engineering. Prioritize improvements to data fetching, downloaded code size, server processing, and unnecessary rendering, with rule files providing explanations and code examples.
- Reviewing React code for performance issues
- Reducing delays in Next.js data fetching
- Reducing downloaded code size and load times
tech-leads-club/agent-skills☆ 7.1KUpdated Oct 17, 2026
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, and set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget. Do NOT use for fixing specific performance issues (use perf-web-optimization or core-web-vitals) or Astro-specific optimization (use perf-astro).
The English summary is being prepared. Showing the original description.
tech-leads-club/agent-skills☆ 7.1KUpdated Oct 17, 2026
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.
The English summary is being prepared. Showing the original description.
rmyndharis/antigravity-skills☆ 1.8KUpdated Oct 15, 2026
Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.
The English summary is being prepared. Showing the original description.
dzhng/skills☆ 1.4KUpdated Oct 16, 2026
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.
The English summary is being prepared. Showing the original description.
getsentry/skills☆ 1.1KUpdated Oct 16, 2026
Use when you need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports. This should trigger for requests such as Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support; Review Gatling performance test assertions and feeders. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
jabrena/plinth☆ 453Updated Oct 15, 2026
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents performance management appropriately.
The English summary is being prepared. Showing the original description.
w95/awesome-claude-corporate-skills☆ 261Updated Feb 27, 2026
Test application performance with k6 load/stress/soak/spike scripts and k6 scenarios, Lighthouse CI for Web Vitals, and performance budgets as CI gates. Covers load profiles, custom metrics, bottleneck identification, and Core Web Vitals (LCP, INP, CLS). Use when: "performance test," "load test," "stress test," "soak test," "spike test," "k6," "k6 scenarios," "Lighthouse," "Web Vitals," "Core Web Vitals," "performance budget." Not for: scheduled production probes — use synthetic-monitoring; pixel-diff regressions — use visual-testing; designing tests from prod telemetry — use observability-driven-testing. Related: ci-cd-integration, qa-metrics, release-readiness.
The English summary is being prepared. Showing the original description.
petrkindlmann/qa-skills☆ 191Updated Jun 11, 2026
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
The English summary is being prepared. Showing the original description.
bg-szy/TOP-SKILLS☆ 6Updated Sep 8, 2026
Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, traffic drops, content gaps, search visibility, technical SEO, meta tags, schema markup, structured data, URL indexing, keyword research, indexing issues, page speed, performance, Core Web Vitals, LCP, INP, CLS, or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "crawl errors", "content strategy", "keyword cannibalization", "search intent", "schema markup", "structured data", "URL inspection", "page speed", "performance score", "core web vitals", "lighthouse", or any organic search question. If in doubt, trigger. This skill handles everything from quick GSC checks to deep technical audits with performance monitoring.
The English summary is being prepared. Showing the original description.
0xAidan/polymarket-bot-test☆ 4Updated Sep 4, 2026
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.
The English summary is being prepared. Showing the original description.
0xAidan/polymarket-bot-test☆ 4Updated Sep 4, 2026
Generates a polished, leadership-ready performance briefing with KPI tiles, executive narrative bullets, and a driver analysis — all as a print-ready HTML document. Always use this skill when someone asks for an executive summary, performance briefing, leadership readout, stakeholder update, or business review — even if they don't say "executive" explicitly. Trigger phrases include: "write a summary of last week's performance," "create a briefing for our leadership team," "produce a monthly business review," "what should I tell executives about our metrics," "generate a performance narrative," "QBR summary," "weekly business review," "board update," "stakeholder briefing," "how did we do last week," or "give me a performance snapshot." When in doubt, use this skill — it is always better to produce a polished briefing than a raw data dump.
The English summary is being prepared. Showing the original description.
OCIOStateOfNebraska/stateofnebraska-aem☆ 3Updated Oct 17, 2026
Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."
The English summary is being prepared. Showing the original description.
OCIOStateOfNebraska/stateofnebraska-aem☆ 3Updated Oct 17, 2026
Performance optimization guidelines for OneKey React/React Native applications. Use when optimizing app performance, fixing UI freezes/lag, reducing re-renders, handling concurrent operations, or analyzing performance bottlenecks. Triggers on performance, optimization, optimize, slow, lag, freeze, hang, jank, stutter, memory, leak, concurrent, batching, batch, memoization, memo, bridge, windowSize, contentVisibility, FlashList, re-render, fps, tti, bundle.
The English summary is being prepared. Showing the original description.
MikeCheng1208/BattleTree☆ 2Updated Jul 22, 2026