CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-ios-design

Master iOS Human Interface Guidelines and SwiftUI patterns for building native iOS apps. Use when designing iOS interfaces, implementing SwiftUI views, or ensuring apps follow Apple's design principles.

87

1.36x
Quality

Does it follow best practices?

Impact

89%

1.36x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable body packed with executable SwiftUI examples, but it is over-long for SKILL.md and ignores its own reference bundle. The Core Concepts section re-explains concepts Claude already knows, and the detailed patterns should be offloaded to the existing reference files via clearly signaled links.

Suggestions

Replace the inline Core Concepts / SwiftUI Layout / Navigation detail with concise summaries and one-level-deep links to references/hig-patterns.md, references/swiftui-components.md, and references/ios-navigation.md so the reference bundle is actually used.

Trim the "Core Concepts" HIG-principles and platform-considerations prose, which restates knowledge Claude already has, to keep the body lean.

Either drop the "When to Use This Skill" bullet list (it duplicates the frontmatter description) or fold its triggers into the description to avoid redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code, but the "Core Concepts" section restates HIG principles and platform notes Claude already knows, and basic VStack/HStack examples plus an 8-bullet "When to Use" list (which echoes the description) could be trimmed.

2 / 3

Actionability

It is dense with fully executable, copy-paste-ready SwiftUI—NavigationStack, TabView with the iOS 18 Tab API, LazyVGrid, SF Symbols rendering modes, Dynamic Type, materials, and a complete FeatureCard component—well beyond pseudocode.

3 / 3

Workflow Clarity

This is a broad reference skill rather than a sequenced procedural workflow, so there is no multi-step sequence with validation checkpoints; sections are organized by topic but no explicit process or feedback loop is laid out.

2 / 3

Progressive Disclosure

Three reference files exist (hig-patterns.md, ios-navigation.md, swiftui-components.md) whose topics match the inline sections, yet the body never links to them; the detail that belongs in those bundles is kept inline, so references are present but not signaled.

2 / 3

Total

9

/

12

Passed

Description

100%

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 well-constructed description that concisely pairs a clear capability statement with an explicit "Use when" trigger clause and natural, domain-specific keywords. It uses third-person imperative voice and stays free of vague fluff.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions—"designing iOS interfaces, implementing SwiftUI views, or ensuring apps follow Apple's design principles"—matching the multiple-specific-actions anchor rather than the single-action score-2 example.

3 / 3

Completeness

It states what the skill does ("Master iOS HIG and SwiftUI patterns for building native iOS apps") and gives an explicit "Use when" trigger clause, satisfying both halves required for the top anchor; no missing-trigger cap applies.

3 / 3

Trigger Term Quality

Natural user-facing terms like "iOS," "SwiftUI," "designing iOS interfaces," and "Apple's design principles" give good coverage of phrases a user would actually say, rather than opaque jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply iOS-specific (HIG + SwiftUI) with distinct triggers, making it unlikely to fire for non-iOS or generic design skills.

3 / 3

Total

12

/

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
wshobson/agents
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.