playbridge

Change or review PlayBridge's cross-platform wire protocol and compatibility surface. Use for protocol/asyncapi.yaml, protocol/proto/messages.proto, generated bindings, shared Kotlin message parsing/building, Desktop Dart protocol code, Apple JSON consumers, extension message handling, pairing/authentication envelopes, or any change whose payload must remain compatible across senders and receivers.

Work across PlayBridge's Android phone, Android TV, and shared Kotlin projects. Use for Kotlin, Compose, GeckoView, Android playback, Gradle, shared KMP, root version-catalog, or Android-specific protocol consumer changes under mobile/android/, tv/android/, shared/, gradle/, or prebuilt/media3/.

Work on PlayBridge's native Apple phone and Apple TV applications. Use for Swift, SwiftUI, WebKit, AVFoundation, tvOS/iOS playback, Xcode project, CocoaPods, Bonjour, Keychain, TLS pinning, or Apple protocol-consumer changes under mobile/apple/ or tv/apple/.

Work on the PlayBridge Flutter desktop receiver and its Dart stream proxy. Use for Flutter/Dart receiver UI, playback engines, libmpv/media_kit, desktop sender behavior, extension bridge integration, local proxy routing, HLS rewriting, FFmpeg AVIO, proxy authentication, Docker packaging, or changes under desktop/ and stream-proxy-dart/.

Work on the PlayBridge browser extension. Use for TypeScript, WebExtension APIs, background/content/popup code, media detection, video overlays, native messaging, Desktop bridge reconnection, store packaging, manifests, or changes under extension/.

Work on the PlayBridge Svelte website and static web assets. Use for Svelte, TypeScript, Vite, public documentation pages, release/download UI, the cast demo, static deployment, or changes under web/site/.

Prepare a PlayBridge release by explicitly requested version uprevs, changelog updates, verification, commit, push, and PR creation or update. Use only when the user asks for an uprev, version bump, or release; do not trigger for an ordinary commit, push, or PR request.

Use an available code-review graph for codebase exploration, debugging, change review, impact analysis, test discovery, and scoped refactoring. Use when structural code relationships or blast radius matter; fall back to focused text and file inspection when graph tools are unavailable or lack coverage.

Safely stage task files, verify, commit, push, and create or update a PlayBridge pull request. Use when the user asks to commit, push, publish a branch, or open/update a PR without explicitly requesting a version bump or release.