CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-patterns

SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/swiftui-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

79%

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

The content is concise, actionable, and rich with executable SwiftUI examples that avoid redundant explanation, but it lacks an explicit workflow with validation checkpoints and does not split detailed material into separate reference files.

Suggestions

Add a short build/verify workflow (e.g. build in Xcode and check #Preview results) with an explicit validation checkpoint so workflow clarity can reach 3.

Consider moving the larger code-pattern reference (e.g. full NavigationStack router or performance details) into a referenced file to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes SwiftUI competence; sections are short, prescriptive, and free of explaining what SwiftUI or property wrappers are.

3 / 3

Actionability

Provides complete, executable Swift code examples for each pattern (ViewModel, environment injection, navigation, lazy stacks, Equatable) that are copy-paste ready.

3 / 3

Workflow Clarity

Guidance is organized by topic but lacks an explicit end-to-end build/validate workflow with checkpoints; no build or preview verification step is given, though the skill is mostly advisory patterns.

2 / 3

Progressive Disclosure

Content is well-organized into sections but everything is inline with no separate reference files; references only point to sibling skills, not bundle files, and inline depth is moderate.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and distinctive, naming concrete SwiftUI capability areas, but lacks an explicit when-to-activate trigger and is missing some common natural-language phrasings users might say.

Suggestions

Add an explicit Use when... clause, e.g. Use when building or debugging SwiftUI views, state management, navigation, or UI performance on iOS/macOS.

Incorporate more natural trigger phrasings users would actually say, such as SwiftUI views, iOS app UI, declarative UI, or bindings.

DimensionReasoningScore

Specificity

Lists several concrete capability areas (architecture patterns, state management with @Observable, view composition, navigation, performance optimization) rather than vague language.

3 / 3

Completeness

It clearly states what the skill covers but never gives an explicit Use when... trigger for when Claude should activate it, capping completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms like SwiftUI, state management, navigation, and performance, but omits common phrasings users would say like building iOS/macOS apps, UI, views, or declarative UI.

2 / 3

Distinctiveness Conflict Risk

The combination of SwiftUI, @Observable, and iOS/macOS UI best practices is a clear niche unlikely to trigger for non-SwiftUI skills.

3 / 3

Total

10

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.