ios-ettrace-performance

Profile and symbolicate ETTrace traces for iOS simulator apps.

7|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/omarshahine/Apple-PIM-Agent-Plugin --skill ios-ettrace-performance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-ettrace-performance
Source: https://github.com/omarshahine/Apple-PIM-Agent-Plugin/tree/main/.claude/skills/ios-ettrace-performance
Command: npx skills add https://github.com/omarshahine/Apple-PIM-Agent-Plugin --skill ios-ettrace-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Profile and interpret ETTrace profiles for iOS simulator apps, including symbolicated launch and runtime flamegraphs. Use when asked to profile an iOS app flow, gather simulator performance traces, identify CPU-heavy stacks, compare before/after traces, or produce flamegraph evidence for startup, scrolling, navigation, rendering, or other user-visible latency.

Core Features & Use Cases

  • Capture symbolicated ETTrace launches and runtime traces for iOS simulator apps.
  • Analyze flamegraphs to locate CPU hotspots, rendering bottlenecks, and flow-related delays.
  • Compare before/after traces to validate performance improvements across app flows.

Quick Start

Link ETTrace into your iOS simulator app, run a focused trace, and inspect the produced symbolicated flamegraph.

Frequently Asked Questions about ios-ettrace-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I profile an iOS simulator app to find startup bottlenecks?

Profile iOS simulator apps by capturing ETTrace traces to reveal startup bottlenecks. You link ETTrace into your target app build, run a focused user flow trace, and inspect the symbolicated flamegraph to locate CPU hotspots.

How do I symbolicate ETTrace flamegraphs for an iOS simulator?

Symbolicate ETTrace flamegraphs by linking ETTrace into your iOS simulator app build. This setup processes dSYMs automatically, producing symbolicated launch and runtime traces that identify specific CPU-heavy stacks.

Can I compare before and after performance traces for an iOS app flow?

Compare before and after performance traces by capturing ETTrace profiles of the same iOS app flow at different stages. Analyzing the resulting flamegraphs validates performance improvements across startup, scrolling, or navigation flows.

Do I need a specific version of ETTrace to profile iOS simulator runtime traces?

Profiling iOS simulator runtime traces requires ETTrace v1.1.0. You also need an active iOS simulator and a project setup that links ETTrace into the target app build to generate symbolicated outputs.

What's the best way to locate rendering bottlenecks in an iOS simulator app?

Locate rendering bottlenecks by capturing an ETTrace runtime trace for the specific iOS simulator flow. Analyzing the symbolicated flamegraph reveals CPU hotspots and delays related to rendering, scrolling, or navigation.

Why does my iOS app user flow have visible latency during navigation?

Visible navigation latency stems from CPU-heavy stacks or rendering bottlenecks. Capture an ETTrace trace for the specific user flow, then inspect the symbolicated flamegraph to pinpoint the exact functions causing the delay.