「perf」の検索結果

Profiles Python code for performance bottlenecks and memory issues. Use when Python code is slow or when profiling for optimization before a release.

日本語の概要は準備中です。原文の説明を表示しています。

Profile and optimize application performance including load times, memory usage, and rendering. Use when debugging slow performance, memory leaks, or optimizing app speed.

日本語の概要は準備中です。原文の説明を表示しています。

Performs a deep code review of files, modules, a diff, or a branch - finding security vulnerabilities (mapped to OWASP Top 10:2025), correctness bugs, performance problems, and maintainability issues - and returns severity-ranked findings with evidence and concrete fixes. Use when the user asks to review, audit, or sanity-check code, asks "is this safe", "what's wrong with this", "find bugs", or wants a security or performance pass before shipping. For posting line comments on a GitHub pull request, use git-pr-reviewer.

日本語の概要は準備中です。原文の説明を表示しています。

Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.

日本語の概要は準備中です。原文の説明を表示しています。

Plan, diagnose, and verify performance budgets, latency targets, load tests, capacity estimates, bottleneck analysis, caching strategy, query efficiency, queue throughput, and regression gates. Use when a feature may be slow, a system must scale, a performance regression is suspected, or release readiness depends on throughput, cost, memory, CPU, or response time.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.

日本語の概要は準備中です。原文の説明を表示しています。

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

日本語の概要は準備中です。原文の説明を表示しています。

Akana by Perforce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Akana by Perforce data.

日本語の概要は準備中です。原文の説明を表示しています。

Design game performance testing strategy. Use when the user says "performance test" or "benchmark"

日本語の概要は準備中です。原文の説明を表示しています。

Web performance audits with Core Web Vitals, bottleneck identification, optimization recommendations. Use for page load times, performance reviews, UX optimization, or encountering LCP, FID, CLS issues, resource blocking, render delays.

日本語の概要は準備中です。原文の説明を表示しています。

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

日本語の概要は準備中です。原文の説明を表示しています。

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

日本語の概要は準備中です。原文の説明を表示しています。

Recent quarter performance analysis, quarterly earnings review, last quarter results, quarterly financial performance, analyze recent quarter, Q4 earnings, quarterly revenue breakdown, EPS this quarter, margin analysis recent quarter, sequential growth, quarterly performance review

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert High-Performance Computing Specialist. Use when a task calls for High-Performance Computing Specialist judgment. Reasons from NUMA topology and hybrid MPI+OpenMP+CUDA decomposition through Slurm fairshare/backfill job design, strong/weak scaling (Amdahl/Gustafson), Darshan/mpiP/Nsight profiling, and parallel HDF5/MPI-IO on Lustre while treating I/O storms, collectives bottlenecks, and rank-binding mistakes as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Plan, implement, or review google cloud waf performance optimization work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests google cloud waf performance optimization work.

日本語の概要は準備中です。原文の説明を表示しています。

Provider-independent production workflow for AI agents assembling generated or source media into HyperFrames HTML/CSS/JS videos. Use for HyperFrames composition planning, scene architecture, media custody, animation/timing, captions/audio, deterministic preview/render QA, accessibility/flashing checks, provenance ledgers, and delivery handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to design, rewrite, refine, or vary emotional acting prompts for live-action AI video characters. Translate abstract emotions, dialogue, subtext, and scene context into concise, observable, temporally ordered micro-performance directions. Preserve the user's existing character, scene, camera, and dialogue requirements unless they explicitly ask to change them. Do not use for general story writing, shot design, action choreography, or visual asset design when emotional performance is not the main task.

日本語の概要は準備中です。原文の説明を表示しています。

Optimize MATLAB code for better performance through vectorization, memory management, and profiling. Use when user requests optimization, mentions slow code, performance issues, speed improvements, or asks to make code faster or more efficient.

日本語の概要は準備中です。原文の説明を表示しています。

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.

日本語の概要は準備中です。原文の説明を表示しています。

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, beat planning, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-motion`.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to perform load testing or performance testing using Artillery with YAML-based scenario definitions. Also use when the user mentions "artillery," "YAML load test," "WebSocket testing," "Socket.io load test," "scenario-based load testing," or "artillery run." For JavaScript-based load testing, see k6.

日本語の概要は準備中です。原文の説明を表示しています。

Expert mobile game developer specializing in iOS and Android game optimization, touch input design, battery and thermal management, device fragmentation handling, and App Store/Play Store submission. Deep knowledge of mobile-specific constraints and best practices for shipping performant, player-friendly mobile games. Use when "mobile game, ios game, android game, touch input, mobile optimization, mobile performance, app store, play store, mobile battery, thermal throttling, mobile porting, tablet game, phone game, mobile monetization, mobile build, mobile, ios, android, touch, optimization, performance, battery, thermal, app-store, play-store, game-development, unity-mobile, godot-mobile, device-fragmentation" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

The specialized craft of writing copy that sells—headlines that stop thumbs, body copy that persuades, CTAs that convert. This is copywriting specifically tuned for advertising: paid media, performance marketing, direct response. Ad copy is different from content writing. Every word costs money (CPM/CPC). Every character competes for attention. There's no time for warm-up—you have one chance to hook, persuade, and convert. The best ad copy feels effortless but is engineered word by word. In the age of AI-generated creative at scale, ad copywriting becomes both more important (you need more variations) and more challenging (everyone has access to the same tools). The differentiation is in the strategy, the insight, and the craft that AI assists but doesn't replace. Use when "ad copy, headline, ad text, CTA, call to action, Facebook ad, Google ad, ad variations, direct response, performance copy, primary text, ad headline, ad-copy, headlines, direct-response, performance, conversion, cta, advertising" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Angular Best Practices workflow skill. Use this skill when the user needs Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。