react-native-best-practices
React Native performance optimization - FPS, bundle size, TTI, memory management, animations.
Découvrez les skills Contenu et médias, comparez leurs dépôts et consultez leurs instructions.
React Native performance optimization - FPS, bundle size, TTI, memory management, animations.
Four-phase debugging process - root cause investigation, pattern analysis, hypothesis testing, implementation.
CodeQL static analysis for interprocedural data flow and taint tracking across codebases.
This skill should be used when the user asks to "write tests", "test strategy", "coverage", "unit test", "integration test", or needs testing guidance. Provides testing methodology and patterns.
This skill should be used when the user asks to "investigate code", "analyze implementation", "find patterns", "understand codebase", "debug issue", "find bug", "troubleshoot", or needs evidence-based code anal...
Fuzzing coverage analysis - identify uncovered code, magic values, and track campaign effectiveness.
Vercel React/Next.js performance optimization guide with 45 rules across 8 categories, prioritized by impact.
Static analysis with Semgrep - pattern-based security scanning and custom rule creation.
Three.js performance optimization - 100+ rules for memory, rendering, geometry, materials, WebGPU, and WebXR.
This skill should be used when working with C projects, "C11", "C17", "C23", "Makefile", "gcc", "clang", "valgrind", "getopt", or C language patterns. Provides comprehensive Modern C (C11-C23) patterns, memory...
Master YARAL query language for low-maintenance threat hunting and detection in Google SecOps. Build behavioral detections without magic strings or IOC lists. Use when writing YARAL queries, creating custom det...
Comprehensive code review toolkit for evaluating quality across multiple languages. Use for PR analysis, quality checking, and generating review reports. Based on alirezarezvani/claude-skills.
Check resource usage (CPU, memory) on cluster nodes. Used to identify nodes under pressure. Keywords: node resources, cpu, memory, capacity, pressure, metrics, cluster health.
Four-phase debugging methodology emphasizing root cause analysis before fixes. Use for bug investigation, preventing random fixes, and systematic problem-solving. Based on obra/superpowers.
Deep investigation of a failing pod. Gathers logs, events, and resource status to identify root cause. Keywords: investigate, debug, pod failure, troubleshoot, root cause, logs, events.
Official coding standards and best practices derived from Xcode's internal AI chat templates.
Use when errors are unclear, flaky, or regressions occur; apply a disciplined debugging loop in VS Code Copilot Agent mode.
Manage tmux sessions. Use when needing to create, list, attach to, or manage terminal multiplexer sessions. Triggers on "tmux", "create session", "list sessions", "terminal session".
Latitude.sh bare metal infrastructure management via API, MCP server, or CLI. Use when provisioning servers, managing VLANs, checking plans/regions, or automating bare metal deployments.
This skill should be used when the user asks to "write nix", "nix expression", "flake.nix", "home-manager config", "programs.*", "services.*", or works with Nix language, flakes, or Home Manager. Provides compr...
Manage tmux sessions, windows, and panes for terminal multiplexing. Use when running long processes, managing multiple terminals, or executing commands in background sessions.
Analyze cluster capacity and provide scaling recommendations. Forecasts resource needs, identifies imbalances, and suggests actions. Use for capacity planning and proactive scaling. Keywords: capacity, planning...
Manage tmux sessions, windows, and panes for terminal multiplexing. Use when running long processes, managing multiple terminals, or executing commands in background sessions.
Guide for managing terminal sessions with tmux via bash. Use when running long-lived processes, managing multiple concurrent terminal sessions, monitoring background tasks, or needing persistent shells that sur...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.