Run any Skill in Manus with one click

apple-performance-memory

Stars0

Forks0

UpdatedJuly 7, 2026 at 15:48

Diagnose Apple app launch/runtime performance, SwiftUI invalidation, hangs, Instruments traces, Top Functions, ETTrace profiles, dSYMs, memgraphs, leaks, retain cycles, and Foundation Models traces. Use when an Apple app is slow, janky, memory-heavy, leaking, hanging, or needs before/after profiling evidence.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Allmight97

Allmight97/agents

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

13 files

SKILL.md

readonly

name	apple-performance-memory
description	Diagnose Apple app launch/runtime performance, SwiftUI invalidation, hangs, Instruments traces, Top Functions, ETTrace profiles, dSYMs, memgraphs, leaks, retain cycles, and Foundation Models traces. Use when an Apple app is slow, janky, memory-heavy, leaking, hanging, or needs before/after profiling evidence.

Apple Performance / Memory

Purpose

Use this skill when the question is runtime cost, not merely build correctness. Start with code and scenario clarity, then pick the smallest trace that answers the question.

Workflow

Define the scenario.
- launch, first screen, scroll, navigation, search, import/export, HealthKit sync, model generation, background work, watch handoff, or memory growth
- same scheme, destination, configuration, data, and steps for before/after comparisons
Inspect code first.
- SwiftUI body churn, expensive computed properties, broad Observation invalidation, unstable IDs, nested lists, image decoding, synchronous work on the main actor
- retain cycles, long-lived tasks, unbounded caches, NotificationCenter/KVO/timer ownership, task cancellation, and actor isolation problems
Pick the proof.
- Instruments or xctrace for CPU, hangs, allocation, leaks, and launch
- Top Functions for hot-stack narrowing
- ETTrace helpers for iOS Simulator latency and stack comparison
- dSYM collection when traces need symbolication
- memgraph helpers for retained objects and leaks
- Foundation Models Instrument for prompt, response, token, and tool-call behavior
- XcodeBuildMCP coverage/log workflows when the issue is tied to tests or runtime logs
Run the narrow command.
- Keep raw trace files out of git unless the repo explicitly stores performance artifacts.
- Store temporary evidence under /private/tmp or another ignored location.
- Preserve the exact command, destination, device, OS, build configuration, and app version.
Fix and compare.
- Make one causal change at a time where possible.
- Re-run the same scenario.
- Report before/after evidence and residual risk.

Bundled Helpers

scripts/analyze_flamegraph_json.py
scripts/collect_ios_dsyms.sh
scripts/capture_sim_memgraph.sh
scripts/summarize_memgraph_leaks.py

References

references/swiftui/

More from this repository

same repository

use-proton-pass

Allmight97/agents

Read credentials and secrets from Proton Pass through pass-cli with scoped agent sessions and non-disclosing handoffs. Use when retrieving passwords, TOTP codes, pass:// references, attachments, or other vault fields; logging into a website or application; running commands with Proton Pass secrets; inspecting vault, item, share, agent, or access-token metadata; using Proton Pass SSH keys; or diagnosing pass-cli installation, authentication, session, and permission failures.

2026-07-180

code-review

Allmight97/agents

Read-only review of a PR, branch, diff, or worktree changes for correctness, requested behavior, regressions, scope creep, proof gaps, and merge readiness. Use when asked to review changed code or decide whether work is safe to merge. Route over-engineering-only reviews to whittle-review and repository-wide structural scans to improve-codebase-architecture.

2026-07-120

whittle-review

Allmight97/agents

Review for over-engineering without applying fixes: find what to delete, replace with stdlib/native, or shrink. Use when asked to review a diff or audit a repo for unnecessary complexity, bloat, deletion candidates, or YAGNI violations. Correctness, requested behavior, merge readiness, security, and performance are out of scope; route ordinary code review to code-review.

2026-07-120

write-sharp-docs

Allmight97/agents

Write, rewrite, critique, and manage high-taste technical program and engineering documents. Use when asked for better docs, specs, RFCs, decision memos, launch or readiness docs, completion records, Google Docs-ready drafts, less LLM-y writing, senior TPM or staff-engineer polish, document pruning, audience fit, decision clarity, or durable knowledge management.

2026-07-120

consult-pro

Allmight97/agents

Build, refine, and synthesize ChatGPT Pro consultation prompts. Use when the user asks for a paste-ready Pro prompt, wants Pro to audit, review, or critique a repo or plan, needs a follow-up after a Pro response, wants Pro feedback checked against local evidence, or wants a manual Pro consultation loop without browser monitoring.

2026-07-120

diagnose

Allmight97/agents

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

2026-07-120

name	apple-performance-memory
description	Diagnose Apple app launch/runtime performance, SwiftUI invalidation, hangs, Instruments traces, Top Functions, ETTrace profiles, dSYMs, memgraphs, leaks, retain cycles, and Foundation Models traces. Use when an Apple app is slow, janky, memory-heavy, leaking, hanging, or needs before/after profiling evidence.

Apple Performance / Memory

Purpose

Use this skill when the question is runtime cost, not merely build correctness. Start with code and scenario clarity, then pick the smallest trace that answers the question.

Workflow

Define the scenario.
- launch, first screen, scroll, navigation, search, import/export, HealthKit sync, model generation, background work, watch handoff, or memory growth
- same scheme, destination, configuration, data, and steps for before/after comparisons
Inspect code first.
- SwiftUI body churn, expensive computed properties, broad Observation invalidation, unstable IDs, nested lists, image decoding, synchronous work on the main actor
- retain cycles, long-lived tasks, unbounded caches, NotificationCenter/KVO/timer ownership, task cancellation, and actor isolation problems
Pick the proof.
- Instruments or xctrace for CPU, hangs, allocation, leaks, and launch
- Top Functions for hot-stack narrowing
- ETTrace helpers for iOS Simulator latency and stack comparison
- dSYM collection when traces need symbolication
- memgraph helpers for retained objects and leaks
- Foundation Models Instrument for prompt, response, token, and tool-call behavior
- XcodeBuildMCP coverage/log workflows when the issue is tied to tests or runtime logs
Run the narrow command.
- Keep raw trace files out of git unless the repo explicitly stores performance artifacts.
- Store temporary evidence under /private/tmp or another ignored location.
- Preserve the exact command, destination, device, OS, build configuration, and app version.
Fix and compare.
- Make one causal change at a time where possible.
- Re-run the same scenario.
- Report before/after evidence and residual risk.

Bundled Helpers

scripts/analyze_flamegraph_json.py
scripts/collect_ios_dsyms.sh
scripts/capture_sim_memgraph.sh
scripts/summarize_memgraph_leaks.py

References

references/swiftui/