CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-ui-patterns

Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-organized, lean body with executable Swift patterns and a sensible workflow, undermined by one material defect: it positions `references/components-index.md` and `references/app-scaffolding-wiring.md` as core entry points, but the bundle contains no reference files at all, so the main component guidance the skill promises cannot be loaded. Meta sections about maintaining references add tokens without user-facing value.

Suggestions

Ship the referenced files (at minimum `references/components-index.md` and `references/app-scaffolding-wiring.md`) or remove/inline those references — currently the skill's central component guidance is unreachable.

Trim the maintainer-facing sections ("Component references" expectations and "Adding a new component reference") or move them into a CONTRIBUTING-style reference file; they spend tokens on skill authorship rather than skill use.

Strengthen the workflow's validation step into a feedback loop: what to check when the build fails and when to re-run it after updating usage callsites.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — it never explains what SwiftUI is, gives a concrete `rg "TabView\("` command, and keeps rules as terse bullets. It sits at 4 rather than 5 because of meta-content that earns few tokens ("Component references" describes what reference files should contain, and "Adding a new component reference" is maintainer guidance rather than usage guidance) and some bullet redundancy with the code examples.

4 / 5

Actionability

Guidance is mostly executable: two complete Swift snippets (item-driven sheet, sheet-owns-its-actions with `dismiss()` and `@Environment`), a concrete search command, and named file paths. Not a 5 because several directives stay high-level ("Sketch the view hierarchy", "Follow the project's formatter and style guide", "explicit loading/error states" without an example) and the core component guidance is deferred to files that do not exist.

4 / 5

Workflow Clarity

"Workflow for a new SwiftUI view" is a clear 6-step sequence ending in a validation checkpoint ("Validate with a build and update usage callsites if needed"), and the Quick start tracks are sequenced. Below 5 because validation is a single mention with no error-recovery loop (what to do when the build or accessibility check fails), and step ordering is present but checkpoints are implicit elsewhere.

4 / 5

Progressive Disclosure

In-body structure is good — clear sections, clearly signaled one-level references ("Use `references/components-index.md` as the entry point", "Start with `references/app-scaffolding-wiring.md`") — but no `references/`, `scripts/`, or `assets/` directories exist in the bundle, so both entry-point references are dangling. The promised component detail is unreachable, leaving the disclosure chain broken; this fits the 'structure present but organization compromised' middle anchor rather than the good-structure anchor at 4.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description with a clear what, an explicit multi-trigger 'Use when' clause, and concrete SwiftUI-specific actions and keywords. The only weakness is mild coverage incompleteness — several actions are named but the long tail (sheets, navigation, state) is folded into generic phrasing.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "building SwiftUI views and components", "creating or refactoring SwiftUI UI", "designing tab architecture with TabView", "composing screens" — which matches the 'several specific actions; minor gaps' anchor. It falls short of 5 because coverage has gaps: body-heavy topics like sheets, navigation, and state management are only vaguely covered by "component-specific patterns and examples".

4 / 5

Completeness

It explicitly answers both: what ("Best practices and example-driven guidance for building SwiftUI views and components") and when ("Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples") with concrete trigger phrases, matching the top anchor. It is not a 4 because the 'when' clause is explicit, multi-trigger, and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "SwiftUI UI", "SwiftUI views", "TabView", "components", "composing screens", "refactoring" — terms users would plausibly say. A few natural variants are missing (e.g., "iOS app", "screens", "Swift UI" spacing), keeping it below the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"SwiftUI" plus "TabView" and "component patterns" carves out a clear niche with distinct triggers and minimal conflict risk; only a very closely related general SwiftUI/iOS skill would overlap. Not a 4 because the trigger terms (TabView, tab architecture, SwiftUI views/components) are specific enough to disambiguate from adjacent skills.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 2 possibly missing (references/app-scaffolding-wiring.md, references/components-index.md)

Warning

Total

15

/

16

Passed

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/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.