common-performance-engineering
Enforce universal standards for high-performance development. Use when profiling bottlenecks, reducing latency, fixing memory leaks, improving throughput, or optimizing algorithm complexity in any language.
What this skill does
# Performance Engineering Standards ## **Priority: P0 (CRITICAL)** ## Workflow 1. **Baseline**: Profile before changing anything — measure CPU, memory, and latency. 2. **Identify**: Find top bottleneck (N+1 query, hot loop, memory leak). 3. **Fix**: Apply targeted optimization from sections below. 4. **Verify**: Re-profile to confirm improvement and check for regressions. ## Resource Management - **Memory Efficiency**: - Avoid memory leaks: explicit cleanup of listeners, observers, and streams. - Optimize data structures: `Set` for lookups, `List` for iteration. - Lazy Initialization: Initialize expensive objects only when needed. - **CPU Optimization**: - Aim for O(1) or O(n); avoid O(n^2) in critical paths. - Offload heavy computations to background threads or workers. - Memoize pure, expensive functions. See [implementation examples](references/implementation.md) for memoization and batching patterns. ## Network & I/O - **Payload Reduction**: Use efficient serialization (Protobuf, JSON minification) and compression (gzip/br). - **Batching**: Group multiple small requests into single bulk operations. - **Caching**: Implement multi-level caching (Memory -> Storage -> Network) with appropriate TTL and invalidation. - **Non-blocking I/O**: Always use asynchronous operations for file system and network access. ## UI/UX Performance - **Minimize Main Thread Work**: Keep animations and interactions fluid by offloading to workers. - **Virtualization**: Use lazy loading or virtualization for long lists/large datasets. - **Tree Shaking**: Ensure build tools remove unused code and dependencies. ## Monitoring & Testing - **Benchmarking**: Write micro-benchmarks for performance-critical functions. - **SLIs/SLOs**: Define Service Level Indicators (latency, throughput) and Objectives. - **Load Testing**: Test system behavior under peak and stress conditions. ## Anti-Patterns - **No premature optimization**: Profile first, fix proven bottlenecks only. - **No N+1 queries**: Always batch and paginate data-access operations. - **No synchronous I/O on main thread**: Async all file/network access. ## References - [Implementation Patterns](references/implementation.md) — profiling patterns, benchmark setup
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.