workflow-performance
Systematic performance analysis and optimization. Use when things are slow, need optimization, or preparing for scale.
What this skill does
# Performance Optimization Workflow Systematic approach to finding and fixing performance issues. ## Phase 1: Baseline **Agents:** `performance-engineer` Measure current state: - Response times (p50, p95, p99) - Memory usage - CPU utilization - Database query times - Bundle sizes (frontend) - Render performance **Output:** Baseline metrics report ## Phase 2: Bottleneck Identification **Agents:** `performance-engineer` Analysis: - Profiling (CPU, memory) - Query analysis (slow query log, EXPLAIN) - Bundle analysis (webpack-bundle-analyzer) - Network analysis (waterfall, latency) **Output:** Bottleneck list with priority ranking ## Phase 3: Optimization Planning **Agents:** `requirements-analyst` - Prioritize by impact vs effort - Define expected improvements - Determine implementation order - Set target metrics ## Phase 4: Database Optimization **Agents:** `database-optimizer` Tasks: - Query optimization (rewrite slow queries) - Index creation/optimization - Caching strategy (Redis, memcached) - Connection pooling ## Phase 5: Code Optimization **Agents:** `performance-engineer` Focus: - Algorithm efficiency (O(n) → O(log n)) - Memory management (leaks, allocation) - Async operations (parallelize I/O) - Application-level caching ## Phase 6: Frontend Optimization **Agents:** `performance-engineer` Tasks: - Bundle size reduction - Code splitting - Lazy loading - Asset optimization (images, fonts) - Render optimization (virtualization, memoization) ## Phase 7: Infrastructure Optimization **Agents:** `devops-architect` Areas: - Scaling strategy (horizontal/vertical) - Caching layers (CDN, reverse proxy) - Load balancing - Resource allocation ## Phase 8: Validation **Agents:** `performance-engineer` **Blocking:** Must meet targets Targets: - Response time: <200ms (p95) - Memory usage: <200MB - Bundle size: <500KB ## Phase 9: Load Testing **Agents:** `performance-engineer` Scenarios: - Normal load (expected traffic) - Peak load (2-3x normal) - Stress test (find breaking point) Duration: 30min per scenario ## Phase 10: Monitoring Setup **Agents:** `devops-architect` - Performance dashboards - Alerting rules (degradation detection) - Automated profiling (continuous) ## Success Criteria - [ ] Performance targets met - [ ] Load tests pass - [ ] Monitoring in place - [ ] Documentation complete ## Targets | Metric | Target | |--------|--------| | Response time improvement | 50% | | Memory reduction | 30% | | Cost reduction | 20% | ## Quick Reference | Resource | Reference File | |---|---| | **Optimization Techniques** | `skills/workflow-performance/references/optimization-techniques.md` | ## Anti-patterns - Optimizing without measuring first - Micro-optimizations before algorithmic fixes - Optimizing code that isn't the bottleneck - No load testing before production
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.