opencode-skills-collection 3.1.12 → 3.1.13

package/bundled-skills/expo-deployment/references/workflows.md

@@ -0,0 +1,160 @@
+# EAS Workflows
+
+Automate builds, submissions, and deployments with EAS Workflows. The examples below are deployment-oriented starting points.
+
+When you need to write, edit, or validate a workflow YAML file beyond these examples, use the `expo-cicd-workflows` skill.
+
+## Web Deployment
+
+Deploy web apps on push to main:
+
+`.eas/workflows/deploy.yml`
+
+```yaml
+name: Deploy
+
+on:
+  push:
+    branches:
+      - main
+
+# https://docs.expo.dev/eas/workflows/syntax/#deploy
+jobs:
+  deploy_web:
+    type: deploy
+    params:
+      prod: true
+```
+
+## PR Previews
+
+### Web PR Previews
+
+```yaml
+name: Web PR Preview
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  preview:
+    type: deploy
+    params:
+      prod: false
+```
+
+### Native PR Previews with EAS Updates
+
+Deploy OTA updates for pull requests:
+
+```yaml
+name: PR Preview
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  publish:
+    type: update
+    params:
+      branch: "pr-${{ github.event.pull_request.number }}"
+      message: "PR #${{ github.event.pull_request.number }}"
+```
+
+## Production Release
+
+Complete release workflow for both platforms:
+
+```yaml
+name: Release
+
+on:
+  push:
+    tags: ['v*']
+
+jobs:
+  build-ios:
+    type: build
+    params:
+      platform: ios
+      profile: production
+
+  build-android:
+    type: build
+    params:
+      platform: android
+      profile: production
+
+  submit-ios:
+    type: submit
+    needs: [build-ios]
+    params:
+      platform: ios
+      profile: production
+
+  submit-android:
+    type: submit
+    needs: [build-android]
+    params:
+      platform: android
+      profile: production
+```
+
+## Build on Push
+
+Trigger builds when pushing to specific branches:
+
+```yaml
+name: Build
+
+on:
+  push:
+    branches:
+      - main
+      - release/*
+
+jobs:
+  build:
+    type: build
+    params:
+      platform: all
+      profile: production
+```
+
+## Conditional Jobs
+
+Run jobs based on conditions:
+
+```yaml
+name: Conditional Release
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  check-changes:
+    type: run
+    params:
+      command: |
+        if git diff --name-only HEAD~1 | grep -q "^src/"; then
+          echo "has_changes=true" >> $GITHUB_OUTPUT
+        fi
+
+  build:
+    type: build
+    needs: [check-changes]
+    if: needs.check-changes.outputs.has_changes == 'true'
+    params:
+      platform: all
+      profile: production
+```
+
+## Tips
+
+- Use `workflow_dispatch` for manual production releases
+- Combine PR previews with GitHub status checks
+- Use tags for versioned releases
+- Keep sensitive values in EAS Secrets, not workflow files

package/bundled-skills/expo-dev-client/SKILL.md

@@ -1,29 +1,27 @@
 ---
 name: expo-dev-client
-description: Build and distribute Expo development clients locally or via TestFlight
+description: Build Expo app for development
 risk: unknown
-source: community
-version: 1.0.0
+source: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-dev-client
+source_repo: expo/skills
+source_type: official
+date_added: 2026-07-01
 license: MIT
+license_source: https://github.com/expo/skills/blob/main/LICENSE
 ---
 
 Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.
 
-## When to Use
-- You need an Expo development client because the app depends on custom native code or targets not supported by Expo Go.
-- The task involves building, distributing, or testing EAS development builds on physical devices.
-- You need guidance on when to choose a dev client versus staying on plain Expo Go.
-
 ## Important: When Development Clients Are Needed
 
-**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.
+**Development clients are the recommended setup for any real or production app.** Expo Go is a playground for learning and quick experiments with the native libraries it bundles; most apps outgrow it and move to a development client. See [Expo Go vs. development builds](https://docs.expo.dev/develop/development-builds/introduction/) for the full reasoning.
 
 You need a dev client ONLY when using:
+
 - Local Expo modules (custom native code)
 - Apple targets (widgets, app clips, extensions)
 - Third-party native modules not in Expo Go
-
-**Try Expo Go first** with `npx expo start`. If everything works, you don't need a dev client.
+- Config plugins, or testing remote push notifications and App/Universal Links
 
 ## EAS Configuration
 
@@ -52,6 +50,7 @@ Ensure `eas.json` has a development profile:
 ```
 
 Key settings:
+
 - `developmentClient: true` - Bundles expo-dev-client for development builds
 - `autoIncrement: true` - Automatically increments build numbers
 - `appVersionSource: "remote"` - Uses EAS as the source of truth for version numbers
@@ -65,11 +64,13 @@ eas build -p ios --profile development --submit
 ```
 
 This will:
+
 1. Build the development client in the cloud
 2. Automatically submit to App Store Connect
 3. Send you an email when the build is ready in TestFlight
 
 After receiving the TestFlight email:
+
 1. Download the build from TestFlight on your device
 2. Launch the app to see the expo-dev-client UI
 3. Connect to your local Metro bundler or scan a QR code
@@ -80,6 +81,10 @@ Build a development client on your machine:
 
 ```bash
 # iOS (requires Xcode)
+## When to Use
+
+Use this skill when you need build Expo app for development.
+
 eas build -p ios --profile development --local
 
 # Android
@@ -87,6 +92,7 @@ eas build -p android --profile development --local
 ```
 
 Local builds output:
+
 - iOS: `.ipa` file
 - Android: `.apk` or `.aab` file
 
@@ -139,6 +145,7 @@ eas build:view
 ## Using the Dev Client
 
 Once installed, the dev client provides:
+
 - **Development server connection** - Enter your Metro bundler URL or scan QR
 - **Build information** - View native build details
 - **Launcher UI** - Switch between development servers
@@ -155,22 +162,26 @@ npx expo start --dev-client
 ## Troubleshooting
 
 **Build fails with signing errors:**
+
 ```bash
 eas credentials
 ```
 
 **Clear build cache:**
+
 ```bash
 eas build -p ios --profile development --clear-cache
 ```
 
 **Check EAS CLI version:**
+
 ```bash
 eas --version
 eas update
 ```
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Use this skill only when the task clearly matches its upstream product or API scope.
+- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
+- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/expo-dev-client/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Dev Client"
+  short_description: "Create and use Expo development clients when Expo Go is not enough"
+  default_prompt: "Use $expo-dev-client to decide whether an Expo development client is required, configure development EAS profiles, build local or cloud dev clients, and connect them to Metro."

package/bundled-skills/expo-examples/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: expo-examples
+description: Expo's official example projects — the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical,...
+risk: unknown
+source: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples
+source_repo: expo/skills
+source_type: official
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/expo/skills/blob/main/LICENSE
+---
+
+# Expo Examples
+## When to Use
+
+Use this skill when you need expo's official example projects — the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical,...
+
+
+[expo/examples](https://github.com/expo/examples) is Expo's official library of ~70 **integration examples** — directories named `with-<library>` (e.g. `with-stripe`, `with-maps`), each built around **one** library or service. These are not full apps: they're **managed** projects (no `ios/`/`android/` dirs — native setup is via config plugins), and the typical one is a **single screen of ~100–200 lines**. Mine them for the canonical integration *pattern* — the dependency set, `app.json` config plugins, and minimal wiring Expo maintains against the current SDK — and adapt that into the user's app. Don't expect to lift an application architecture from them.
+
+Reach for an example before hand-rolling an integration. (Kinds — full-stack, showcases, starters — are noted in `./references/catalog.md`.)
+
+## Two modes
+
+1. **Inspiration / adapt** (most common) — the user already has a project. Find the matching example, read its key files, and apply the *pattern* to their code.
+2. **Scaffold** — greenfield. Start a fresh project directly from the example.
+
+## Workflow
+
+### 1. Find the right example
+
+Map the user's need to an example name (e.g. payments → `with-stripe`, auth → `with-clerk`). `./references/catalog.md` is a categorized snapshot for fast triage — but it drifts, so confirm against the live list:
+
+```bash
+# Live example names:
+gh api repos/expo/examples/contents --jq '.[] | select(.type=="dir" and (.name|startswith(".")|not)) | .name'
+# Aliases (renamed) + deprecated (dead/moved) examples — check before recommending:
+gh api repos/expo/examples/contents/meta.json --jq '.content' | base64 -d
+```
+
+`meta.json` is the source of truth for what's renamed or dead (deprecated examples are removed from the repo tree but still listed here, each with a `message`). If an example is in its `deprecated` map, don't recommend it — follow the `message` to the modern path. If it's in `aliases`, use the `destination`.
+
+### 2a. Inspiration mode — study without touching the user's project
+
+The common case: the user already has an app and wants to see how Expo does something. Read the example as **reference** and apply the patterns by hand — never scaffold an example on top of their project.
+
+**First, list the whole example in one call.** Integration code is often nested (e.g. Stripe's server routes live in `app/api/`), so a one-level listing misses the important files:
+
+```bash
+gh api 'repos/expo/examples/git/trees/master?recursive=1' \
+  --jq '.tree[].path | select(startswith("with-stripe/"))'
+```
+
+**Then read the high-signal files first:** `README.md` (setup) → `package.json` (deps) → `app.json` (config plugins / permissions) → the integration code the manifest revealed → `.env` (required secrets). Per file:
+
+```bash
+gh api repos/expo/examples/contents/with-stripe/utils/stripe-server.ts --jq '.content' | base64 -d
+# No gh? Raw URL (branch is master):
+curl -s https://raw.githubusercontent.com/expo/examples/master/with-stripe/utils/stripe-server.ts
+```
+
+**Reading more than a couple of files?** Many integrations are spread across server routes, a client provider, and config (Stripe is). Skip the per-file calls — pull the whole example into a **throwaway/gitignored dir (not the user's project)** and read it freely with Grep/Read, then apply by hand:
+
+```bash
+npx degit expo/examples/with-stripe /tmp/expo-ref/with-stripe   # clean copy, no git history
+# fallback without degit (sparse-checkout, no full ~64 MB clone):
+git clone --depth 1 --filter=blob:none --sparse https://github.com/expo/examples.git /tmp/expo-ref/examples \
+  && (cd /tmp/expo-ref/examples && git sparse-checkout set with-stripe)
+```
+
+Read from there with Grep/Read; delete the scratch dir when done.
+
+### 2b. Scaffold mode — new project from an example
+
+```bash
+npx create-expo --example with-stripe   # short form:  npx create-expo -e with-stripe
+bun create expo --example with-stripe    # with bun
+```
+
+### 3. Adapt into the user's app — non-destructively (critical)
+
+When the user already has an app, **add only what the example introduces; never overwrite their setup.**
+
+- **Version-align — don't copy pinned versions.** Examples track the **latest** SDK, so their `package.json` pins won't match an older project. Add only the *missing* deps with `npx expo install <pkg>` (it resolves SDK-correct versions) instead of copying exact versions.
+- **Merge config, don't replace it.** Add only the `app.json`/`app.config.*` plugins and permissions the example introduces that the user lacks — keep their existing config block intact.
+- **Port the integration code.**
+- **Recreate env vars** from the example's `.env` shape — it holds placeholders, never working secrets.
+
+**Done when** the integration code is ported and every dependency, config plugin, permission, and env var it needs is accounted for in the user's app — not when it merely *looks* wired up.
+
+## Gotchas
+
+- **Default branch is `master`,** not `main` (matters for raw URLs and sparse checkout).
+- **Single-click deploy.** Every example has a launch URL: `https://launch.expo.dev/?github=https://github.com/expo/examples/tree/master/<example>`.
+
+## Related skills
+
+- Tailwind / NativeWind styling → `expo-tailwind-setup`
+- Native UI components → `building-native-ui`
+- Authoring a native module → `expo-module`
+- Upgrade the SDK before adopting a latest-SDK example → `upgrading-expo`
+
+## References
+
+- `./references/catalog.md` — categorized snapshot of the example library for fast triage.
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream product or API scope.
+- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
+- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/expo-examples/references/catalog.md

@@ -0,0 +1,105 @@
+# Example catalog (snapshot)
+
+A categorized view of [expo/examples](https://github.com/expo/examples) for fast triage. Each entry is a **single-concern integration demo** (one library/service, managed project, usually one screen) — not a full app. This snapshot drifts — the **live repo is the source of truth**. Confirm the exact name against `gh api repos/expo/examples/contents` and check `meta.json` for aliases/deprecations (see SKILL.md step 1) before recommending or scaffolding.
+
+Use any name with `npx create-expo --example <name>` (scaffold) or inspect it via `gh api repos/expo/examples/contents/<name>/<file>`.
+
+Most are single-screen integrations; a few differ:
+
+- **Full-stack** (include Expo Router `+api` routes — a backend too): `with-stripe`, `with-clerk`, `with-better-auth`, `with-openai`, `with-router-ai`, `with-graphql`, `with-s3`, `with-satori`.
+- **Larger showcases:** `with-shadcn`, `with-router-tv`, `with-router-menus`, `with-react-navigation`, `with-webgpu`.
+- **Starters (not integrations):** `blank`, `stickersmash`.
+
+## Auth & identity
+- `with-clerk` — Clerk authentication
+- `with-auth0` — Auth0 login
+- `with-better-auth` — Better Auth
+- `with-magic` — Magic passwordless auth
+- `with-facebook-auth` — Facebook login
+- `with-firebase-saml-login` — Firebase SAML SSO
+
+## Payments
+- `with-stripe` — Stripe payments (native + web)
+
+## Backend, data & storage
+- `with-convex` — Convex realtime backend
+- `with-legend-state-supabase` — Supabase + Legend-State sync
+- `with-firebase-storage-upload` — Firebase Storage uploads
+- `with-aws-storage-upload`, `with-s3` — AWS / S3 file uploads
+- `with-apollo`, `with-graphql` — GraphQL clients
+- `with-formdata-image-upload` — multipart image upload
+
+## Local database & state
+- `with-sqlite` — expo-sqlite
+- `with-libsql` — libSQL / Turso
+- `with-tinybase` — TinyBase local-first store
+- `with-zustand` — Zustand state management
+
+## Navigation & routing
+- `with-router` — Expo Router basics
+- `with-react-navigation` — React Navigation (stacks + tabs)
+- `with-drawer-navigation` — drawer navigator
+- `with-router-menus` — native context menus with Router
+- `with-router-uniwind` — Router + Uniwind styling
+- `with-router-ai` — Router + AI chat UI
+- `with-router-tv` — Router on TV
+- `with-react-router` — React Router (web)
+
+## Styling & UI
+- `with-tailwindcss` — Tailwind / NativeWind (see also `expo-tailwind-setup` skill)
+- `with-styled-components` — styled-components
+- `with-shadcn` — shadcn-style components
+- `with-moti` — Moti animations
+- `with-custom-font` — custom fonts
+- `with-svg` — react-native-svg
+- `with-icons` — icon sets
+- `with-splash-screen` — custom splash screen
+- `with-video-background` — full-screen video background
+
+## Animation & graphics
+- `with-reanimated` — Reanimated
+- `with-skia` — React Native Skia 2D graphics
+- `with-three`, `with-react-three-fiber` — three.js / R3F 3D
+- `with-webgpu` — WebGPU
+- `with-processing` — Processing-style sketches
+- `with-react-flow` — node/flow diagrams
+- `with-victory-native` — charts
+
+## AI & ML
+- `with-openai` — OpenAI API
+- `with-router-ai` — AI chat app with Expo Router
+- `with-google-vision` — Google Cloud Vision
+- `with-tfjs-camera` — TensorFlow.js on the camera
+
+## Media & device
+- `with-camera` — expo-camera
+- `with-maps` — react-native-maps
+- `with-webrtc` — WebRTC
+- `with-pdf` — render / view PDFs
+
+## Web & rendering
+- `with-nextjs` — Next.js + Expo
+- `with-rsc` — React Server Components
+- `with-react-strict-dom` — React Strict DOM
+- `with-react-compiler` — React Compiler
+- `with-html` — render raw HTML
+- `with-satori` — OG image generation with Satori
+- `with-workbox` — service worker / PWA
+- `with-webbrowser-redirect` — expo-web-browser auth redirect
+
+## Platform: TV, widgets
+- `with-tv` — Apple TV / Android TV
+- `with-widgets` — iOS / Android home-screen widgets
+
+## Tooling, testing & monorepo
+- `with-typescript` — TypeScript baseline
+- `with-yarn-workspaces` — Yarn monorepo
+- `with-storybook` — Storybook
+- `with-maestro` — Maestro E2E tests
+- `with-sentry` — Sentry error monitoring
+- `with-socket-io` — Socket.IO realtime
+- `with-github-remote-build-cache-provider` — remote build cache on GitHub
+
+## Starters
+- `blank` — minimal app
+- `stickersmash` — the tutorial app

package/bundled-skills/expo-module/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: expo-module
+description: Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules...
+risk: unknown
+source: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-module
+source_repo: expo/skills
+source_type: official
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/expo/skills/blob/main/LICENSE
+---
+
+# Writing Expo Modules
+
+Complete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript.
+
+## When to Use
+
+- Creating a new Expo native module or native view
+- Adding native functionality (camera, sensors, system APIs) to an Expo app
+- Wrapping platform SDKs for React Native consumption
+- Building config plugins that modify native project files
+- Adding Android, Apple, or web support to an existing Expo module
+- Editing `expo-module.config.json`, config plugins, or lifecycle hooks
+
+## References
+
+Consult these resources as needed:
+
+```
+references/
+  create-expo-module.md      Scaffolding and add-platform-support workflow, defaults, and quirks
+  native-module.md           Module definition DSL: Name, Function, AsyncFunction, Property, Constant, Events, type system, shared objects
+  native-view.md             Native view components: View, Prop, EventDispatcher, view lifecycle, ref-based functions
+  lifecycle.md               Lifecycle hooks: module, iOS app/AppDelegate, Android activity/application listeners
+  config-plugin.md           Config plugins: modifying Info.plist, AndroidManifest.xml, reading values in native code
+  module-config.md           expo-module.config.json fields, file placement, and autolinking behavior
+```
+
+## Quick Start
+
+Prefer `create-expo-module` over manually creating native module files and directories. In practice, the best path is usually to create the scaffold first and then build on top of it. The scaffold sets up the expected layout, `expo-module.config.json`, podspec or Gradle files, TypeScript bindings, and the standalone example app flow.
+
+If an existing Expo module only needs another platform, use `create-expo-module add-platform-support` instead of manually copying native directories.
+
+See [references/create-expo-module.md](references/create-expo-module.md) before scaffolding or extending a module. It covers:
+
+- local vs standalone modules
+- `--platform`, `--features`, `--barrel`, `--package-manager`, and non-interactive mode
+- `expo.autolinking.nativeModulesDir`
+- `add-platform-support` behavior and quirks
+
+## Recommended Workflow
+
+1. Choose the scaffold type first:
+   - **Local module** for one app
+   - **Standalone module** for reuse, monorepos, or publishing
+2. Determine native `expo-module` features that you will need.
+   - Based on the user's instructions determine which feature scaffolding will be useful.
+   - Available features: `Constant`, `Function`, `AsyncFunction`, `Event`, `View`, `ViewEvent`, `SharedObject`
+3. Scaffold deliberately:
+   - pass an explicit slug or path
+   - choose `--platform` intentionally instead of relying on defaults
+   - use `--features` to choose code samples which you will modify in the next step to match the real implementation.
+4. Replace generated example code with the real implementation.
+5. If you add a new platform later, prefer `add-platform-support` over manual file copying.
+
+## Practical Scaffolding Rules
+
+- Feature examples are **opt-in**. A newly scaffolded module may be minimal if no features were selected.
+- `ViewEvent` implies `View`.
+- Local modules do **not** generate an `index.ts` barrel by default. Use `--barrel` only if you want one.
+- In non-interactive local scaffolding, pass the positional slug or path explicitly. `--name` changes the native class name, not the folder name.
+- Local modules live in `expo.autolinking.nativeModulesDir` when configured, otherwise in `modules/`.
+- Standalone modules have their own package metadata, scripts, and usually an example app. Local modules use the host app's tooling instead.
+
+## Core File Shapes
+
+The Swift and Kotlin DSL share the same structure. Swift is usually the clearest primary example; consult the references for feature-specific details.
+
+## Module Structure Reference
+
+The Swift and Kotlin DSL share the same structure. Both platforms are shown here for reference — in other reference files, Swift is shown as the primary language unless the Kotlin pattern meaningfully differs.
+
+**Swift (iOS):**
+
+```swift
+import ExpoModulesCore
+
+public class MyModule: Module {
+  public func definition() -> ModuleDefinition {
+    Name("MyModule")
+
+    Function("hello") { (name: String) -> String in
+      return "Hello \(name)!"
+    }
+  }
+}
+```
+
+**Kotlin (Android):**
+
+```kotlin
+package expo.modules.mymodule
+
+import expo.modules.kotlin.modules.Module
+import expo.modules.kotlin.modules.ModuleDefinition
+
+class MyModule : Module() {
+  override fun definition() = ModuleDefinition {
+    Name("MyModule")
+
+    Function("hello") { name: String ->
+      "Hello $name!"
+    }
+  }
+}
+```
+
+**TypeScript:**
+
+```typescript
+import { requireNativeModule } from "expo";
+
+const MyModule = requireNativeModule("MyModule");
+
+export function hello(name: string): string {
+  return MyModule.hello(name);
+}
+```
+
+### expo-module.config.json
+
+```json
+{
+  "platforms": ["android", "apple"],
+  "apple": {
+    "modules": ["MyModule"]
+  },
+  "android": {
+    "modules": ["expo.modules.mymodule.MyModule"]
+  }
+}
+```
+
+Note: iOS uses just the class name; Android uses the fully-qualified class name (package + class). See `references/module-config.md` for all fields.
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream product or API scope.
+- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
+- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/expo-module/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Module"
+  short_description: "Build Expo native modules and native views with Swift, Kotlin, TypeScript, autolinking, and config plugins"
+  default_prompt: "Use $expo-module to scaffold, implement, clean up, or review Expo native modules, native views, shared objects, lifecycle hooks, autolinking configuration, and config plugins."