Conciseness

The body is dense and directive — phases, grep patterns, severity tables, and a health-score rubric with almost no padding or restating of concepts Claude already knows — with only minor over-explanation (e.g. re-justifying why sets are O(1)) that could be trimmed.

Actionability

Each anti-pattern gives an exact grep string, a verification step (Read near 'var body'), a concrete impact, and a specific fix (e.g. 'Move to static let', 'Add .onDisappear { timer?.invalidate() }'), and the output format is a copy-paste-ready template — fully executable guidance covering common cases.

Workflow Clarity

Five phases are explicitly sequenced with checkpoints (produce the Performance Context Map before proceeding, verify each grep with Read, cross-reference compounds in Phase 4) and the destructive/batch guidance 'present this map before proceeding' plus 'require evidence from the Phase 1 map' acts as a validation gate, though there is no explicit validate->fix->retry loop for re-scanning after fixes.

Progressive Disclosure

Content is well-organized into phases with tables and an output template, and cross-references are one level deep and clearly signaled ('See axiom-swiftui (skills/layout-ref.md)', 'axiom-performance (skills/memory-debugging.md)'), but those references point outside the bundle (no references/scripts/assets directories exist) and the bulk anti-pattern catalog lives inline rather than in a split reference file.

Specificity

The description names the SwiftUI performance domain but lists zero concrete actions the skill performs — it only states when to invoke it, never what it does ('detects anti-patterns', 'maps view hierarchy', etc.), matching 'Names the domain but actions are minimal or generic'.

Completeness

Only a 'when' clause is present — 'Use when the user mentions...' — with no 'what' describing what the skill does, matching 'only "when" is present without "what"'; it cannot reach 3 because the 'what' is entirely absent.

Trigger Term Quality

Phrases like 'SwiftUI performance, janky scrolling, slow animations, or view update issues' are natural things a user would say; good coverage with a few synonyms (e.g. 'frame drops', 'lag') missing, placing it just above the midpoint.

Distinctiveness Conflict Risk

The trigger is narrowly scoped to SwiftUI-specific performance symptoms (janky scrolling, view update issues), making it mostly distinct from general performance or UI skills with only minor overlap risk against a sibling SwiftUI debugging skill.