How do I install the Review Hig Compliance skill?

Run npx skillmds@latest add 0xkoru/review-hig-compliance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review Hig Compliance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review Hig Compliance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review Hig Compliance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review Hig Compliance?

0xKoru (@0xkoru) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review Hig Compliance by 0xkoru — Agent Skill

Name: Review Hig Compliance
Rating: 4.2 (5 reviews)
Author: 0xKoru

Review Hig Compliance

Review iOS, iPadOS, macOS, SwiftUI, Flutter, React, or web interfaces for Apple Human Interface Guidelines fit. Use when Codex needs to audit screenshots, designs, code, prototypes, PRs, Figma exports, frontend screens, or app flows for native Apple feel, accessibility, typography, layout, navigation, controls, color, materials, Dynamic Type, safe areas, and implementation risks.

0xKoru Updated Sep 22, 2026

File contents

Review HIG Compliance

Use this skill to evaluate an interface against Apple-style product quality. Lead with actionable findings.

Workflow

Identify platform target: iOS, iPadOS, macOS, web with Apple style, or mixed.
Inspect the artifact: screenshot, running app, code, design spec, or PR diff. If possible, verify at multiple viewport sizes and color schemes.
Review in this order: task clarity, navigation model, layout and safe areas, controls, typography, color/materials, accessibility, motion, states, and implementation details.
Separate HIG issues from personal taste. Explain why each issue affects usability, platform fit, accessibility, or implementation quality.
Give fixes that are specific enough to implement. Include file/line references for code reviews when available.
End with residual risks and the smallest next verification step.

Finding Priorities

P0: Blocks core use, severe accessibility failure, data loss, unsafe destructive action.
P1: Major platform mismatch, broken navigation, unreadable text, impossible Dynamic Type, unsafe safe-area overlap.
P2: Noticeable HIG mismatch, inconsistent controls, weak hierarchy, incomplete states.
P3: Polish, naming, spacing, icon choice, minor consistency.

Review Heuristics

Native feel: does the layout use familiar platform structures, or does it import web/desktop habits into iOS?
Hierarchy: can a first-time user tell what matters and what to do next?
Adaptation: does it survive small screens, iPad widths, orientation changes, large text, localization, and dark mode?
Controls: are actions in expected places, with 44pt targets on touch platforms and clear affordances?
Materials: does blur/glass clarify layers without harming contrast?
Accessibility: are labels, focus order, contrast, motion, touch targets, and non-color cues present?

References

Read references/hig-audit-checklist.md for a detailed checklist and source links.

---name: review-hig-compliancedescription: Review iOS, iPadOS, macOS, SwiftUI, Flutter, React, or web interfaces for Apple Human Interface Guidelines fit. Use when Codex needs to audit screenshots, designs, code, prototypes, PRs, Figma exports, frontend screens, or app flows for native Apple feel, accessibility, typography, layout, navigation, controls, color, materials, Dynamic Type, safe areas, and implementation risks.---# Review HIG ComplianceUse this skill to evaluate an interface against Apple-style product quality. Lead with actionable findings.## Workflow1. Identify platform target: iOS, iPadOS, macOS, web with Apple style, or mixed.2. Inspect the artifact: screenshot, running app, code, design spec, or PR diff. If possible, verify at multiple viewport sizes and color schemes.3. Review in this order: task clarity, navigation model, layout and safe areas, controls, typography, color/materials, accessibility, motion, states, and implementation details.4. Separate HIG issues from personal taste. Explain why each issue affects usability, platform fit, accessibility, or implementation quality.5. Give fixes that are specific enough to implement. Include file/line references for code reviews when available.6. End with residual risks and the smallest next verification step.## Finding Priorities- P0: Blocks core use, severe accessibility failure, data loss, unsafe destructive action.- P1: Major platform mismatch, broken navigation, unreadable text, impossible Dynamic Type, unsafe safe-area overlap.- P2: Noticeable HIG mismatch, inconsistent controls, weak hierarchy, incomplete states.- P3: Polish, naming, spacing, icon choice, minor consistency.## Review Heuristics- Native feel: does the layout use familiar platform structures, or does it import web/desktop habits into iOS?- Hierarchy: can a first-time user tell what matters and what to do next?- Adaptation: does it survive small screens, iPad widths, orientation changes, large text, localization, and dark mode?- Controls: are actions in expected places, with 44pt targets on touch platforms and clear affordances?- Materials: does blur/glass clarify layers without harming contrast?- Accessibility: are labels, focus order, contrast, motion, touch targets, and non-color cues present?## ReferencesRead `references/hig-audit-checklist.md` for a detailed checklist and source links.

Frequently asked questions