Builds, integrates, migrates, and audits Stream Chat, Stream Video, and Stream Feeds in React Native CLI and Expo apps. Use when scaffolding a new RN/Expo Chat, Video, or Feeds app, adding Stream to an existing RN app, upgrading a Stream SDK version (stream-chat-react-native v8 to v9, Feeds v2 to v3

Stream React Native skill router + execution flow Rules: Read [ RULES.md ](RULES.md) once per session. Every non negotiable React Native Chat, Video, and Feeds rule is stated there. This file is the single entrypoint: intent classification, product selection, project detection, and module pointers for Stream Chat React Native, Stream Video React Native, and Stream Feeds React Native work. Step 0: Intent classifier (mandatory first never skip) Before any tool call, decide the track from the user's input alone. Do not probe the filesystem first. Signals track Signal in user input Track "Build/create/scaffold a new React Native app", "create an Expo app", "new Stream Chat RN app", "new Stream Video RN app", "new Stream Feeds RN app", empty directory + React Native/Expo Chat / Video / Feeds A New app "Upgrade/migrate/bump a Stream SDK version", "upgrade stream chat react native to v9", "migrate Chat RN to the new SDK", "v8 to v9", "bump Stream Video/Feeds", "Feeds v2 v3" M Migrate / upgrade "Migrate from Sendbird", "replace Sendbird with Stream", "we're switching off Sendbird", "rip out @sendbird/uikit react native", "convert SendbirdUIKitContainer / createGroupChannelFragment to Stream", @sendbird/chat / @sendbird/uikit react native / foundation present in the target's package.json S Migrate from Sendbird "Add/integrate Stream Chat into this app", "wire Chat RN", "set up stream chat expo", "add a video call", "wire Stream Video", "set up @stream io/video react native sdk", "add an activity feed", "wire Stream Feeds", "set up @stream io/feeds react native sdk", "change/customize this Chat / Video / Feeds UI" B Existing app React Native , Expo , Expo Router , stream chat react native , stream chat expo , @stream io/video react native sdk , @stream io/feeds react native sdk , Stream Chat RN , Stream Video RN , Stream Feeds RN , Chat React Native , Video React Native , Feeds React Native , migration C Reference lookup if the user only asks how/docs; otherwise B Existing app Explicit product/runtime token: Chat React Native , Chat Expo , Video React Native , Video Expo , Feeds React Native , Feeds Expo C Reference lookup Words "docs" or "documentation" around Stream Chat, Stream Video, or Stream Feeds React Native / Expo work C Reference lookup "How do I {X} in React Native/Expo?", "What does {SDK component/hook/prop} do?" C Reference lookup "Audit/review/check an existing Stream Video integration against best practices", "is my video app production ready?", "what am I missing before launch?" C Reference lookup (read only) run the Integration best practices audit in [ references/VIDEO REACT NATIVE.md ](references/VIDEO REACT NATIVE.md) "Install Stream packages", "set up Chat RN", "set up Video RN", "set up Feeds RN", "wire auth/token flow" with no broader feature request D Bootstrap / setup Stream Moderation review UI or any other non Chat / non Video / non Feeds Stream RN product Reject bundled scope and route to live docs only if the user wants docs Bare /stream react native with no args List the tracks briefly and wait Disambiguation flow If the request is ambiguous between wiring code and reference lookup, ask one short question and wait: Do you want me to wire this into the project, or just map the React Native SDK pattern and files? If the user wants a new app but did not name Expo or RN CLI, default to Expo because it is the shortest successful path. Use RN CLI when the user asks for it or when native project constraints require it. Product classifier (after track is known) Identify the product from the user's input or detected packages. Tracks A, B, and D all need the product before continuing; Track C selects the matching reference pair. Product signal Product References stream chat react native , stream chat expo , channel, message, MessageComposer, thread, attachment, offline support Chat [ references/CHAT REACT NATIVE.md ](references/CHAT REACT NATIVE.md) + [ references/CHAT REACT NATIVE blueprints.md ](references/CHAT REACT NATIVE blueprints.md) @stream io/video react native sdk , video call, livestream, audio room, ringing, CallContent, ParticipantView, screenshare, picture in picture Video [ references/VIDEO REACT NATIVE.md ](references/VIDEO REACT NATIVE.md) + [ references/VIDEO REACT NATIVE blueprints.md ](references/VIDEO REACT NATIVE blueprints.md) @stream io/feeds react native sdk , useCreateFeedsClient , StreamFeeds , StreamFeed , activity feed, timeline feed, notification feed, for you feed, useFeedActivities , useActivityComments , reactions, comments, follows, follow / unfollow, activity composer, activityWithStateUpdates Feeds [ references/FEEDS REACT NATIVE.md ](references/FEEDS REACT NATIVE.md) + [ references/FEEDS REACT NATIVE blueprints.md ](references/FEEDS REACT NATIVE blueprints.md) Two or more products in one app (chat alongside a video call, feeds + chat, feeds + video, etc.) Combined Load only the reference pairs for the products in scope. Nest the providers (e.g. <StreamVideo inside <OverlayProvider <Chat inside <StreamFeeds ); do not place them as siblings. See [ RULES.md ](RULES.md) and the manifest selected /video/docs/react native/advanced/chat with video.md for the Chat + Video interop notes If the request is ambiguous between products, ask one short question and wait: Are you wiring Stream Chat (channels, messages), Stream Video (calls, livestream, audio rooms), or Stream Feeds (activity feed, timeline, comments, reactions, follows)? Or more than one in the same app? Scope rejection This skill bundles Chat, Video, and Feeds React Native . If the user asks for Stream Moderation review UI or another non bundled Stream RN product, say: The React Native skill currently bundles Chat, Video, and Feeds references. I can help with any combination of those here, or switch to live docs for other products. Do not invent missing React Native Moderation API details from memory. After classification Tracks A, B, D run Project signals, then continue in [ builder.md ](builder.md) and [ sdk.md ](sdk.md). Run [ credentials.md ](credentials.md) before writing Chat, Video, or Feeds connection code or creating requested demo data. Track M Read [ migrate.md ](migrate.md) first; it fetches the live upgrade guide before any edit. Run Project signals for lane / package manager / New Architecture detection, but skip credentials, provisioning, and the scaffold path it edits an existing project. Track S Read [ sendbird migration.md ](sendbird migration.md) first; it detects the Sendbird integration shape (and the Expo vs bare flavor) before any edit. Run Project signals for lane / package manager / New Architecture detection, but do not enter Track A/B/D or any scaffold path it re implements an existing Sendbird integration in place. Track C skip credentials and project probes if the product + runtime are explicit. Only run a read only probe if RN CLI vs Expo is ambiguous and the answer affects the guidance. Step 0.5: Credentials, token, and demo data (tracks A, B, D only) Use [ credentials.md ](credentials.md) once per session before writing code that connects to Stream Chat, Stream Video, or Stream Feeds. It resolves: Stream API key user id and display name user token or token provider plan optional demo data, only when requested, via Stream CLI calls (Chat: UpdateUsers , GetOrCreateChannel , SendMessage ; Video and Feeds do not require seed data because calls are ephemeral and activities can be posted at runtime) For Track A, it is acceptable to scaffold the app first if the runtime or target directory must be resolved before credentials. Do not render a connected Chat, Video, or Feeds UI until credentials or a token provider plan are resolved. Project signals (tracks A/B/D once per session; Track C on demand only) Read only local probe. Use it to detect empty/new workspace, RN CLI vs Expo, New Architecture hints, navigation setup, and existing Stream packages. Hold the result in conversation context. Do not re run unless the user changes directory, packages are installed, or the project shape changes. Use the result to produce a one line status, for example: Empty workspace detected defaulting to Expo new app unless the user asked for RN CLI Expo app detected stream chat expo absent Expo Router present ready for Chat setup Expo app detected Expo SDK 56+ apply RULES.md Expo Router SDK 56+ rule (no @react navigation/ ) ⚠️ react native reanimated 4.5.0 + react native worklets 0.10.0 detected — known crash pair (Expo SDK 57 pin); bump to ≥4.5.1/≥0.10.2 and rebuild native (RULES.md Required peer setup) Expo app detected @stream io/video react native sdk absent ready for Video setup Expo app detected @stream io/feeds react native sdk absent ready for Feeds setup RN CLI app detected ios/android present stream chat react native installed checking provider placement RN CLI app detected both @stream io/video react native sdk and stream chat react native installed Chat + Video interop applies Expo app detected @stream io/feeds react native sdk and stream chat expo installed nest StreamFeeds + Chat providers (no sibling mounts) No RN/Expo app detected in a non empty directory create a new app in a child directory or ask before reusing this directory If there is no RN/Expo project and Track A applies, scaffold one through [ builder.md ](builder.md) 2. New app scaffold . If Track B/D applies in a non RN directory, ask before creating a child app because that changes project ownership. Module map Track Module(s) A New app [ builder.md ](builder.md) + [ sdk.md ](sdk.md) + llms.txt docs lookup + product references (Chat / Video / Feeds) B Existing app [ builder.md ](builder.md) + [ sdk.md ](sdk.md) + llms.txt docs lookup + product references (Chat / Video / Feeds) C Reference lookup [ sdk.md ](sdk.md) + [ references/DOCS.md ](references/DOCS.md) + relevant product reference files D Bootstrap / setup [ builder.md ](builder.md) + [ sdk.md ](sdk.md) + llms.txt docs lookup M Migrate / upgrade [ migrate.md ](migrate.md) + [ references/DOCS.md ](references/DOCS.md) (live upgrade guide) + product reference for the migrated SDK S Migrate from Sendbird [ sendbird migration.md ](sendbird migration.md) + [ references/sendbird notes.md ](references/sendbird notes.md) + [ references/sendbird symbols.tsv ](references/sendbird symbols.tsv) + [ references/design matching.md ](references/design matching.md) + [ credentials.md ](credentials.md) + [ references/CHAT REACT NATIVE.md ](references/CHAT REACT NATIVE.md) Reference layout Shared React Native and Expo patterns live in [ sdk.md ](sdk.md) . Product specific setup, docs lookup, gotchas, and UI blueprints live under references/ : llms.txt docs lookup (Chat, Video, Feeds): [ references/DOCS.md ](references/DOCS.md) Chat setup/reference: [ references/CHAT REACT NATIVE.md ](references/CHAT REACT NATIVE.md) Chat screen/component blueprints: [ references/CHAT REACT NATIVE blueprints.md ](references/CHAT REACT NATIVE blueprints.md) Video setup/reference: [ references/VIDEO REACT NATIVE.md ](references/VIDEO REACT NATIVE.md) Video screen/component blueprints: [ references/VIDEO REACT NATIVE blueprints.md ](references/VIDEO REACT NATIVE blueprints.md) Feeds setup/reference: [ references/FEEDS REACT NATIVE.md ](references/FEEDS REACT NATIVE.md) Feeds screen/component blueprints: [ references/FEEDS REACT NATIVE blueprints.md ](references/FEEDS REACT NATIVE blueprints.md) iOS simulator verification (fast run/s

stream-react-native