[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VQC8TG772768X73CS0ADR":3,"skill-same:01M77VQC8TG772768X73CS0ADR":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77VQC8TG772768X73CS0ADR","expo-project-structure",null,"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.","tallermchector\u002F02enviosdosruedas","tallermchector","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752173?v=4","01M77VMBE7KP4GMF5KJ15E96D5","01M77VMBEYKNBGBXVQBFB2SX4A",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-project-structure\ndescription: 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.\nlicense: MIT\n---\n\n# Expo Project Structure\n\nA starting skeleton for a **new** Expo app — one with no committed folder structure yet.\n\n**Apply only to new projects.** If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything.\n\nThe whole layout, assembled from the rules below:\n\n```\n├── assets\u002F\n├── scripts\u002F\n├── src\u002F\n│   ├── app\u002F                       # Expo Router routes ONLY — every file is a route\n│   │   ├── api\u002F                   #   server API routes, grouped here\n│   │   │   ├── user+api.ts\n│   │   │   └── settings+api.ts\n│   │   ├── _layout.tsx\n│   │   ├── _layout.web.tsx         #   platform-specific layout\n│   │   ├── index.tsx\n│   │   └── settings.tsx\n│   ├── components\u002F                 # reusable UI: button, card, table…\n│   │   ├── table\u002F                  #   complex component → folder + index.tsx\n│   │   │   ├── cell.tsx\n│   │   │   └── index.tsx\n│   │   ├── bar-chart.tsx\n│   │   ├── bar-chart.web.tsx        #   platform-specific variant\n│   │   └── button.tsx\n│   ├── screens\u002F                    # screen bodies that route files render\n│   │   ├── home\u002F\n│   │   │   ├── card.tsx            #   used only by Home — not shared\n│   │   │   └── index.tsx           #   rendered by src\u002Fapp\u002Findex.tsx\n│   │   └── settings.tsx\n│   ├── server\u002F                     # server-only helpers used by app\u002Fapi\n│   │   ├── auth.ts\n│   │   └── db.ts\n│   ├── utils\u002F                      # standalone helpers + colocated tests\n│   │   ├── format-date.ts\n│   │   └── format-date.test.ts\n│   ├── hooks\u002F                      # reusable hooks: use-theme.ts…\n│   ├── constants.ts\n│   └── theme.ts\n├── app.json\n├── eas.json\n└── package.json\n```\n\n## `src\u002F` and `src\u002Fapp`\n\nKeep app code under `src\u002F` to separate it from config files. Expo Router supports both `app\u002F` and `src\u002Fapp\u002F` out of the box — to switch, move the folder and restart the bundler. The default template aliases `@\u002F*` to `.\u002Fsrc\u002F*` in `tsconfig.json`.\n\n`src\u002Fapp` is **routes-only**: every file there becomes a route, so nothing else belongs in it. Everything below lives in sibling folders.\n\n## components\u002F — reusable UI\n\nGeneric, reused UI (button, card, table) with one named export each. Name files in **kebab-case** (`bar-chart.tsx`), matching the default `create-expo-app` template. When a component grows, give it its own folder with the root in `index.tsx` and **colocate** its private sub-components beside it — the import path (`@\u002Fcomponents\u002Ftable`) stays unchanged.\n\n## screens\u002F — screen bodies\n\nBecause `app\u002F` files must be routes, complex screen UI that isn't reused has no home there. Once a screen grows big enough to need breaking out to separate components, put it in `screens\u002F` and let each route just render its screen:\n\n```tsx\nimport { Home } from \"@\u002Fscreens\u002Fhome\";\n\nexport default function HomeScreen() {\n  \u002F\u002F route-specific concerns only — e.g. read url params here\n  return \u003CHome \u002F>;\n}\n```\n\n**Colocate** a screen's private components inside its folder (`screens\u002Fhome\u002Fcomponents\u002F`). A bonus: the same screen can render under multiple routes.\n\n## server\u002F + app\u002Fapi\u002F — separate server code\n\nAppending `+api` to a file in `app\u002F` makes it a server **API route**. Server code is different from frontend code — it runs in a Node-like server environment (deployed with EAS Hosting or on [third-party services](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Fweb\u002Fapi-routes\u002F#hosting-on-third-party-services)) and can read secret env vars (`process.env.X`, not just `EXPO_PUBLIC_*`). Keep it apart:\n\n- Group all routes under `app\u002Fapi\u002F` → `\u002Fapi\u002Fuser`, `\u002Fapi\u002Fsettings`. This colocates them and avoids collisions (e.g. a `\u002Fuser` screen and a `\u002Fuser` route).\n- Put shared server-only helpers in `src\u002Fserver\u002F`.\n- Consider ESLint rules that fence `+api` files and `server\u002F` off from frontend-only checks.\n\n## Platform-specific code\n\nSmall differences: use `Platform.select` \u002F `Platform.OS`. For larger ones, split into platform files instead of inline `if\u002Felse` — `bar-chart.tsx` + `bar-chart.web.tsx`, imported extension-free (`@\u002Fcomponents\u002Fbar-chart`); Metro picks the right file per target.\n\n- Props must be identical across variants.\n- A default file (no platform extension) is always required — make it a no-op if the component is single-platform.\n- Supported extensions: `.ios`, `.android`, `.native`, `.web`.\n\n## Colocate styles and tests\n\n- **Styles:** keep the `StyleSheet.create({ ... })` object at the bottom of the component file rather than in a separate `.styles` file.\n- **Tests:** put `format-date.test.ts` next to `format-date.ts` (preferred over a separate `__tests__\u002F` folder) so tested files are obvious at a glance.\n\n## AI and config files\n\nAgent instructions live at the repo root — `AGENTS.md` \u002F `CLAUDE.md`, with project skills under `.claude\u002F`. Other config and assets stay outside `src\u002F`: `app.json` \u002F `app.config.ts`, `eas.json`, `package.json`, `assets\u002F`, and `scripts\u002F`.\n\n---\n\nBased on [Expo app folder structure best practices](https:\u002F\u002Fexpo.dev\u002Fblog\u002Fexpo-app-folder-structure-best-practices) by Kadi Kraman. For `src\u002F` precedence and alias mechanics, see the [Expo docs](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Freference\u002Fsrc-directory\u002F).\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"expo-project-structure\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n","# Expo Project Structure\n\nA starting skeleton for a **new** Expo app — one with no committed folder structure yet.\n\n**Apply only to new projects.** If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything.\n\nThe whole layout, assembled from the rules below:\n\n```\n├── assets\u002F\n├── scripts\u002F\n├── src\u002F\n│   ├── app\u002F                       # Expo Router routes ONLY — every file is a route\n│   │   ├── api\u002F                   #   server API routes, grouped here\n│   │   │   ├── user+api.ts\n│   │   │   └── settings+api.ts\n│   │   ├── _layout.tsx\n│   │   ├── _layout.web.tsx         #   platform-specific layout\n│   │   ├── index.tsx\n│   │   └── settings.tsx\n│   ├── components\u002F                 # reusable UI: button, card, table…\n│   │   ├── table\u002F                  #   complex component → folder + index.tsx\n│   │   │   ├── cell.tsx\n│   │   │   └── index.tsx\n│   │   ├── bar-chart.tsx\n│   │   ├── bar-chart.web.tsx        #   platform-specific variant\n│   │   └── button.tsx\n│   ├── screens\u002F                    # screen bodies that route files render\n│   │   ├── home\u002F\n│   │   │   ├── card.tsx            #   used only by Home — not shared\n│   │   │   └── index.tsx           #   rendered by src\u002Fapp\u002Findex.tsx\n│   │   └── settings.tsx\n│   ├── server\u002F                     # server-only helpers used by app\u002Fapi\n│   │   ├── auth.ts\n│   │   └── db.ts\n│   ├── utils\u002F                      # standalone helpers + colocated tests\n│   │   ├── format-date.ts\n│   │   └── format-date.test.ts\n│   ├── hooks\u002F                      # reusable hooks: use-theme.ts…\n│   ├── constants.ts\n│   └── theme.ts\n├── app.json\n├── eas.json\n└── package.json\n```\n\n## `src\u002F` and `src\u002Fapp`\n\nKeep app code under `src\u002F` to separate it from config files. Expo Router supports both `app\u002F` and `src\u002Fapp\u002F` out of the box — to switch, move the folder and restart the bundler. The default template aliases `@\u002F*` to `.\u002Fsrc\u002F*` in `tsconfig.json`.\n\n`src\u002Fapp` is **routes-only**: every file there becomes a route, so nothing else belongs in it. Everything below lives in sibling folders.\n\n## components\u002F — reusable UI\n\nGeneric, reused UI (button, card, table) with one named export each. Name files in **kebab-case** (`bar-chart.tsx`), matching the default `create-expo-app` template. When a component grows, give it its own folder with the root in `index.tsx` and **colocate** its private sub-components beside it — the import path (`@\u002Fcomponents\u002Ftable`) stays unchanged.\n\n## screens\u002F — screen bodies\n\nBecause `app\u002F` files must be routes, complex screen UI that isn't reused has no home there. Once a screen grows big enough to need breaking out to separate components, put it in `screens\u002F` and let each route just render its screen:\n\n```tsx\nimport { Home } from \"@\u002Fscreens\u002Fhome\";\n\nexport default function HomeScreen() {\n  \u002F\u002F route-specific concerns only — e.g. read url params here\n  return \u003CHome \u002F>;\n}\n```\n\n**Colocate** a screen's private components inside its folder (`screens\u002Fhome\u002Fcomponents\u002F`). A bonus: the same screen can render under multiple routes.\n\n## server\u002F + app\u002Fapi\u002F — separate server code\n\nAppending `+api` to a file in `app\u002F` makes it a server **API route**. Server code is different from frontend code — it runs in a Node-like server environment (deployed with EAS Hosting or on [third-party services](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Fweb\u002Fapi-routes\u002F#hosting-on-third-party-services)) and can read secret env vars (`process.env.X`, not just `EXPO_PUBLIC_*`). Keep it apart:\n\n- Group all routes under `app\u002Fapi\u002F` → `\u002Fapi\u002Fuser`, `\u002Fapi\u002Fsettings`. This colocates them and avoids collisions (e.g. a `\u002Fuser` screen and a `\u002Fuser` route).\n- Put shared server-only helpers in `src\u002Fserver\u002F`.\n- Consider ESLint rules that fence `+api` files and `server\u002F` off from frontend-only checks.\n\n## Platform-specific code\n\nSmall differences: use `Platform.select` \u002F `Platform.OS`. For larger ones, split into platform files instead of inline `if\u002Felse` — `bar-chart.tsx` + `bar-chart.web.tsx`, imported extension-free (`@\u002Fcomponents\u002Fbar-chart`); Metro picks the right file per target.\n\n- Props must be identical across variants.\n- A default file (no platform extension) is always required — make it a no-op if the component is single-platform.\n- Supported extensions: `.ios`, `.android`, `.native`, `.web`.\n\n## Colocate styles and tests\n\n- **Styles:** keep the `StyleSheet.create({ ... })` object at the bottom of the component file rather than in a separate `.styles` file.\n- **Tests:** put `format-date.test.ts` next to `format-date.ts` (preferred over a separate `__tests__\u002F` folder) so tested files are obvious at a glance.\n\n## AI and config files\n\nAgent instructions live at the repo root — `AGENTS.md` \u002F `CLAUDE.md`, with project skills under `.claude\u002F`. Other config and assets stay outside `src\u002F`: `app.json` \u002F `app.config.ts`, `eas.json`, `package.json`, `assets\u002F`, and `scripts\u002F`.\n\n---\n\nBased on [Expo app folder structure best practices](https:\u002F\u002Fexpo.dev\u002Fblog\u002Fexpo-app-folder-structure-best-practices) by Kadi Kraman. For `src\u002F` precedence and alias mechanics, see the [Expo docs](https:\u002F\u002Fdocs.expo.dev\u002Frouter\u002Freference\u002Fsrc-directory\u002F).\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"expo-project-structure\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n",{"name":5,"license":14,"description":7},"localmente","f3b25a2c5cd65a8d0bec3b60db7f86046dabea73",".cortex\u002Fskills\u002Fexpo-project-structure",2,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas","https:\u002F\u002F02enviosdosruedas.vercel.app","https:\u002F\u002Fgithub.com\u002Ftallermchector","2026-11-02 07:33:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add tallermchector\u002F02enviosdosruedas --skill expo-project-structure",{"tool":37,"command":38},"bunx","bunx skills add tallermchector\u002F02enviosdosruedas --skill expo-project-structure",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tallermchector\u002F02enviosdosruedas --skill expo-project-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",316,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-project-structure\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M77VVT9RDRSGP78TQBW156AD","expo-web-to-native","Migrate an existing web React app to a native iOS\u002FAndroid app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js\u002FVite\u002FCRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `expo-dom` skill for the DOM-component mechanism itself.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-web-to-native\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M77VVR68YB3RFKA4T4W1FSZR","expo-upgrade","Guidelines for upgrading Expo SDK versions and fixing dependency issues","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-upgrade\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M77VVH8HWSZHBQBZNZ539Y0C","expo-ui","Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-ui\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77VVAMSVHDGRRDWEQX2Q9NR","expo-skill-eval","Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-skill-eval\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77VV77S442TTSWHHFVRY9V7","expo-router","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.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-router\u002FSKILL.md",[],[],{"skillNo":88,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M77VV428CXNCHFWVPET3TZ4T","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",[],[]]