Claude skill for Apple Instruments performance traces (iOS/Mac)
Details
- External ID
- 47662765
- Source
- HN
- Company
- —
- Product
- Claude skill for Apple Instruments performance traces (iOS/Mac)
- Website domain
- github.com
- Launched
- April 6, 2026
- Cohort
- —
- Upvotes
- 5
- Upvotes percentile
- 0.11182519280205655
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I was running into scroll performance issues with a mac app I was building a few months back and I got frustrated with the manual instrument → trace → diagnose → fix loop, so I built a way for claude to do it automatically.Instruments Analyzer exports .trace files captured programmatically or via Instruments (file → save) into DuckDB with Parquet backing, giving your agents full SQL access to CPU profiling, animation hitches, SwiftUI view updates, Core Animation frame lifetimes, RunLoop activity, signposts, and 30+ other tables.Key features:1. Natural Language Queries. Since it’s just a skill, you can ask “why did scroll lag in this trace” rather than dig through WWDC videos to understand which instruments to use and how to use them.2. Derived views for analysis: Frame-level analysis, cascade analysis, and per-frame attribution are available via prepared views (prepare_analysis.py), making it easy to query performance metrics without manual preprocessing.3. Scroll & animation jank workflow: Optional workflow for diagnosing scroll lag or animation stutter, only loads when relevant.Install as a Claude Code skill or with whatever agent you’re building with.https://github.com/jlreyes/instruments-analyzer
Enrichment
- Theme
- utilities for Claude and Claude Code
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- AI feature
- Project type
- Hobby / open-source project
- Normalized one-liner
- ai analysis for performance traces
- Manually corrected
- False
Could you build this?
Yes This is a developer tooling integration that uses Xcode command-line tools (`xctrace`) to parse `.trace` files into XML or JSON and feeds the structured data into Claude via a custom tool/MCP skill.
Discussion
3 comments analyzed.
Competitors mentioned: Instruments (Apple's native tool), existing performance tooling/dashboards
Concerns raised: AI gets distracted by aggregate signals instead of root causing specific issues, traces can be noisy and context-dependent, derived views may encode too many assumptions about what 'jank' looks like, whether derived views generalize across different traces
Feature requests: support for new SwiftUI instrument from WWDC 2025 with attribute graph, handle large traces (5+ minute scroll-heavy traces) efficiently
Competitors
Other products that read as similar to this one — 78 launches clear the similarity bar, closest 8 shown.
Attention rank: #70 of 79 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 142 days after the earliest competitor.
- Claude Usage Tracker · ph · 2026-03-23 · 235 upvotes · similarity 0.47
- I built a tool to un-dumb Claude Code's CLI output (Local Log Viewer) · hn · 2026-02-13 · 69 upvotes · similarity 0.43
- macOS menu bar app to track Claude usage in real time · hn · 2026-01-08 · 161 upvotes · similarity 0.41
- DataKit, your all in browser data studio is open source now · hn · 2025-12-08 · 6 upvotes · similarity 0.40
- Claude Code usage tracking by LangWatch · ph · 2026-07-30 · 351 upvotes · similarity 0.38
- Claude Tune · ph · 2026-09-07 · 1 upvotes · similarity 0.38
- Claude Watch · ph · 2026-09-25 · 2 upvotes · similarity 0.37
- CC-BEEPER · ph · 2026-04-15 · 222 upvotes · similarity 0.37
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.