design-hig-principles
npx skills add https://github.com/jacoblewisau/design-hig-principles --skill design-hig-principles
Agent 安装分布
Skill 文档
<essential_principles>
The Three Perspectives
Every HIG audit applies these complementary lenses:
1. Clarity Perspective â “Does the interface communicate clearly?”
- Content is paramount, UI defers to it
- Every element has a purpose
- Users know what they can do without instructions
- Information hierarchy is obvious
2. Consistency Perspective â “Does this feel like an Apple platform app?”
- Standard UI elements and familiar patterns
- Navigation follows platform conventions
- Gestures work as expected
- Components appear in expected locations
3. Deference Perspective â “Does the UI stay out of the way?”
- Subtle backgrounds, restrained branding
- Content is the hero
- Controls recede when not needed
- No visual competition with content
Golden Rule: “Deference makes an app beautiful by ensuring the content stands out while the surrounding visual elements do not compete with it.” â Apple HIG </essential_principles>
Before evaluating any UI, gather project intelligence:
-
Check project type â What kind of app is this?
- Productivity tool â Emphasize Clarity + Consistency
- Media/content app â Emphasize Deference
- Creative tool â Balance all three
- Utility â Emphasize Clarity
-
Scan for common patterns
Search for: - Hardcoded colors (.white, .black, Color(red:...)) - Fixed font sizes (.system(size: 17)) - Missing accessibility labels - Custom touch targets under 44pt - Animations without Reduce Motion checks -
Identify platform targets â iOS, iPadOS, macOS, watchOS, visionOS?
-
Perform HIG Gap Analysis Search for these anti-patterns:
Color(red:orColor(hex:without asset catalog fallback.font(.system(size:withoutrelativeTo:ButtonorImagewithout.accessibilityLabel.frame(width:or.frame(height:under 44 for interactive elementswithAnimationwithout@Environment(\.accessibilityReduceMotion)
After reconnaissance, present findings and ask user to confirm context weighting before full audit.
Step 2: Full Audit
Read the audit checklist, then read perspective-specific references based on project type:
| Project Type | Primary Refs | Secondary Refs |
|---|---|---|
| Productivity | clarity.md, consistency.md | accessibility.md |
| Media/Content | deference.md, colors.md | typography.md |
| Creative | all three perspectives | platform-specific.md |
| Utility | clarity.md, accessibility.md | consistency.md |
Always include: accessibility.md review (mandatory for every audit)
Step 3: Output Format
Present findings with this structure:
âââââââââââââââââââââââââââââââââââââââââââ
â HIG AUDIT SUMMARY â
â Project: [name] | Platform: [target] â
â Critical: X | Important: Y | Minor: Z â
âââââââââââââââââââââââââââââââââââââââââââ
## Overall Assessment
[2-3 sentence summary of HIG compliance]
## Clarity Perspective
### Working Well
- [items that support clear communication]
### Issues Found
- [specific violations with file:line references]
### Perspective Summary
[How well does the UI communicate its purpose?]
---
## Consistency Perspective
### Working Well
- [items following platform conventions]
### Issues Found
- [specific violations with file:line references]
### Perspective Summary
[How well does this feel like a native app?]
---
## Deference Perspective
### Working Well
- [items that let content shine]
### Issues Found
- [specific violations with file:line references]
### Perspective Summary
[How well does the UI stay out of the way?]
---
## Combined Recommendations
| Priority | Issue | Fix | Effort |
|----------|-------|-----|--------|
| Critical | [issue] | [solution] | [Low/Med/High] |
| Important | [issue] | [solution] | [Low/Med/High] |
| Minor | [issue] | [solution] | [Low/Med/High] |
## Quick Reference
- Clarity: [focused on X]
- Consistency: [focused on Y]
- Deference: [focused on Z]
<severity_levels>
Issue Classification
Critical (Must Fix)
- Accessibility violations (contrast, touch targets, missing labels)
- Platform convention breaks (non-standard navigation, gestures)
- Dynamic Type not supported
- Reduce Motion not respected
Important (Should Fix)
- Hardcoded colors without dark mode variants
- Fixed font sizes
- Inconsistent spacing/alignment
- Missing semantic colors
Context-Dependent
- Branding placement
- Custom animations
- Non-standard controls (may be intentional)
Nice to Have
- Optical alignment refinements
- Material thickness optimization
- Platform-specific polish </severity_levels>
<reference_library>
Comprehensive Reference Library
This skill has 21 detailed reference documents covering every aspect of Apple HIG:
Core References (Always Read)
references/audit-checklist.mdâ Systematic evaluation criteria for all domainsreferences/philosophy.mdâ The “why” behind Clarity, Consistency, Deferencereferences/accessibility.mdâ Vision, mobility, cognitive, hearing accessibility (MANDATORY)references/common-mistakes.mdâ Anti-patterns with fixes
Visual Design
references/colors.mdâ Semantic color system, dark mode, contrast requirementsreferences/typography.mdâ Text styles, Dynamic Type, font weight guidelinesreferences/sf-symbols.mdâ Symbol usage, weights, rendering modes, accessibilityreferences/materials-depth.mdâ Blur, vibrancy, materials, visual layersreferences/dark-mode.mdâ Dark mode design, elevation, color adaptation
Layout & Structure
references/layout-spacing.mdâ 8pt grid, safe areas, adaptive layout, marginsreferences/lists-collections.mdâ List styles, grids, lazy loading, interactionsreferences/navigation-architecture.mdâ Navigation patterns, deep linking, state restoration
Interaction
references/controls-inputs.mdâ All system controls, forms, pickers, inputsreferences/gestures-touch.mdâ Gesture design, touch targets, hit testingreferences/modals-sheets.mdâ Sheets, alerts, popovers, confirmation dialogsreferences/motion-animation.mdâ Timing, springs, choreography, Reduce Motionreferences/haptics-feedback.mdâ UIFeedbackGenerator, sensory feedback patternsreferences/feedback-status.mdâ Progress, loading, success/error states
Platform & Polish
references/platform-specific.mdâ iOS, iPadOS, macOS, watchOS, tvOS, visionOSreferences/branding.mdâ Appropriate branding, launch screens, app iconsreferences/onboarding-ftue.mdâ First-run experience, permissions, feature discoveryreferences/localization-rtl.mdâ Internationalization, RTL support, formattingreferences/privacy-ux.mdâ Permission requests, Privacy Manifest, data handling </reference_library>
<required_reading>
Required Reading by Audit Type
Full HIG Audit
references/audit-checklist.mdâ Start herereferences/philosophy.mdâ Understand the three perspectivesreferences/accessibility.mdâ ALWAYS requiredreferences/common-mistakes.mdâ Know what to look for- Platform-specific reference(s) based on target
Quick Color/Typography Audit
references/colors.mdreferences/typography.mdreferences/dark-mode.md
Accessibility Audit
references/accessibility.mdreferences/gestures-touch.md(touch targets)references/motion-animation.md(Reduce Motion)
Navigation/Flow Audit
references/navigation-architecture.mdreferences/modals-sheets.mdreferences/platform-specific.md
Interaction Audit
references/controls-inputs.mdreferences/gestures-touch.mdreferences/haptics-feedback.mdreferences/feedback-status.md
Pre-Release Audit
Read all core references plus:
references/privacy-ux.mdreferences/localization-rtl.mdreferences/branding.md</required_reading>
<context_mapping>
Project Type â Perspective Priority
| App Category | Primary Focus | Why |
|---|---|---|
| Productivity (Linear, Notion) | Clarity + Consistency | Users have clear goals, efficiency matters |
| Media (Photos, Music) | Deference | Content is the hero |
| Social (Messages, Twitter) | Consistency | Familiarity reduces friction |
| Creative (Procreate, Figma) | Balance all | Both tool clarity and canvas deference |
| Utility (Calculator, Weather) | Clarity | Single purpose, immediate understanding |
| Games | Deference | Immersion over conventions |
| Enterprise | Consistency | Training costs, reliability |
| </context_mapping> |
<success_criteria> A complete HIG audit:
- Identifies project type and platform targets
- Applies all three perspectives appropriately weighted
- Provides specific file:line references for issues
- Includes working code examples for fixes
- Classifies issues by severity
- Always checks accessibility compliance
- Gives actionable, prioritized recommendations </success_criteria>