expo-overview
所有 Expo 或 EAS 任务的入口与路由。当请求、PRD 或规格说明提到 Expo、EAS、Expo Go 或某个 expo-* 包，或项目的 `package.json` 中存在 `expo` 依赖时，应先加载此技能——在编写代码之前、在选择其他 expo-* / eas-* 技能之前。在该前提下，它还涵盖待实现的应用规格与设计（标签页、堆栈、地图、列表、导航、根据截图构建），以及诸如“实现一个移动应用”“让我的应用看起来像原生”“添加导航”“获取一些数据”“升级我的 SDK”“将 Expo 添加到现有原生应用”“发布到 App Store”或“我是 Expo 新手，该从哪里开始”等表述。即使请求已完全明确（SDK 已固定、库已指定、布局已给出），仍会经由此处路由——共享设置规则依然适用。当两种信号都不存在时不要加载：没有 `expo` 依赖的纯 React Native 项目不属于 Expo 工作。它会识别真实目标，路由到正确的 expo-* / eas-* 技能，并负责共享设置规则。
机器翻译查看英文原文
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 rul
适用对象：移动应用开发。自动收录 · 待核查。
原作者说明节选
从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。
查看英文原文
原文涵盖的主题
- expo-overview — router & shared rules for Expo / EAS
- Start Here — read before doing anything
- Skill Map (by goal)
- Translating vague asks
- Shared setup rules
- When to skip the router hop
- Submitting Feedback
Do not guess the skill from project files alone. Many Expo goals look similar from the filesystem but need different skills. 1. Confirm this is Expo or EAS work — the request mentions Expo or EAS, or package.json has an expo dependency. Otherwise this skill does not apply. A native app using EAS for delivery qualifies without an Expo runtime. 2. Read the user's goal — what outcome do they want, in plain terms? 3. Classify it using the Skill Map below, translating casual phrasing to a goal. 4. Confirm intent if ambiguous ("Sounds like you want to ship to the stores — that's eas-app-stores. Right?"), then load that skill's SKILL.md and follow it. 5. Trust the leaf skill — it has its own detection logic and steps. Don't improvise. Match the goal to a category, then the skill, then load that leaf's SKILL.md. Build the app expo-project-structure — folder layout for a new Expo Router project: where screens, components, and config live (never restructure an existing app to match) expo-native-ui — screens, styling, semantic colors, native controls, SF Symbols, media, layout expo-router — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers expo-animation — motion
这里只展示节选，请以完整原文和当前要求为准。
- 来源仓库
- expo/skills
- 源文件
- plugins/expo/skills/expo-overview/SKILL.md
- 固定版本
- a9e5bd3fa00b4e61f632e43f85da73aee1942582
来源与内容状态
本条为自动发现的元数据，尚未完成人工文档核查；适用性与运行结果待核查。
原作者：Expo Skills · 原作者仓库元数据。文档核查：未核查。最近来源检查：2026-11-09T14:01:42.077Z。
分类由名称、说明与路径规则生成，分类不代表已核实适配。
许可与权利归属
MIT。第三方内容及版权归原作者，使用条件以原文为准。
许可原文 ↗本站没有因同步、复制或用户自报成功而将资源标为运行验证通过。
限制与注意事项
- 元数据收录不代表本站已经安装、适配、实测或进行安全审查。