CtrlK
BlogDocsLog inGet started
Tessl Logo

apple-hig-expert

Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines, including the Liquid Glass design language (announced WWDC25, shipped with iOS 26/macOS Tahoe, Sept 2025). Use when reviewing an Apple-platform mockup or app for HIG compliance, checking contrast or tap-target sizes, or designing native-feeling Apple UI (e.g., 'audit my iOS app against the HIG', 'is this text readable on Liquid Glass?').

74

Quality

93%

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

82%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 strong, highly actionable skill body: real verified tool output, concrete fix guidance, clear modes and embedded validation. The main defects are a dangling reference to a nonexistent audit template and inline time-sensitive version/date enumeration that belongs in a reference or a changelog-style section.

Suggestions

Create templates/hig-audit-template.md (or remove the reference) — Mode 2 instructs 'fill in templates/hig-audit-template.md' but the file is absent from the bundle, leaving the audit workflow with a dead-end step.

Move the WWDC25 announcement date and the iOS/iPadOS/macOS/watchOS/tvOS/visionOS 26 version enumeration out of Core Design Principles into references/visual-design.md or a versioned-changelog section, keeping the body evergreen (the 'verify against the live HIG pages' note already covers drift).

Make the audit feedback loop explicit in Mode 2: apply fixes, re-run `hig_checker.py batch`, and confirm the score reaches the 90-100 ship band before delivering the report.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the Core Design Principles section inlines time-sensitive version enumeration ("announced at WWDC25, June 2025; shipped Sept 2025 across iOS 26, iPadOS 26, macOS Tahoe, watchOS 26, tvOS 26, visionOS 26") which the guidelines penalize when not placed in a deprecated/old-patterns section. This is the only real over-explanation, so it sits at 'minor instances that could be trimmed' rather than the mostly-inefficient level below.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: the three documented subcommands run as written (verified: `hig_checker.py contrast "#8E8E93" "#FFFFFF"` -> "Contrast Ratio: 3.26 [FAILED]"; `batch audit.json` -> the exact worked-example JSON shown), plus a concrete input schema and specific fixes ("Use `.secondaryLabel` (semantic color) instead of hardcoded `#8E8E93`", "expand the hit region to 44x44 with padding/`contentShape`"). The worked example covers the common audit case end-to-end, matching the top anchor.

5 / 5

Workflow Clarity

The two modes are clearly sequenced and validation is embedded in the tool (FAILED flags, scorecard thresholds "90-100 = ship, 70-80 = fix before release, below 70 = systematic rework") with a manual re-test checkpoint ("re-test caption contrast against the *busiest* underlying region and with Reduce Transparency on"). Not 5 because Mode 2's step "fill in `templates/hig-audit-template.md`" points to a file that does not exist in the bundle, and the fix -> re-run -> confirm loop is implied rather than explicit; the batch operation is read-only measurement, so the destructive-batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

Good structure with well-signaled, one-level-deep references that all exist and are topic-matched (`references/visual-design.md`, `references/accessibility.md`, `references/platform-specifics.md`, `scripts/hig_checker.py`), and reference files contain no nested references. Not 5 because the body references `templates/hig-audit-template.md` in Mode 2 but no templates/ directory exists in the bundle — a dangling path that breaks navigation for a core workflow component.

4 / 5

Total

17

/

20

Passed

Description

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

The description is exemplary: concrete third-person actions, an explicit 'Use when' clause with quoted natural trigger phrases, full platform enumeration, and a clearly distinct niche. The parenthetical date/version detail adds slight length but carries trigger-relevant currency information and does not dilute specificity.

DimensionReasoningScore

Specificity

"Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines" plus "checking contrast or tap-target sizes, or designing native-feeling Apple UI" lists multiple specific concrete actions with comprehensive coverage of the domain, in third-person voice. No material coverage gaps keep it out of the anchor-5 band.

5 / 5

Completeness

Explicitly answers both questions: the 'what' ("Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines, including the Liquid Glass design language") and the 'when' ("Use when reviewing an Apple-platform mockup or app for HIG compliance, checking contrast or tap-target sizes, or designing native-feeling Apple UI") with concrete example trigger phrases — structurally identical to the anchor-5 exemplar.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including quoted user phrasings users would actually say ("audit my iOS app against the HIG", "is this text readable on Liquid Glass?") alongside keywords (HIG compliance, contrast, tap-target sizes, mockup, and all four platform names). The quoted triggers are the strongest possible form of natural phrasing, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

"Against the Apple Human Interface Guidelines" with Apple-platform-specific triggers (HIG compliance, Liquid Glass, tap-target sizes on iOS/macOS/watchOS/visionOS) carves a clear niche with minimal conflict risk against generic design or web-UI skills; no neighboring anchor fits better.

5 / 5

Total

20

/

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
alirezarezvani/claude-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.