Expo Router

What it does

This source concentrates on navigation structure rather than the styling of individual controls. It connects file-based routes and groups with links, native navigation containers and screen presentation. A useful outcome is a route structure that matches the intended user journey and behaves consistently when a screen is opened from different entry points.

Best for

An Expo app adding a screen, reorganizing navigation, introducing a modal or correcting back and deep-link behavior. Supply the existing route tree and identify which URLs or navigation paths must remain compatible.

Tradeoffs and requirements

Native presentation features can depend on platform and OS versions. Moving route files can break links even if the new screen renders correctly. The skill's examples should be reconciled with the installed Expo and router versions, and navigation refactoring should not silently redesign the surrounding screens.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/expo/skills/tree/05754e71d02abe0d2d7a2fb5259ccac41f5ea59c/plugins/expo/skills/expo-router --skill expo-router

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

64/100

64

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Map the important routes and entry points, implement a small navigation change, then test forward, back and direct entry. Pair with expo-native-ui for the screen's controls and with the project's accessibility review.

How to judge the result

Check deep links, app restoration, tab state and modal dismissal on relevant platforms. Confirm that route changes preserve existing links and do not expose a screen before its required access checks.