CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-design-ios

Use when the user asks to build iOS screens, SwiftUI views, UIKit layouts, mobile components, or any iOS app UI. Also use when styling, redesigning, or beautifying any iOS interface. Covers iOS 26 Liquid Glass design language, hierarchy, motion, and platform-native patterns.

65

1.44x
Quality

70%

Does it follow best practices?

Impact

88%

1.44x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./mobile-design-ios/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This skill provides genuinely valuable, specific iOS 26 Liquid Glass knowledge that Claude likely doesn't have from training data, with strong anti-pattern coverage and clear hierarchy principles. Its main weaknesses are the complete absence of executable SwiftUI/UIKit code examples (critical for a UI-building skill) and some verbosity in framing/motivational language. The content would benefit significantly from concrete code snippets and splitting detailed reference material into supporting bundle files.

Suggestions

Add executable SwiftUI code examples showing proper GlassEffectContainer usage, glass variant application (.regular vs .clear vs .identity), and scroll-edge behavior configuration — these are the most actionable patterns and currently exist only as prose descriptions.

Add a validation checklist or feedback loop step (e.g., 'After generating UI: verify no glass on content elements, check GlassEffectContainer grouping, test contrast with scrolling content, confirm Reduce Transparency fallback exists').

Trim the introductory paragraphs and 'Design Thinking' section — remove motivational framing like 'avoiding the generic template app aesthetic' and 'Accessibility is Non-Negotiable' header, keeping only the actionable decision points.

Extract the detailed Liquid Glass guidelines and anti-patterns list into separate bundle files (e.g., GLASS_REFERENCE.md, ANTI_PATTERNS.md) and reference them from a more concise SKILL.md overview.

DimensionReasoningScore

Conciseness

The skill contains valuable iOS 26-specific knowledge Claude wouldn't have, but includes some unnecessary framing ('This skill guides creation of iOS interfaces that feel genuinely designed...') and motivational language ('Accessibility is Non-Negotiable') that could be tightened. The 'Design Thinking' section mixes actionable guidance with philosophical padding.

2 / 3

Actionability

The skill provides specific, concrete guidance (e.g., GlassEffectContainer, .interactive() modifier, .identity glass variant, 44×44pt touch targets, 4.5:1 contrast ratios) and clear anti-patterns, but lacks any executable SwiftUI/UIKit code examples. For a UI skill targeting a specific framework, the absence of copy-paste-ready code snippets showing proper glass usage, GlassEffectContainer wrapping, or scroll behavior configuration is a significant gap.

2 / 3

Workflow Clarity

The Design Thinking section provides a reasonable sequence (purpose → personality → content-first → differentiation → then add glass), and the overall structure flows logically from principles to guidelines to anti-patterns. However, there are no explicit validation checkpoints or feedback loops for verifying the output meets the stated criteria (e.g., contrast testing on glass, checking Reduce Transparency fallbacks).

2 / 3

Progressive Disclosure

The content is well-organized with clear section headers and logical grouping (guidelines, accessibility, anti-patterns, professional traits). However, it's a fairly long monolithic document with no references to supporting files. The detailed Liquid Glass guidelines, anti-patterns list, and accessibility requirements could benefit from being split into referenced files, especially given no bundle files exist to support this.

2 / 3

Total

8

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger term coverage and completeness, clearly specifying both when to use it and what it covers. The main weakness is that the 'what it does' portion could be more specific about concrete actions/deliverables rather than broad categories. The iOS-specific terminology and framework references make it highly distinctive.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'Builds navigation stacks, tab views, form layouts, modal sheets, and custom components' rather than the broader 'iOS screens' and 'mobile components'.

DimensionReasoningScore

Specificity

The description names the domain (iOS UI) and mentions some actions like 'build iOS screens', 'styling', 'redesigning', 'beautifying', but doesn't list multiple concrete specific actions like 'create navigation bars, implement tab views, build form layouts'. The capabilities are somewhat general rather than enumerating specific deliverables.

2 / 3

Completeness

Clearly answers both 'what' (covers iOS 26 Liquid Glass design language, hierarchy, motion, platform-native patterns) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios (building iOS screens, SwiftUI views, UIKit layouts, styling/redesigning interfaces).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'iOS screens', 'SwiftUI views', 'UIKit layouts', 'mobile components', 'iOS app UI', 'styling', 'redesigning', 'beautifying', 'Liquid Glass', 'platform-native patterns'. These cover multiple natural variations of how users would request iOS UI work.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche focused specifically on iOS UI development. The mention of specific frameworks (SwiftUI, UIKit), platform (iOS), and design language (iOS 26 Liquid Glass) makes it very unlikely to conflict with other skills like general web UI or Android development skills.

3 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
ivan-magda/mobile-design-skills
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.