- Home
- Skills
- Mobile Development
- Expo Overview: Route the Work Before You Write Code
More screenshots
Works with the AI Agents you already use
Expo Overview: Route the Work Before You Write Code
Triage any Expo or EAS request first — confirm it is Expo work, route it to the right leaf skill, and apply the shared setup rules.
$5
Expo Overview: Route the Work Before You Write Code
Example session with this skill installed
Make my app look native. It is an Expo app, but I do not know which skill or step comes first.
- Read your context and instructions
- Compiled the expo overview
Triaged and routed. Gate: request mentions Expo and package.json has an expo dependency — Expo work, both signals present. Goal restated: screens, styling, and platform feel across the app. Route: native-UI skill — not the router (no navigation mentioned) and not the UI skill (the ask is app-wide feel, not one component). Setup: SDK version detected, docs pinned to it, managed workflow confirmed. Handoff: note written with the goal, gate evidence, route, and setup facts — the native-UI skill can start from it alone. Misroute log: empty. The handoff note carries everything the native-UI skill needs to start: the goal in the user's words, the gate evidence (both signals present), the route and why it was chosen over the router and UI skills, the SDK version, the pinned docs, and the managed workflow confirmation. The misroute log is empty, and the triage took minutes against the afternoon a wrong route would have cost. The note is filed with the project so the routing decision is visible to anyone who picks the work up later. The working log holds the gate evidence and the routing decision, so the next triage of a similar request starts from a precedent. The routing decision is filed with the project for the next triage. Rubric score: 8/8.
Connects securely to your tools. The creator never sees your data.
About this skill
Expo's skill set is a toolbox, not a ladder — picking the wrong tool first wastes the whole session. This skill is the triage step: figure out what the user actually wants, name the right leaf skill, then get out of the way and let that skill's own logic drive. It covers the gate (is this Expo work?), translating the goal into a route, the shared setup rules (SDK detection, version-pinned docs, install discipline, managed vs prebuild), when to skip the triage, and a worked example. The gate is two signals, either one qualifying: the request mentions Expo or EAS, or package.json has an expo dependency. A bare React Native project with no expo dependency is not Expo work — do not force it. A purely native app using EAS only for delivery qualifies as EAS work, with routing, SDK, and package-install rules not applying to that path.
Triage routes; it does not build — the leaf skill owns the work.
- A bare React Native project without an expo dependency is not Expo work.
- A fully specified request still needs the setup rules, even when routing is skipped.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected