Agent skill · software engineering · getstream
stream-swift
Build, integrate, migrate to, and answer how-to questions for Stream Chat, Video, and Feeds in Swift / SwiftUI / UIKit / iOS apps. Routes each request to the exact official iOS docs page, fetches it live, and applies it - with a curated setup flow, a Sendbird -> Stream Chat migration runbook, and iOS-specific pitfalls.
Why this skill is useful
Provides a curated setup flow and migration runbook for integrating Stream Chat, Video, and Feeds into iOS apps, which the AI wouldn't reliably generate on its own.
What it needs
Requires xcode installed locally. About 9k tokens when loaded. Last updated 2026-08-05. 17 stars on the source repository.
What this skill does
Stream Swift - docs orchestrator for iOS This skill is small on purpose. It does not bundle SDK reference dumps - the official iOS docs are the source of truth and they cover the entire surface (Chat, Video, Feeds; SwiftUI and UIKit; polls, drafts, voice, AI, push, screen share, CallKit, SIP, transcriptions, moderation, and more). Your job is to orchestrate: classify the request, point to the exact docs page, fetch it live, and apply it inside the user's project - while obeying the curated rules and pitfalls that the docs do not shout about. Rules (read once per session): RULES.md - non-negotiable rules + iOS pitfalls. Read before writing any code. --- The docs convention (the core mechanism) Every Stream docs page has a Markdown twin that coding agents can read directly: take the page URL, drop the trailing /, add .md. Always fetch the .md variant - it is clean Markdown with verbatim code, no page chrome. Per-product index pages list every doc page with its .md URL. Fetch these to discover or confirm a page: Product Live index (always current) Page URL shape --- --- --- Chat (iOS SDK: UI + State Layer) https://getstream.io/cli/docs/chat-sdk-ios.md https://getstream.io/chat/docs/sdk/ios/...md Chat (low-level client API reference) https://getstream.io/cli/docs/chat-ios-swift.md https://getstream.io/chat/docs/ios-swift/...md Video https://getstream.io/cli/docs/video-ios.md https://getstream.io/video/docs/ios/...md Feeds https://getstream.io/cli/docs/activity-feeds-ios.md https://getstream.io/activity-feeds/docs/ios/...md URL grounding: only fetch a page URL that you got from docs-map.md or from a live index fetch in this conversation. Do not invent doc paths from memory - many look guessable but are wrong. If a page is not in the map, fetch the live index and pick from it. --- Step 0: Classify the request (always first) From the user's words alone, resolve three things: 1. Product - Chat, Video, Feeds, or a combination. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills getstream/stream-swift