Stream Flutter

Stream Flutter - skill router + execution flow

Rules: Read RULES.md once per session - every non-negotiable rule is stated there, nowhere else.

This file is the single entrypoint: intent classification, local project detection, and module pointers for Stream work in Flutter apps.

Step 0: Intent classifier (mandatory first - never skip)

Before any tool call, decide the track from the user's input alone - no probes first.

Signals -> track

Styling-depth flag (orthogonal to Tracks A/B/C/D)

If the request carries a target appearance — an attached screenshot, a Figma frame, or "make it look like WhatsApp / iMessage / Telegram / Slack / " — then before feature work (Track A or B), first run the strategy decision below (components vs custom):

• Components → run design-matching.md: read its procedure half in full — everything above the # Reference divider (Steps 1–5; it may span two Reads, so page past a mid-procedure truncation) — then Grep its Reference half per region while implementing.
• Custom (livestream / overlay / bespoke) → run custom-ui.md instead — same region-by-region rigor, different mechanism.

The rest of this section is the components case (the common one). A reference design is a checklist of regions (header, composer buttons, where the timestamp + read receipts sit, bubble shape/tail, date separators, attachments...), and most of them differ from Stream's defaults structurally, not just by color. Do not stop at the wallpaper and bubble color — that is the known failure mode. Decompose every region first (capturing its dimensions, not just colors), then route each to one of two axes:

1. Theming — StreamTheme (a ThemeExtension on MaterialApp.theme.extensions) owns design foundations (spacing / radius / typography / colors) and all fine-grained/leaf styling including the whole message row (messageItemTheme bubble/text/attachment/metadata, reactionsTheme, reactionPickerTheme, avatarTheme, textInputTheme, mediaViewerTheme, …), while StreamChatThemeData (passed to StreamChat(themeData:)) owns only the chat composite-widget slots (the three headers, message-list background/wallpaper, channel-list item, quoted message, thread tile, poll themes).
2. Widget replacement — the component factory, populated via core named slots on StreamComponentBuilders(...) (48 leaf slots: messageBubble, messageText, reactions, reactionPicker, mediaViewer, jumpToUnreadButton, textInput, avatar, …) and chat slots via streamChatComponentBuilders(...) → extensions: (30 composite slots: messageItem, messageComposer + sub-slots, channelListItem, per-attachment builders, …), passed to StreamChat(componentBuilders: StreamComponentBuilders(...)) (global) or StreamComponentFactory(builders: …, child: …) (scoped); plus per-widget builders (messageBuilder, itemBuilder) for a single instance.

Recurring traps the doc guards against:

• (a) overriding a composite widget (messageItem builder, messageComposer builder, messageBuilder on StreamMessageListView) silently drops the sub-features the default rendered — the incoming-message avatar, grouping, reactions, replies, status, or the send/voice/edit/slow-mode button — unless you read the default's build() and reproduce them (grouping state is available inside a custom messageItem via StreamMessageLayout.of(context));
• (b) model-driven title logic must live in one shared helper used by both the channel list itemBuilder and the header, so the two surfaces cannot diverge;
• (c) route deliberately — bubble padding / color / shape live on StreamTheme (StreamTheme.messageItemTheme.bubble); structural changes (send button outside the field, metadata inside the bubble, a bubble tail, a Slack-style flat row) need widget replacement (component factory or a per-widget builder).

The match is not done until you run, seed data that triggers every region, compare region-by-region against the reference on the real navigation path, and iterate (design-matching.md Step 5), deleting any throwaway verification scaffold — the UI must be as close to the reference as possible, not approximately like it. Implement every region, the composer included — never deliver a partial match with the rest labelled "known cosmetic gaps"; a region left at the SDK default is a FAIL, not a footnote. And work in batches: ground the pinned SDK version + local checkout once, read the source you need in one pass, implement all regions, then verify once on hot reload — don't rebuild-and-screenshot after every small edit.

Chat only: pick the UI strategy first (before any code)

Stream Chat ships two layers, and choosing between them is an architecture decision that dwarfs any styling choice — getting it wrong wastes a day either way. So decide deliberately, and default to the pre-built components:

Lean hard toward components. They're built to be customized, and the litmus test is: if the two axes — theming (StreamTheme + StreamChatThemeData) + a few component-builder slots — could get there, it's a components job — even strong messenger reskins. Pick custom only when matching the design would mean replacing the message row, composer, header, AND list all at once — i.e. you'd be using the SDK purely as a data source, not for any of its widgets. Over-choosing custom (rebuilding a worse messenger by hand, losing avatars/grouping/reactions/threads/attachments/typing/receipts/pickers) is the common, expensive mistake; over-choosing components costs a few hours of fighting layout. When unsure, build the components version first — it's faster to confirm-or-reject. And treat "livestream" / "live-shopping" as signals, not labels: they point to custom only when the shape matches (flat identical rows, overlay/ticker, high volume, read-only viewers) — a livestream app that wants a normal bubble/channel-list chat panel stays on components. This is the full decision rubric; custom-ui.md is the build runbook you follow after the decision lands on custom, not a doc you open to decide.

Workplace / Slack-style hybrid is a components job too. A Slack/Teams/Discord surface is a channel list + message list + composer, so it stays on the pre-built components — but two things differ from a messenger and must be matched, not punted: (1) the message row is flat and left-aligned (avatar-top rounded-square, an author·custom-status·timestamp header line, body, bottom reaction pills, and a thread-reply summary), with no incoming/outgoing bubble split — reproduce it by overriding the messageItem component builder (a composite slot — reproduce its sub-features); (2) the header and chrome are custom. The full workplace archetype is in design-matching.md. Workplace apps are also thread-first, so wire the thread-reply summary and thread screen.

The strategy also picks the channel type and permission model (e.g. messaging membership-gated for social/marketplace vs livestream public + anonymous viewers) — see RULES.md → "Surface permission prerequisites proactively", and Step 0.5 → "Permissions awareness". Decide both axes together.

If it's genuinely unclear, ask one question:

Does this chat look like a standard messenger (channel list + bubbles), or a bespoke surface like livestream/overlay chat? It decides whether we customize the pre-built components or build custom UI on stream_chat_flutter_core.

Disambiguation flow

If the request is ambiguous between build/integrate and reference lookup, ask one short question and wait:

Do you want me to wire this into the project, or just map the Flutter SDK pattern and widgets?

After classification

• Tracks A, B, D -> run Project signals once per session, then continue in builder.md and sdk.md. If the styling-depth flag was raised, run the design-match phase alongside per the UI-strategy decision — design-matching.md for the pre-built components (the common case; read its procedure half in full — everything above the # Reference divider, which may span two Reads — then Grep its Reference half per region) or custom-ui.md for a bespoke stream_chat_flutter_core surface (design-match rigor is a mandatory phase, not an optional add-on).
• Track C -> skip the probe if the product + package are explicit. Only run it on demand if the SDK layer is ambiguous.
• Track M -> run sendbird-migration.md: detect the existing Sendbird integration shape, swap packages/init/views/channels/messages, re-apply theming via the two axes, and verify design + functional fidelity per screen against the Sendbird original. Reuses Step 0.5 credentials and design-matching.md/custom-ui.md rigor; hands off to the shared data-migration runbook when the code migration is done.

Step 0.5: Credentials, token, and seed data (tracks A, B, D — and Track M at phase M2)

Run this once per session, right after intent classification, before the Project signals probe.

Goal

Collect the Stream API key, a user token, and optionally seed channels or calls - all before touching code - so the app has real data to show from the first run.

Single upfront question (ask exactly once, then act immediately)

Post one message asking all relevant things together. Do not split into multiple rounds.

For Chat projects:

To wire everything up with real data, I need a few quick answers:

1. Credentials - Should I fetch your API key from the dashboard and generate a token via the Stream CLI, or will you paste them yourself?
2. Token expiry - If I'm generating the token: should it expire? (e.g. 1h, 1d, 30m) or never expire?
3. Seed channels - Should I pre-create a few channels with random usernames so the app has something to show immediately?

If you want to handle everything yourself, just paste your API key and token and tell me whether to seed channels.

For Video projects (calls are ephemeral - no seeding needed):

To wire everything up, I need a couple of quick answers:

1. Credentials - Should I fetch your API key from the dashboard and generate a token via the Stream CLI, or will you paste them yourself?
2. Token expiry - If I'm generating the token: should it expire? (e.g. 1h, 1d, 30m) or never expire?

If you want to handle everything yourself, just paste your API key and token.

Guest-viewer requirement — surface this BEFORE building any app that signs viewers in as guests. A guest connects with the guest role, which by default has minimal capabilities. On the livestream call type guests cannot even read or join a call until the integrator grants those capabilities to the guest role. When a guest-based viewer flow is in scope, tell the integrator it is a prerequisite to grant the guest role read-call and join-call (plus create-call if a viewer may open the call before the host) on the relevant call type via Stream Dashboard → Video & Audio → Call Types → → Roles & Permissions (or the API), or to use authenticated User.regular viewers instead. Details: references/VIDEO-FLUTTER.md → Guest users, and references/LIVESTREAM-FLUTTER.md → Roles, permissions, and backstage security.

For Feeds projects (no pre-built UI; feed groups required):

Ask one message with all setup questions together — do not split into rounds:

To wire everything up, I need a few quick answers:

1. Credentials - Should I fetch your API key from the dashboard and generate a token via the Stream CLI, or will you paste them yourself?
2. Token expiry - If I'm generating the token: should it expire? (e.g. 1h, 1d, 30m) or never expire?
3. Feed groups - I need to create 3 feed groups in your Stream project (user, timeline, notification). Should I set these up automatically, or have you already created them?
4. Seed posts - Should I add a few sample posts so the feed has content from the first run?

If you want to handle credentials yourself, just paste your API key and token.

Once the user replies, execute all steps without pausing. For feed groups, if the user said "set up automatically":

getstream api CreateFeedGroup --request '{"id": "user", "type": "flat"}'
getstream api CreateFeedGroup --request '{"id": "timeline", "type": "flat"}'
getstream api CreateFeedGroup --request '{"id": "notification", "type": "notification"}'

If the CLI commands fail (the Feeds API may use different endpoints than Chat), tell the user once:

Please create these in Stream Dashboard → Activity Feeds → Feed Groups: user (Flat), timeline (Flat), notification (Notification).

For Feeds projects, always generate two separate helpers in main after connect():

1. _setupFollows(client) — always called, unconditionally. Makes timeline follow user so the user's own posts appear there. Do not merge this into seed logic — once seed data exists the guard returns early and the follow call never runs.
2. _seedPosts(client) — only if the user said yes to seeding. Adds sample activities and exits early if data already exists.

See references/FEEDS-FLUTTER.md for both implementations.

The package is stream_feeds: ^0.5.1 — not the deprecated stream_feed or stream_feed_flutter_core.

After the user replies - act without further prompting

Once the user answers, execute all CLI steps in sequence without pausing for confirmation between them. Narrate each step briefly as you go (one line per action), but do not stop to ask "shall I continue?".

Step A - API key

getstream env --target flutter

This writes the public API key to dart_defines.json; the app reads it via String.fromEnvironment('STREAM_API_KEY') and is run with flutter run --dart-define-from-file=dart_defines.json. If the command returns a 401 error, the CLI session has expired - run getstream login to re-authenticate, then retry.

If getstream is not installed (command not found): ask the user to install it from https://getstream.io and wait. Or, if the user prefers, skip the CLI entirely and have them paste the API key + a token per user (Dashboard -> Explorer has a token generator). Decide based on the user's answer to the upfront credentials question; don't stall.

Step B - Token

# Never-expiring
getstream token <user_id>

# Expiring
getstream token <user_id> --ttl <duration>

Hold the token in context. Use it (and the API key) in every code snippet - no placeholder strings.

Step C - Seed channels (only if the user said yes)

Create 3-5 channels with random realistic usernames. Use messaging as the default channel type.

Sub-step C1 — upsert all users (seed users + the token user):

getstream api UpdateUsers --request '{
  "users": {
    "<token_user_id>": {"id": "<token_user_id>", "name": "<Display Name>"},
    "alice": {"id": "alice", "name": "Alice"},
    "bob":   {"id": "bob",   "name": "Bob"},
    "carol": {"id": "carol", "name": "Carol"},
    "dave":  {"id": "dave",  "name": "Dave"}
  }
}'

Sub-step C2 — create each channel (no members in the body; members are added in C3):

getstream api GetOrCreateChannel --type messaging --id <channel-id> \
  --request '{"data": {"created_by_id": "<token_user_id>", "custom": {"name": "<Channel Name>"}}}'

Repeat for each channel (e.g. general, random, team-alpha).

Sub-step C3 — add members to each channel using add_members. The token user must be in every channel so the Filter.in_('members', [userId]) query in the app returns results.

getstream api UpdateChannel --type messaging --id <channel-id> \
  --request '{
    "add_members": [
      {"user_id": "<token_user_id>"},
      {"user_id": "alice"},
      {"user_id": "bob"}
    ],
    "user_id": "<token_user_id>"
  }'

Generate short memorable channel IDs (e.g. general, random, team-alpha) and use a small set of random usernames (e.g. alice, bob, carol, dave). The token user must be added to every channel — the channel list filter is Filter.in_('members', [tokenUserId]) and will return nothing if the user is absent.

Sub-step C4 — seed messages. Attribute the sender server-side with message.user_id. Send a couple per channel so the list shows previews and the channel screen isn't empty; set an explicit message.id on anything you want to reply to, so a threaded reply can reference it without parsing a response.

getstream api SendMessage --type messaging --id <channel-id> \
  --request '{"message":{"id":"<channel-id>-m1","user_id":"alice","text":"Morning - anyone up for a sync today?"}}'

# Threaded reply into that message
getstream api SendMessage --type messaging --id <channel-id> \
  --request '{"message":{"user_id":"bob","text":"I will bring the numbers","parent_id":"<channel-id>-m1"}}'

After seeding, print a brief summary:

Created channels: general (token_user, alice, bob), random (token_user, carol, dave), team-alpha (token_user, alice, carol)

Step D - Proceed automatically

After all CLI steps succeed, continue without pausing - no additional prompt needed: tracks A/B/D move straight to Project signals and then into builder.md; Track M returns to sendbird-migration.md (phase M2). If any CLI step fails, explain the error briefly and ask the user to paste the missing value manually before continuing.

What NOT to do

• Never put the API secret in app code - the CLI uses it server-side only.
• Never invent or fabricate credentials.
• Never ask "should I continue?" between Step A, B, C, and D - execute the whole sequence once the user's upfront answers are in.

Permissions awareness (Chat - surface proactively)

Stream Chat checks permissions per role, per scope on every client-side call — but server-side calls (the CLI and your backend, using the API secret) bypass all checks. That asymmetry is the #1 source of "it worked when you seeded it, but the app 403s": seeding channels via the CLI succeeds regardless of grants, then the same query/join from the app hits the connected user's role and fails.

When the app you're about to build does anything beyond chatting inside channels the user is already a member of, tell the integrator about the relevant grants before writing the feature — don't wait for a runtime 403. Map the scenario to the grant:

guest users (name-only / no-backend sign-in) are stricter than user — if the app uses guest auth, the same grants must be added to the guest role too. Point the integrator to Dashboard → Chat → Roles & Permissions (permissions v2) for the role + messaging type, or UpdateChannelType via API/CLI. Full detail and the exact error string: references/CHAT-FLUTTER.md → Channel permissions & roles (custom-UI builds: references/CHAT-CORE.md).

This is a prompt, not a blocker — build the feature as requested, but call out the prerequisite in the same turn so discover/join/create don't silently fail on first run.

Project signals (tracks A/B/D/M - once per session; Track C on demand only)

Read-only local probe. Use it to detect whether the user is in a Flutter project or an empty directory.

bash -c 'echo "=== FLUTTER ==="; find . -maxdepth 2 -name "pubspec.yaml" -print 2>/dev/null; echo "=== STREAM ==="; grep -rE "stream_chat|stream_video|stream_feed" . --include="pubspec.yaml" -l 2>/dev/null; echo "=== EMPTY ==="; test -z "$(ls -A 2>/dev/null)" && echo "EMPTY_CWD" || echo "NON_EMPTY"'

Hold the result in conversation context. Don't re-run it unless the user changes directory or the project shape clearly changed.

Use the result to produce a one-line status, for example:

• Flutter app detected - stream_chat_flutter already in pubspec.yaml
• Flutter app detected - stream_video_flutter already in pubspec.yaml
• Flutter app detected - stream_feed already in pubspec.yaml
• Flutter app detected - no Stream dependency yet, ready to install
• No Flutter project found - empty directory

Version prerequisite (Chat - existing project)

When a Stream Chat dependency is already present, check the resolved version (pubspec.yaml constraint or the version: in pubspec.lock). These skills target stream_chat_flutter / stream_chat_flutter_core v10 only. If the project is pinned to 9.x or earlier, stop before editing code and tell the user:

Your project uses stream_chat_flutter v. These instructions cover v10. A lot changed between v9 and v10 (widget names, controllers, theming, reaction/delete APIs). The official migration guides are at https://github.com/GetStream/stream-chat-flutter/tree/master/migrations — refer to the relevant version's guide for step-by-step instructions. Once you're on v10, I can continue with the full feature set.

If the user asks for help with the migration itself, fetch the relevant migration doc from the URL above and walk them through it step by step.

Only proceed with Chat work once the project resolves a v10 (^10.0.0) dependency. New installs always use ^10.0.0, so this check applies to existing integrations only.

Module map

Feeds note (Track A/B): Use Twitter-style UI by default. Only deviate if the user explicitly requests a different style (e.g., "Instagram grid", "Reddit-style votes").

Reference layout

Shared Flutter/Dart patterns live in sdk.md.

Product and package specifics live under references/ using a flat naming scheme:

• Reference: references/<PRODUCT>-<PACKAGE>.md
• Blueprints: references/<PRODUCT>-<PACKAGE>-blueprints.md

Current extracted modules:

• Chat + pre-built UI (stream_chat_flutter): references/CHAT-FLUTTER.md + references/CHAT-FLUTTER-blueprints.md
• Chat + custom UI (stream_chat_flutter_core): references/CHAT-CORE.md + references/CHAT-CORE-blueprints.md
• Chat advanced (push, offline, lifecycle — both UI tiers): references/CHAT-ADVANCED-FLUTTER.md + references/CHAT-ADVANCED-FLUTTER-blueprints.md - push notifications, offline/local persistence, connection lifecycle & backgrounding
• Video (stream_video_flutter): references/VIDEO-FLUTTER.md + references/VIDEO-FLUTTER-blueprints.md
• Livestream (stream_video_flutter): references/LIVESTREAM-FLUTTER.md + references/LIVESTREAM-FLUTTER-blueprints.md
• Video advanced use cases (stream_video_flutter): references/VIDEO-ADVANCED-FLUTTER.md + references/VIDEO-ADVANCED-FLUTTER-blueprints.md - audio rooms, multicall, chat+video, livestream feed, querying/events/preferences/moderation
• Ringing / incoming calls + push (stream_video_flutter + stream_video_push_notification): references/RINGING-FLUTTER.md + references/RINGING-FLUTTER-blueprints.md - outgoing ring, foreground/background/terminated incoming, CallKit (iOS) + FCM (Android)
• Feeds (stream_feed / stream_feed_flutter_core): references/FEEDS-FLUTTER.md + references/FEEDS-FLUTTER-blueprints.md

Additional Stream product coverage should stay in this naming family instead of creating more top-level skills.

Track A - New app

Full detail: builder.md - use the new-project path.

Track B - Existing app

Full detail: builder.md - use the existing-project path.

Track C - Reference lookup

Load only the relevant files for the requested package.

• Shared lifecycle / auth / state / client-ownership patterns -> sdk.md
• Chat advanced production concerns — push notifications, offline/local persistence, connection lifecycle & backgrounding (both UI tiers) -> references/CHAT-ADVANCED-FLUTTER.md
• Chat advanced wiring blueprints (FCM setup + background handler, persistence init, lazy-connect gate) -> references/CHAT-ADVANCED-FLUTTER-blueprints.md
• Chat pre-built UI setup, widgets, theming, member/user lists, message search, composer flags (voice/polls/drafts), filter operators, permissions -> references/CHAT-FLUTTER.md
• Chat pre-built UI widget blueprints -> references/CHAT-FLUTTER-blueprints.md
• Chat custom UI setup and controllers -> references/CHAT-CORE.md
• Chat custom UI widget blueprints -> references/CHAT-CORE-blueprints.md
• Video setup, call types, controls, state, StreamCallContainer -> references/VIDEO-FLUTTER.md
• Video widget blueprints (entry point, join, call container, controls, participant tile) -> references/VIDEO-FLUTTER-blueprints.md
• Livestream SDK patterns (call type, backstage, goLive/stopLive, HLS) -> references/LIVESTREAM-FLUTTER.md
• Livestream widget blueprints (mode selection, creator, WebRTC viewer, HLS viewer) -> [references/LIVESTREAM-FLUTTER-blueprints.md](references/LIVESTREAM-FLUTTE

…(truncated)