What is expo-ios-hig?

A guide to building Expo and React Native interfaces that follow Apple’s Human Interface Guidelines, which are Apple’s recommendations for iPhone and iPad app design. It covers native navigation, system controls, safe areas, dark mode, text sizing, accessibility, haptics, and motion.

It is for building or reviewing iOS screens, navigation, lists, forms, controls, colors, typography, sheets, modals, and platform interactions.

It helps an Expo app behave and look like an iOS app instead of a web page or an Android interface placed on an iPhone.

expo-ios-hig — Skill for Claude Code and Codex by pproenca

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add pproenca/dot-skills --skill expo-ios-hig

Clone the repo

git clone --depth 1 https://github.com/pproenca/dot-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pproenca/dot-skills/expo-ios-hig/github.svg)](https://agentmods.dev/skills/pproenca/dot-skills/expo-ios-hig)

Your own site

<a href="https://agentmods.dev/skills/pproenca/dot-skills/expo-ios-hig"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/expo-ios-hig/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pproenca/dot-skills/expo-ios-hig"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/expo-ios-hig.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 163 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,342 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00163	$0.02342
Opus 5	$0.00081	$0.01171
Sonnet 5	$0.00033	$0.00468
Haiku 4.5	$0.00016	$0.00234

Measured 6d ago against content hash 83b2e6a0fc8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

expo-ios-hig scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/.experimental/expo-ios-hig/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Expo iOS HIG Best Practices

Design rules for building iOS 26 apps in Expo (React Native) that feel genuinely native under Apple's Human Interface Guidelines. Contains 46 rules across 8 categories, prioritized by how much each decision affects native feel and HIG compliance. Every example is TSX/Expo — the decisions you make in React Native and TypeScript, not Swift.

The core idea: a React Native app feels native when it reaches for the platform — the system navigation controller, system controls, semantic colors, SF Symbols, real haptics, the system share sheet — instead of re-implementing iOS in JavaScript. These rules say which decision earns the native feel and which one quietly forfeits it.

When to Apply

Reference these guidelines when:

Building or reviewing iOS screens, navigation, lists, or forms in an Expo app
Choosing navigation: Expo Router native stack vs JS stack, native tabs, sheets, modals, large titles
Picking controls: when to use the native Alert, ActionSheetIOS, date picker, Switch, SF Symbols, or drop to @expo/ui
Styling for the platform: safe areas, dark mode, semantic colors, the iOS type scale, spacing, Liquid Glass
Making interaction feel native: touch targets, press feedback, swipe actions, pull-to-refresh, gestures, haptics
Adding motion, loading/empty states, accessibility, permissions, and launch polish

When NOT to Use This Skill

The @expo/ui component API — for how to use @expo/ui/swift-ui components, Host boundaries, and modifiers, use the expo-ui skill. This skill says which decisions make an app native and points to @expo/ui when dropping to SwiftUI is the right call; it does not re-document that API.
The cross-platform design system itself — for the shared Unistyles theme, design tokens, variant-driven component APIs, and making components feel native on web as well as iOS, use the expo-design-system skill. This skill governs iOS native feel; that one governs the token and component architecture that the two frontends share.
Native Swift / SwiftUI — for HIG in a native Swift codebase, use ios-hig or ios-design. This skill's examples are all React Native/TSX.
Android — these rules target iOS conventions. Use platform-adaptive code so Android gets Material; don't apply iOS idioms there.

Read the full file on GitHub · 129 lines

Files

What ships with it

50 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 129 lines · 163 tokens per session scan A 83b2e6a0fc8b

Subscribe to this mod's changes

expo-ios-hig is a skill published in the GitHub repository pproenca/dot-skills (206 stars, last pushed 25d ago), licensed MIT. It adds 163 tokens to every session and 2,342 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Design and UX Mobile

display-glasses-with-jetpack-compose-glimmer

Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…

android/skills · 91 tokens

expo-design-system

Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…

expo/skills · 201 tokens

expo-ios-hig