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.
81
66%
Does it follow best practices?
Impact
89%
1.36xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ui-design/skills/mobile-ios-design/SKILL.mdQuality
Discovery
75%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 well-structured with a clear 'Use when' clause and targets a distinct niche (iOS/SwiftUI development with HIG compliance). However, it could be more specific about the concrete actions it enables and include more natural trigger terms that users would actually say when needing this skill.
Suggestions
Add more specific concrete actions like 'build navigation hierarchies, implement tab views, create adaptive layouts, handle dark mode, design accessibility-compliant interfaces'.
Include additional natural trigger terms users might say: 'HIG', 'iPhone app', 'iPad', 'mobile UI', 'SwiftUI components', 'Apple design system', '.swift'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iOS/SwiftUI) and mentions some actions ('designing iOS interfaces', 'implementing SwiftUI views', 'ensuring apps follow Apple's design principles'), but these are fairly broad and don't list specific concrete actions like 'create navigation stacks, implement tab views, build adaptive layouts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (master iOS HIG and SwiftUI patterns for building native iOS apps) and 'when' (explicit 'Use when' clause covering designing iOS interfaces, implementing SwiftUI views, or ensuring Apple design compliance). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'iOS', 'SwiftUI', 'Human Interface Guidelines', and 'Apple's design principles', but misses common user variations like 'HIG', 'UIKit', 'iPhone app', 'iPad', 'mobile UI', '.swift files', or specific component names users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of iOS, SwiftUI, and Apple's Human Interface Guidelines creates a clear niche that is unlikely to conflict with other skills. It's distinctly about Apple platform UI design and implementation. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at providing concrete, executable SwiftUI code examples that cover key iOS design patterns, making it highly actionable. However, it's overly long for a SKILL.md overview, mixing reference-level detail with high-level guidance in a single monolithic file. It could be significantly improved by trimming explanatory content Claude already knows, splitting detailed code examples into referenced files, and adding a clearer workflow for building iOS interfaces.
Suggestions
Split detailed code examples (navigation patterns, grid layouts, visual design) into separate reference files (e.g., NAVIGATION.md, LAYOUTS.md) and keep SKILL.md as a concise overview with links.
Remove the 'When to Use This Skill' section and HIG principles explanation—Claude already understands these concepts and they consume tokens without adding actionable value.
Add a brief workflow sequence for building an iOS interface (e.g., 1. Define navigation structure → 2. Build layouts → 3. Apply styling → 4. Add accessibility → 5. Test with VoiceOver) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., HIG principles like 'Clarity', 'Deference', 'Depth' that Claude already knows, platform considerations for visionOS which is tangential, and the 'When to Use This Skill' section is largely redundant). The code examples are useful but the overall document could be significantly tightened. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready SwiftUI code examples across multiple patterns (layouts, navigation, SF Symbols, Dynamic Type, visual design). The Quick Start Component is a complete, runnable view. All code is concrete and specific. | 3 / 3 |
Workflow Clarity | This is primarily a reference/pattern skill rather than a multi-step workflow, but it lacks any sequencing for how to build an iOS interface (e.g., start with navigation structure, then layout, then styling). The Best Practices and Common Issues sections are lists without clear ordering or validation checkpoints. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic document with no references to external files for detailed topics like accessibility, navigation patterns, or iPad-specific layouts. At ~200 lines, topics like grid layouts, navigation patterns, and visual design could be split into separate reference files with a concise overview here. | 1 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
27a7ed9
- 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.