domains / families / software-engineering / swiftui-performance-audit

swiftui-performance-audit

combined

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient. Audit SwiftUI performance issues from code review and profiling evidence.

When to use

• When the user reports slow rendering, janky scrolling, layout thrash, or high CPU in SwiftUI.
• When you need a code-first audit plus Instruments guidance if profiling evidence is required.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The three copies overlap heavily on the core workflow (classify symptom, code-first review, guide profiling, analyze, remediate, verify), but each has material steps the others lack. Dimillian/Skills and sickn33/agentic-awesome-skills are near-identical and reference external files (references/code-smells.md, references/profiling-intake.md, references/report-template.md) that are not present in the skill text. LeoYeAI/openclaw-master-skills inlines a detailed code-smells catalog with concrete Swift examples and fixes, and adds a workflow decision tree, but omits the external reference files and the explicit intake checklist. Crowning one copy would hide either the external reference structure or the inlined remediation examples, so a combined instruction is needed.