CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-ui-patterns

Apply proven SwiftUI UI patterns for navigation, sheets, async state, and reusable screens.

Quality

76%

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-ui-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a strong instruction-only skill: prescriptive, concrete rules, a state-ownership decision table, and a workflow with explicit build-validation checkpoints and failure-recovery loops. Its main flaws are a dangling empty 'Quick start' section, some cross-section repetition, and the absence of any minimal code skeletons in the main body.

Suggestions

Fix the empty '## Quick start' heading by either removing it or placing the two-track entry ('Existing project' / 'New project scaffolding') directly under it.

Consolidate the repeated async/sheet guidance and reference pointers so each rule and each reference path is stated once, trimming token cost.

Inline one minimal skeleton (e.g., a 10-line AppTab + NavigationStack shell) so the 'New project scaffolding' track is immediately executable before opening references/app-wiring.md.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no padding explaining concepts Claude already knows, assuming competence throughout ('Prefer composition; keep views small and focused'). It falls short of a 5 due to redundancy: async, sheet, and reference-pointer guidance is repeated across 'General rules', the workflow, and 'Cross-cutting references'.

4 / 5

Actionability

Concrete, specific guidance throughout: exact API names ('.sheet(item:)' over '.sheet(isPresented:)', '.task(id:)'), a runnable command ('rg "TabView\("'), and a state-ownership decision table mapping scenarios to wrappers. Not a 5 because there is no copy-paste-ready code and some steps remain abstract ('Sketch the view hierarchy, routing model, and presentation points').

4 / 5

Workflow Clarity

The 'Workflow for a new SwiftUI view' section gives a clear 6-step sequence with explicit validation checkpoints ('Build and verify no compiler errors before proceeding', 'Validate with a build') and error-recovery feedback loops ('**If the build fails:** read the error message carefully, fix the identified issue, then rebuild before proceeding', plus preview-crash isolation and re-run). This matches the score-5 anchor; not a 4 because no checkpoint is missing or merely implicit.

5 / 5

Progressive Disclosure

The body is a genuine overview pointing to 30 one-level-deep reference files, all of which exist, with a well-signaled components index listing 'when to use' guidance per entry. Not a 5 because of minor organization gaps: a dangling empty '## Quick start' header with no content beneath it, and reference pointers repeated across three separate sections.

4 / 5

Total

17

/

20

Passed

Description

61%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 clearly identifies its domain and enumerates relevant focus areas, but relies on a single generic verb and omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause and more concrete action verbs would raise most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or refactoring SwiftUI views, wiring navigation, or presenting sheets.'

Replace the generic 'Apply proven... patterns' with concrete actions such as 'wire TabView and NavigationStack routing, present item-driven sheets, and manage async loading state'.

Include natural trigger variations like 'SwiftUI views', 'iOS app UI', or 'sheet'/'tab' that users would plausibly say when needing this skill.

DimensionReasoningScore

Specificity

The only action verb is the generic 'Apply proven SwiftUI UI patterns', while 'navigation, sheets, async state, and reusable screens' name focus areas rather than concrete actions. It exceeds the score-2 anchor (bare domain naming) but lacks the several distinct concrete actions needed for a 4.

3 / 5

Completeness

The 'what' is clear (apply SwiftUI UI patterns across navigation, sheets, async state, reusable screens) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural user terms like 'SwiftUI', 'navigation', 'sheets', and 'screens' are present and would be said when this skill is needed. A few common variations are missing ('views', 'iOS', 'tab'), so it falls short of the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

'SwiftUI' carves out a clear niche with minimal conflict risk against unrelated skills. It is not a 5 because overlap remains with closely related general Swift or iOS UI skills, and the absence of explicit trigger phrases weakens disambiguation.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/swiftui-ui-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.