'performance' 검색 결과

Analyze performance in Claude Flow swarms, groups of agents working together. Identify delays in communication, processing, memory, and networking, then generate reports and prioritized recommendations. Compare previous runs or apply available automatic optimizations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating slow tasks across multiple agents
• Comparing performance before and after changes
• Creating weekly performance reports

Measure and optimize claude-flow v3 startup, search, attention processing, and memory use. Compare benchmarks against performance targets, track changes over time, and identify regressions to guide further optimization.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare performance before and after v3 optimization
• Evaluate vector search speed and memory use
• Track performance regressions over time

Set and review limits for bundled file size and page performance so CI, automated checks on code changes, can catch regressions. Check enforcement on pull requests and review production monitoring for slowdowns after release.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing performance limits in CI configuration
• Checking pull requests that add dependencies or assets
• Setting limits for file size and page performance

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

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

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

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

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

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

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

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

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

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

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

Measure and improve Three.js or WebGL game performance through repeatable gameplay checks. Identify CPU or GPU bottlenecks, reduce unnecessary rendering and processing, and verify that controls, collisions, visuals, and memory remain stable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating frame-time spikes
• Reducing rendering and particle workloads
• Improving performance on mobile devices

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.