Performance Hint
Notices performance issues when viewing code with nested loops, database queries in loops, inefficient algorithms, or missing caching. Use when user shows code that might have O(n²) complexity, N+1 queries, or obvious performance bottlenecks.
What this skill does
# Performance Hint Lightweight performance awareness for conversations. Provides quick hints about potential bottlenecks without deep analysis. ## When to activate Activate when you notice in code being discussed: - Nested loops (O(n²) or worse) - Database queries inside loops (N+1 problem) - Sorting or filtering inside loops - Sequential API calls that could be parallel - Large arrays without pagination - Missing memoization for expensive operations - Event listeners without cleanup ## What to do **Briefly mention** the issue in 1-2 sentences, then suggest running a command: **Example responses:** ``` "This nested loop creates O(n²) complexity on lines 45-52. Run `/review src/utils.js` to check for performance optimizations." ``` ``` "I see a query inside a loop (N+1 problem) on line 28. This will make 100+ database calls. Run `/deep-review` to analyze performance and get optimization suggestions." ``` ``` "These API calls are sequential (lines 15-18) but could run in parallel with Promise.all. Run `/quick-check src/api/` for performance check." ``` ## Important rules - ❌ Do NOT perform full complexity analysis - ❌ Do NOT benchmark or profile code - ✅ Only mention obvious issues in current conversation - ✅ Keep hints brief (1-2 sentences) - ✅ Always suggest a command for detailed analysis - ✅ Focus on impactful optimizations, not micro-optimizations ## Red flags to watch for **Algorithm complexity:** - Nested loops, especially with array methods like `.find()` or `.filter()` - Sorting inside loops **Database:** - Queries in `for`/`forEach` loops - Missing `include` or eager loading - No pagination on `.findAll()` **Memory:** - Event listeners without removal - Timers/intervals not cleared - Large objects in closures **Network:** - Multiple `await` calls that could use `Promise.all` - No request debouncing - Fetching entire datasets ## Commands to suggest - `/quick-check` - for fast performance scan - `/review [file]` - for specific file analysis - `/deep-review` - for comprehensive performance review with optimization strategies This is a hint tool, not a replacement for proper performance profiling.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.