instruments-profiling
by steipete
iOS & macOS DevelopmentBrief
Use when profiling native macOS or iOS apps.
Description
What This Skill Does
Covers performance profiling for native macOS and iOS apps using xctrace CLI and the Instruments UI. Addresses correct binary selection, CLI arguments, stack exports, and common gotchas like LaunchServices resolving the wrong app bundle.
Instruments and xctrace have non-obvious argument ordering and bundle-resolution gotchas that cause silent profiling errors; this skill documents the fixes directly.
When to Use It
- Profiling slow app startup on macOS
- Capturing CPU samples from a running iOS app by PID
- Exporting time-profile stacks to XML for offline analysis
- Identifying hot frames in a native app's call tree
- Attaching a profiler to a live process without restarting it
Example Workflow
User asks: how do I profile my macOS app's startup with xctrace?
- 1
Run
xcrun xctrace list templatesto confirm Time Profiler is available - 2
Locate the direct binary path to avoid LaunchServices resolving an installed bundle instead of the local build
- 3
Run
xcrun xctrace record --template 'Time Profiler' --time-limit 60s --output /tmp/App.trace --launch -- /path/App.app/Contents/MacOS/App - 4
Verify the traced process path matches the intended build using
ps -p <pid> -o comm= -o command= - 5
Open the trace with
open -a Instruments /tmp/App.traceand review the call tree with Invert Call Tree and Hide System Libraries
A .trace file opened in Instruments showing CPU samples and hot frames covering the app's startup path
Requirements
- Xcode installed (provides xctrace CLI and Instruments)
- Developer Tools permission granted in System Settings → Privacy & Security → Developer Tools
Installation
clawhub install steipete/instruments-profilingRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.