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.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swiftui-performance-audit100
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (SwiftUI runtime performance), lists specific diagnosable problems users would naturally describe, and explicitly states when to use it. The description uses proper third-person voice and provides enough detail to distinguish it from general Swift development or other performance-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'audit and improve runtime performance', 'diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, layout thrash', and 'provide guidance for Instruments profiling'. | 3 / 3 |
Completeness | Clearly answers both what ('Audit and improve SwiftUI runtime performance from code review and architecture') and when ('Use for requests to diagnose slow rendering, janky scrolling...') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'slow rendering', 'janky scrolling', 'high CPU/memory usage', 'excessive view updates', 'layout thrash', 'SwiftUI', 'performance', 'Instruments profiling' - these match how developers describe performance issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining SwiftUI + runtime performance + specific symptoms. Unlikely to conflict with general Swift skills or other performance tools due to the specific focus on SwiftUI rendering issues and Instruments guidance. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently guides SwiftUI performance auditing with a clear decision tree workflow, concrete code examples for common issues, and explicit verification steps. The content respects Claude's intelligence by avoiding basic explanations while providing actionable, copy-paste ready fixes. The structure enables progressive disclosure with well-organized sections and clear references to external documentation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding explanations of basic SwiftUI concepts Claude already knows. Each section provides actionable guidance without padding, and the code examples are minimal but complete. | 3 / 3 |
Actionability | Provides concrete, executable code examples for each common smell with clear before/after patterns. The workflow steps are specific and the fixes are copy-paste ready with real Swift code. | 3 / 3 |
Workflow Clarity | Clear decision tree at the start with explicit sequencing (Code-First Review → Guide to Profile → Analyze → Remediate → Verify). Includes validation step (step 5) asking user to re-run capture and compare with baseline metrics. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate depth. References to external documentation are clearly signaled at the end with one-level-deep links to reference files. Content is appropriately split between overview, workflow, code smells, and references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.