What problem does it solve? When the Moolah app freezes, beachballs, or feels slow, you need to know exactly which code is blocking the main thread. This Skill provides a systematic workflow for capturing stack samples, reading built-in performance logs, and recording Instruments traces to pinpoint the bottleneck. ## Core Features & Use Cases - Stack Sampling: Capture 3-second stack samples of the running app with the sample tool and read the main-thread call graph to find the deepest, hottest frames. - Performance Log Analysis: Monitor built-in ⚠️ PERF: and 📊 SYNC SESSION log lines that report sync batch timing, balance invalidation cost, and per-store reload durations. - Instruments Profiling: Record Time Profiler and os_signpost traces via xctrace for visual timeline analysis of custom signpost intervals like applyRemoteChanges and recomputeAllBalances. - Use Case: A user reports the app hangs when opening a profile with many transactions. Launch the app with log capture, reproduce the freeze, capture a stack sample mid-hang, and grep the performance logs to identify whether sync, balance recomputation, or store reloads caused the stall. ## Quick Start Ask the AI to diagnose why the Moolah app is frozen by capturing a stack sample of the running process and checking the performance logs.