Agent skill · Code Review & Quality

swiftui-performance

Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.

Derek Pearson935★ · +23/wk · 1 repos on radarProfile →
claude-codecodexcursorNOASSERTION
Install
npx skills add dpearson2699/swift-ios-skills --skill swiftui-performance --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/swiftui-performance/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 963 · +28 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SwiftUI Performance Audit SwiftUI view performance from a reproducible symptom to measured remediation. Route animation design to `swiftui-animation`, production telemetry to `metrickit`, ownership/leak analysis to `ios-memgraph-analysis`, navigation behavior to `swiftui-navigation`, state architecture to `swiftui-patterns`, and layout construction to `swiftui-layout-components`. ## Contents - [Workflow Decision Tree](#workflow-decision-tree) - [1. Code-First Review](#1-code-first-review) - [2. Guide the User to Profile](#2-guide-the-user-to-profile) - [3. Analyze and Diagnose](#3-analyze-and-diagnose) - [4. Remediate](#4-remediate) - [Common Code Smells (and Fixes)](#common-code-smells-and-fixes) - [5. Verify](#5-verify) - [Outputs](#outputs) - [Instruments Profiling](#instruments-profiling) - [Identity and Lifetime](#identity-and-lifetime) - [Lazy Loading Patterns](#lazy-loading-patterns) - [State and Observation Optimization](#state-and-observation-optimization) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## Workflow Decision Tree - Code supplied: review it first and label findings as hypotheses. - Symptoms only: co

What's inside
Steps it walks through
  1. Contents
  2. Workflow Decision Tree
  3. 1. Code-First Review
  4. 2. Guide the User to Profile
  5. 3. Analyze and Diagnose
  6. 4. Remediate
  7. Common Code Smells (and Fixes)
  8. 5. Verify
  9. Outputs
  10. Instruments Profiling
  11. Identity and Lifetime
  12. Lazy Loading Patterns
  13. State and Observation Optimization
  14. Common Mistakes
Ships with 6 files
  • evals/evals.json
  • references/demystify-swiftui-performance-wwdc23.md
  • references/optimizing-swiftui-performance-instruments.md
  • references/understanding-hangs-in-your-app.md
  • references/understanding-improving-swiftui-performance.md
  • references/wwdc-session-sources.md
More from swift-ios-skills
All skills →
About this skill
What does the swiftui-performance skill do?

Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.

How do I install it?

Run `npx skills add dpearson2699/swift-ios-skills --skill swiftui-performance --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dpearson2699/swift-ios-skills, a repository with 963 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going