Swiftui Performance
Use this skill when reviewing or fixing SwiftUI performance issues, including unnecessary invalidation, unstable identity, broad state dependencies, expensive body work, heavy rows, scrolling hitches, layout/drawing cost, or async lifecycle work. Do not use it for general SwiftUI syntax, styling, UIKit-only performance, or generic profiling unless SwiftUI update behavior is central.
Install
npx skills add Livsy90/iOS-Performance-Agent-Skills --skill swiftui-performancegit clone --depth 1 https://github.com/Livsy90/iOS-Performance-Agent-Skills.git /tmp/iOS-Performance-Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/iOS-Performance-Agent-Skills/swiftui-performance ~/.claude/skills/swiftui-performancePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# SwiftUI Performance ## Purpose Use this skill to review and refactor SwiftUI code with a performance-first mental model focused on change locality. SwiftUI performance work should explain which change invalidates which part of the UI, why that work matters, and how to keep updates local. ## Scope Use this skill for: * SwiftUI screen, list, row, layout, drawing, animation, and lifecycle reviews * targeted refactors that reduce unnecessary updates or rendering work * profiling plans only when they validate a SwiftUI performance hypothesis Do not use this skill for: * UIKit-only performance problems * app launch performance unless the issue is inside SwiftUI root view or scene construction * networking, backend latency, database performance, or caching unless they affect SwiftUI updates * generic Instruments walkthroughs without a SwiftUI code path * broad architecture rewrites without a concrete SwiftUI performance risk ## Core Model Answer three questions first: 1. What changed? 2. Which views depend on that change? 3. How much UI work happens because of it? Then inspect: * Identity: does SwiftUI preserve the same logical view across updates? * Lifetime: is state owned by the smallest stable component that needs it? * Dependencies: does each view read only the data it needs to render? * Rendering: is `body` cheap, predictable, and free from heavy transformation work?
Details
- Skill name
swiftui-performance- Repository
- Livsy90/iOS-Performance-Agent-Skills
- Path
swiftui-performance/SKILL.md- License
- MIT
- Repo updated
- 12 July 2026
FAQ
What does the Swiftui Performance skill do?
Use this skill when reviewing or fixing SwiftUI performance issues, including unnecessary invalidation, unstable identity, broad state dependencies, expensive body work, heavy rows, scrolling hitches, layout/drawing cost, or async lifecycle work. Do not use it for general SwiftUI syntax, styling, UIKit-only performance, or generic profiling unless SwiftUI update behavior is central.
How do I install the Swiftui Performance skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Livsy90/iOS-Performance-Agent-Skills --skill swiftui-performance. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Swiftui Performance popular?
It lives in Livsy90/iOS-Performance-Agent-Skills, which has 121 GitHub stars and 11 forks.
Related skills
IOS Launch Performance
121Livsy90/iOS-Performance-Agent-Skills
Use this skill when diagnosing iOS app launch performance, startup regressions, first-frame readiness, or early responsiveness. Covers pre-main/dyld work, AppDelegate/SceneDelegate, SwiftUI App startup, launch orchestration, SDK initialization, and launch measurement. Do not use for general performance unless the code runs on the launch path.
IOS Perceived Performance
121Livsy90/iOS-Performance-Agent-Skills
Use this skill for product-level iOS responsiveness and loading/feedback flows, including perceived latency, time to first feedback, progressive rendering, loading states, skeletons, placeholders, optimistic updates, rollback behavior, high-stakes actions, UI continuity, and responsiveness validation. Do not use it for low-level CPU, memory, rendering, Swift Concurrency, or launch-performance diagnostics unless the task is about user-perceived speed.
IOS Performance Profiling
121Livsy90/iOS-Performance-Agent-Skills
Use this skill when choosing, running, or interpreting iOS performance profiling workflows, including Instruments traces, signposts, XCTest metrics, MetricKit, Xcode Organizer, hangs, hitches, CPU, allocations, memory graphs, disk I/O, networking, power, or production performance signals. Do not use it as the deep domain skill for launch, SwiftUI, concurrency, perceived performance, or runtime issues unless the task is specifically about measurement, tool selection, trace interpretation, or verification.
Adversarial IOS Design
228pproenca/dot-skills
Use this skill to gate iOS SwiftUI design and UX with a pass/fail adversarial review — a single blind reviewer subagent judges screens, diffs, or features against 56 decidable HIG-derived rules, working backwards from mandatory rendered evidence, simulator screenshots (light, dark, accessibility text size) and interaction recordings tiled into filmstrips. Covers navigation/IA (tab bars, five tabs max, system Back), modality and flow grammar (sheets, alerts, unsaved-content protection), layout (44pt targets, safe areas, Dynamic Type), color and contrast, typography floors, Liquid Glass, feedbac
Swift Runtime Performance
121Livsy90/iOS-Performance-Agent-Skills
Use this skill when reviewing Swift code for runtime-level performance costs, including heap allocation, ARC traffic, stack vs heap storage, closure capture contexts, method dispatch, protocol witness dispatch, existentials vs generics, opaque types, copy-on-write, SIL optimizer output, unsafe memory boundaries, or module-boundary optimizer visibility. Do not use it for Swift Concurrency scheduling, SwiftUI rendering, app launch, or profiling workflows unless the question is specifically about Swift runtime costs.
Adversarial Swift
228pproenca/dot-skills
Use this skill to gate Swift language code with a pass/fail adversarial review — a single blind reviewer subagent judges a diff or file set against 36 decidable rules covering concurrency (unresumed continuations, cancellation checks, async let, TaskGroup, @concurrent), property invariants (stored-derived state, private(set), observers skipped in init, discard self), error handling (underlying errors preserved, rethrows, Result.get(), #file/#line capture), enum evolution (@unknown default, CaseIterable, synthesized Comparable, caseless namespaces), API surface (memberwise inits, OptionSet, opa
Browse the most popular Claude skills, all mobile development skills, or write your own with the skills generator.