expo-router
Skill1 starsChanged 9 months agoNo licenceView on GitHub
Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.
12 other projects use a version of this, 8 of them edited.
Adopted by
Most recently taken up by
- fatihkan/baditheir own version, first seen Nov 16, 2026
- NoyaraAI/Noyaraedited, first seen Nov 15, 2026
- alexj11324/Mikkaedited, first seen Nov 15, 2026
- dalonga-kohi/mawledited, first seen Nov 8, 2026
- deonmenezes/mobile-app-skillword for word, first seen Nov 1, 2026
- jsmastery-pro/airbnb-cloneword for word, first seen Nov 1, 2026
Used with
Projects with it also use expo-project-structure, expo-overview and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
arcboxlabsSkillexpo-project-structure
Framework (OSS). Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.
Also in 7 projects that use this
deonmenezesSkillexpo-overview
Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.
Also in 5 projects that use this
CaiZongyuanSkillexpo-ui
This skill should be used when users need to work with Expo UI (@expo/ui) for integrating SwiftUI components into React Native applications. It provides comprehensive guidance on installation, Host component, SwiftUI primitives, layouts, modifiers, native tabs navigation, and v10 preview features.
Also in 5 projects that use this
NoyaraAISkillexpo-upgrade
Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues
Also in 4 projects that use this
NoyaraAISkilleas-hosting
EAS service (paid). Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.
Also in 3 projects that use this
jsmastery-proSkillexpo-design-system
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 creating or organizing theme files and design tokens (theme.ts / theme/), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, fixing an app that looks AI-generated or generic instead of native (the named native-slop tells), building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for folder layout of a new app use expo-project-structure.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 2
- jsmastery-pro/airbnb-clone★ 16100% same
- deonmenezes/mobile-app-skill★ 4100% same
Edited · 8
- openvetta/open-vetta★ 29999% same
- arcboxlabs/linkcode★ 14797% same
- alexj11324/Mikka★ 8794% same
- maomaochong-ai/open-astravia★ 5399% same
- dalonga-kohi/mawl★ 294% same
- mahik504/orchestra-workflow★ 197% same
- NoyaraAI/Noyara★ 197% same
- patinaproject/skills★ 197% same
Wrote their own version · 2
- fatihkan/badi★ 8same name
- hinode-codes/claude_skills★ 0same name
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.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- eas-app-storesSkill
- eas-updateSkill
- expo-data-fetchingSkill
- expo-native-uiSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 11 are common, 1 is distinctive, and 4 are very specific to this project.
11
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
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 10 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.

