CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ios-hig-design

Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", or "iOS accessibility". Also trigger when building tab bars, navigation stacks, sheets, or modals for iOS, implementing dark mode, or adapting layouts for different screen sizes. Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

Quality

89%

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

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

This is a highly actionable, well-structured reference skill: precise HIG values and APIs throughout, a diagnostic checklist, and an exemplary one-level-deep reference bundle with every cited file present. Its main weakness is token efficiency — the 'Why it works' rationales, author history, and further-reading sections add little executable value.

Suggestions

Remove or drastically trim the 'About the Author' section and 'Further Reading' book links (including affiliate-tagged Amazon URLs) — they consume tokens without improving design execution.

Cut or compress the per-section 'Why it works' paragraphs; the 'Core concept' and 'Key insights' already convey the necessary guidance, and the rationale is largely inferable.

Add an explicit iteration step to the Scoring/Diagnostic workflow (e.g., 'after applying fixes, re-run the Quick Diagnostic and report the updated score') to close the feedback loop.

DimensionReasoningScore

Conciseness

The core framework content is dense and specific (exact pt values, API names, pattern tables), but there is real padding: eight 'Why it works' rationale paragraphs (e.g., 'Consistent navigation patterns mean users always know where they are...') that state what Claude can infer, an 'About the Author' section tracing HIG history from 1984 through Jony Ive, and a 'Further Reading' list with book links. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation') rather than 4, because the irrelevant history/reading sections go beyond 'minor instances' of over-explanation; it is well above anchor 2 since the bulk is tight, non-generic guidance.

3 / 5

Actionability

Guidance is copy-paste ready and covers the common cases: exact values ('Minimum touch target size is 44 x 44pt', 'Large Title: 34pt Bold', '16-20pt from screen edges'), exact APIs ('.font(.title)', 'Color(.label)', '.keyboardType(.emailAddress)', 'UIImpactFeedbackGenerator(style: .medium)', '.swipeActions', 'NavigationStack'), and per-context pattern tables for buttons, forms, lists, tab bars, icons, and haptics. As an instruction-only design skill this matches anchor 5's 'specific examples cover the common cases'; anchor 4's 'minor gaps' does not apply because every section gives precise, usable directives.

5 / 5

Workflow Clarity

The skill defines a clear review procedure — a 'Scoring' protocol ('rate them 0-10... Always provide the current score and specific improvements needed to reach 10/10') and a 'Quick Diagnostic' checklist with explicit if-no/action branches (e.g., 'Can a VoiceOver user complete every task? → Add accessibility labels, values, hints'). This matches anchor 4 (clear sequence with most checkpoints); it falls short of anchor 5 because there is no explicit re-validation loop (no 're-audit after fixes' step), and no destructive/batch operations apply to cap it at 3.

4 / 5

Progressive Disclosure

The body is a well-organized overview: eight framework sections each end with a scoped pointer ('See: [references/navigation.md] for detailed navigation bar and tab bar specifications'), and a 'Reference Files' section lists all 11 bundle files with one-line descriptions. All 11 referenced paths exist in references/ and are exactly one level deep, matching anchor 5's 'clear overview with well-signaled one-level-deep references... easy navigation' — anchor 4's 'minor organization gaps' is not evidenced.

5 / 5

Total

17

/

20

Passed

Description

95%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: it explicitly states what the skill does and when to use it with a rich set of natural trigger terms, and it proactively disambiguates against adjacent design skills. The only minor gap is that the capability list leans on one overarching action plus topic areas rather than an exhaustive enumeration of concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('Design native iOS interfaces following Apple Human Interface Guidelines') and enumerates concrete coverage areas ('navigation patterns, accessibility, SF Symbols, and platform conventions') plus concrete build actions in the trigger clause ('building tab bars, navigation stacks, sheets, or modals', 'implementing dark mode', 'adapting layouts'). This matches anchor 4 (several specific actions, minor gaps) rather than 5, because the core 'what' is a single overarching action with topic areas rather than the comprehensive multi-action list of the anchor-5 example; it is clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both halves are explicit: what ('Design native iOS interfaces... Covers navigation patterns, accessibility, SF Symbols, and platform conventions') and when ('Use when the user mentions...' followed by concrete trigger phrases, plus 'Also trigger when building...'). This mirrors the anchor-5 example structure exactly — clear what AND when with concrete triggers — so the anchor-3/4 'weak or missing when' anchors do not apply.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: '"iPhone app"', '"iPad layout"', '"SwiftUI"', '"UIKit"', '"Dynamic Island"', '"safe areas"', '"HIG compliance"', '"SF Symbols"', '"haptic feedback"', '"iOS accessibility"', plus 'dark mode' and 'different screen sizes'. These are exactly the phrases a user would naturally say, matching anchor 5's comprehensive synonym-level coverage; not anchor 4 since no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The iOS/HIG niche is unambiguous (SwiftUI, UIKit, Dynamic Island, SF Symbols are iOS-specific triggers) and the description even includes explicit disambiguation pointers: 'For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.' Clear niche with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/ios-hig-design/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.