iOS Performance Router

You MUST use this skill for ANY performance issue including memory leaks, slow execution, battery drain, or profiling.

When to Use

Use this router when:

• App feels slow or laggy
• Memory usage grows over time
• Battery drains quickly
• Diagnosing performance with Instruments
• Memory leaks or retain cycles
• App crashes with memory warnings

Routing Logic

Memory Issues

Memory leaks (Swift) → /skill memory-debugging

• Systematic leak diagnosis
• 5 common leak patterns
• Instruments workflows
• deinit not called

Memory leaks (Objective-C blocks) → /skill objc-block-retain-cycles

• Block retain cycles
• Weak-strong pattern
• Network callback leaks

Performance Profiling

Performance profiling → /skill performance-profiling

• Time Profiler (CPU)
• Allocations (memory growth)
• Core Data profiling (N+1 queries)
• Decision trees for tool selection

Decision Tree

User reports performance issue
  ├─ Memory?
  │  ├─ Swift code? → memory-debugging
  │  └─ Objective-C blocks? → objc-block-retain-cycles
  │
  ├─ Want to profile?
  │  └─ YES → performance-profiling
  │
  └─ General slow/lag? → performance-profiling

Critical Patterns

Memory Debugging (memory-debugging):

• 6 leak patterns: timers, observers, closures, delegates, view callbacks, PhotoKit
• Instruments workflows
• Leak vs caching distinction

Performance Profiling (performance-profiling):

• Time Profiler for CPU bottlenecks
• Allocations for memory growth
• Core Data SQL logging for N+1 queries
• Self Time vs Total Time

Example Invocations

User: "My app's memory usage keeps growing" → Invoke: /skill memory-debugging

User: "I have a memory leak but deinit isn't being called" → Invoke: /skill memory-debugging

User: "My app feels slow, where do I start?" → Invoke: /skill performance-profiling

User: "My Objective-C block callback is leaking" → Invoke: /skill objc-block-retain-cycles