CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-patterns

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/swiftui-patterns/SKILL.md

The canonical home for this skill is swiftui-patterns in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is a strong, executable pattern reference: idiomatic, copy-paste-ready Swift examples with a useful wrapper-selection table and an anti-patterns section. Its main gaps are minor — a redundant intro paragraph, some basic-knowledge restatement, and no offloading of detail into reference files.

Suggestions

Remove the intro paragraph that repeats the frontmatter description, and trim basics like the stable-identifiers guidance to just the non-obvious part.

Move deeper material (e.g., the full Router/NavigationPath example or the Equatable optimization details) into a references/ file, keeping SKILL.md as a lean overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is largely lean and pattern-dense (the property-wrapper table is maximally token-efficient), but the opening paragraph duplicates the frontmatter description and the 'Stable Identifiers' section restates knowledge Claude already has.

4 / 5

Actionability

Every section gives complete, executable Swift — @Observable view model, consuming view, environment injection, ViewModifier + extension, Router with NavigationPath, LazyVStack, Equatable conformance, and #Preview macros — covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

A decision-guide skill with a clear 'choose the simplest wrapper' selection table and logically ordered sections (state → composition → navigation → performance → previews → anti-patterns); no destructive or batch operations requiring validation checkpoints, but there is no explicit task-approach sequencing either.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear headers and a References section signaling sibling skills one level deep; at ~250 lines with several self-contained topic areas (navigation, performance), some content could be split into reference files, and no bundle files exist to offload detail.

4 / 5

Total

17

/

20

Passed

Description

65%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 distinctive and domain-specific with good natural trigger terms, but it reads as a topic list rather than a statement of capabilities, and it entirely lacks a 'Use when...' clause telling Claude when to activate the skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building SwiftUI views, managing UI state, or the user mentions SwiftUI, @Observable, NavigationStack, or view performance.'

Convert topic nouns into concrete actions (e.g. 'Selects the right SwiftUI property wrapper, structures @Observable view models, and optimizes list rendering').

Drop the generic filler 'modern iOS/macOS UI best practices' in favor of specific capabilities.

DimensionReasoningScore

Specificity

Names the domain plus five concrete capability areas ('state management with @Observable', 'view composition', 'navigation', 'performance optimization'), but these are topic nouns rather than specific actions, and 'modern iOS/macOS UI best practices' is generic filler.

3 / 5

Completeness

A clear 'what' is present, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Strong natural terms a developer would actually say — 'SwiftUI', '@Observable', 'state management', 'navigation', 'performance optimization' — though common variations like '@State', 'NavigationStack', 'bindings', or 'Swift' are missing.

4 / 5

Distinctiveness Conflict Risk

'SwiftUI architecture patterns, state management with @Observable' carves out a clear niche with framework-specific triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

15

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/swiftui-patterns/SKILL.md

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.