swiftui-patterns

SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices. Use when building or reviewing SwiftUI views, @Observable state, navigation, or render performance.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise, with executable Swift examples across state management, composition, navigation, and performance. Its main gap is progressive disclosure: everything lives in a single inlined SKILL.md with no reference files to offload deeper material.

Suggestions

Move the detailed property-wrapper selection table and performance-tuning deep-dive into a references/ file (e.g. references/state-management.md and references/performance.md), leaving SKILL.md as a concise overview with one-level-deep pointers.

Tighten a few explanatory sentences that restate SwiftUI fundamentals Claude already knows (e.g. the @Observable re-render explanation) to push conciseness to a 5.

Add a short 'Validation' note in the navigation/migration sections — e.g. confirm `@Observable` migration by checking that no `@StateObject`/`@Published` references remain — to give the migration guidance an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — code-led sections with minimal prose — though a few lines like 'it tracks property-level changes so SwiftUI only re-renders views that read the changed property' restate knowledge Claude already has.	4 / 5
Actionability	Every section is backed by complete, copy-paste-ready Swift code covering the common cases (property wrapper table, @Observable view model, navigation router, lazy stacks, Equatable view), with explicit actionable do/don't lists.	5 / 5
Workflow Clarity	Although this is a patterns reference rather than a destructive multi-step procedure, each topic is presented as a clear decision sequence (e.g. choose simplest wrapper, then migrate @EnvironmentObject -> @Environment), and the 'Anti-Patterns to Avoid' section acts as an explicit checkpoint; no risky batch/destructive operations require validation loops.	5 / 5
Progressive Disclosure	Structure is clear with section headers, but all material is inlined in SKILL.md and there are no bundle files (references/scripts/assets absent); the two cross-skill 'See skill:' pointers are inline references rather than a navigable one-level-deep file split, and content that could live in separate files (e.g. a wrapper-selection or performance reference) is not separated out.	3 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it pairs a concrete capability list with an explicit 'Use when' trigger phrase and uses third-person voice throughout. It is specific and unlikely to conflict with unrelated skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas (architecture patterns, @Observable state, view composition, navigation, performance optimization) and ties each to reviewing/building, though it stays slightly abstract on the actions themselves.	4 / 5
Completeness	Explicitly states what it covers and provides a concrete 'Use when building or reviewing SwiftUI views, @Observable state, navigation, or render performance' trigger clause answering both what and when.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('building or reviewing SwiftUI views', 'navigation', 'render performance', '@Observable state') with good coverage of common phrasings, missing a few synonyms like 'SwiftUI screens' or specific framework names.	4 / 5
Distinctiveness Conflict Risk	The SwiftUI/UI-specific triggers carve a clear niche distinct from general Swift skills, with minor overlap risk against a sibling skill like swift-protocol-di-testing given shared iOS context.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: skills/swiftui-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.