apple-hig
Skill8 starsChanged 24 days agoNo licenceView on GitHub
Apple Human Interface Guidelines distilled for React Native projects, organized by platform (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) with concrete RN implementation mappings, exact metrics, and review checklists. Use this skill whenever building, reviewing, or restyling any UI that runs on an Apple platform — screens, navigation, sheets, modals, alerts, lists, forms, buttons, tab bars, toolbars, typography, color, dark mode, Liquid Glass, animation, haptics, safe areas, Dynamic Type, accessibility, VoiceOver, widgets, notifications, or App Store requirements like permissions and account deletion. Also use it when the user asks whether something "feels native", "looks like an Apple app", follows the HIG, or should be adapted for iPad/Mac/TV/Vision Pro — and when porting an Android or web design to iOS, where platform conventions are most often lost. Prefer this skill over general design intuition for any Apple-platform UI decision, even when Apple or the HIG isn't mentioned by name.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- LOGIN-TB/claude-skillstheir own version, first seen Nov 1, 2026
- ykswang/apple-hig-skilltheir own version, first seen Nov 1, 2026
- AyushRajSinghParihar/apple-human-interface-skillstheir own version, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- vcompagnucci/skillstheir own version, first seen Oct 15, 2026
- jhy0285/monofieldtheir own version, first seen Oct 13, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- skopevoj/spoti.pw★ 732same name
- justinwetch/HIGAgentSkills★ 682same name
- CamilleScholtz/swmpc★ 239same name
- LOGIN-TB/claude-skills★ 82same name
- AyushRajSinghParihar/apple-human-interface-skills★ 27same name
- jhy0285/monofield★ 6same name
- ebuntario/apple-hig★ 4same name
- Elevatormusic/apple-hig★ 4same name
- ykswang/apple-hig-skill★ 4same name
- jpoindexter/theft-kit★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.