BF swiftui-performance-audit
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.
As a process F 33/100 · Will not run — References files that are not bundled: references/optimizing-swiftui-performance-instruments.md, references/understanding-improving-swiftui-performance.md, references/understanding-hangs-in-your-app.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/optimizing-swiftui-performance-instruments.md - warning
missing-refreference to a missing file: references/understanding-improving-swiftui-performance.md - warning
missing-refreference to a missing file: references/understanding-hangs-in-your-app.md - warning
missing-refreference to a missing file: references/demystify-swiftui-performance-wwdc23.md - note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 33/100
- 0Tools and files. 4 referenced file(s) missing: references/optimizing-swiftui-performance-instruments.md, references/understanding-improving-swiftui-performance.md, references/understanding-hangs-in-your-app.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (swiftui-performance-audit) differs from the folder (timeflow-swiftui-performance-audit)
- 70Failures and branches. 4 branches
- 85Steps. 42 steps, 2 vague phrases
- 100Execution cost. Instruction body is 1404 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 322: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.