live-uikit
This is the parent skill for Tencent Live TUILiveKit integration across all platforms. It should be used when users want to build LIVE STREAMING features (host broadcasting, audience viewing). This skill guides platform selection and provides common knowledge shared across all Live implementations. For platform-specific guidance, use the corresponding sub-skills (live/vue, live/android, etc.).
What this skill does
# Live TUILiveKit Integration Skill (Multi-Platform Aggregation) > π **Parent Skill**: This is a sub-skill of `tencent-rtc-skills` (root skill). > If user's intent is ambiguous across products (Chat/Call/Live/Room), load the root skill first for product recommendation. > **π Global Reference**: This sub-skill follows the global standards defined in ROOT SKILL: > - Skill-First Principle (priority order) > - Boundary Recognition Pattern > - MCP Tools Reference (record_prompt, get_usersig, record_result) > - MCP Tool Call Sequence Pattern > - Documentation-Driven Integration Rules > - Silent Execution Rules > - Zero External Configuration > - Auto-Fetch Authentication Credentials > - Agent Execution Checklist Template > > Live-specific rules below may EXTEND or OVERRIDE global rules where explicitly noted. --- ## π΅ Boundary Recognition (Live-Specific) ### Keywords That CONFIRM Live Scope Only proceed with Live integration if user's request contains: - live streaming, broadcast - host, audience - co-host, take seat, leave seat - gift, tip - barrage, comment - PK, battle - voice chat room, voice room, seat management - TUILiveKit, LiveKit ### OUT OF SCOPE β Redirect > **π Reference**: See ROOT SKILL for global Boundary Recognition Pattern. | User Keywords | Redirect To | Reason | |---------------|-------------|--------| | "video conference" / "meeting" / "conference" | TUIRoomKit (Room) | Room is designed for meeting scenarios | | "call" / "phone call" / "1-to-1" | TUICallKit (Call) | Call is designed for call scenarios | | "chat" / "IM" / "message" (without live context) | Chat TUIKit | Chat is designed for instant messaging | --- ## Overview This Skill serves as the **multi-platform aggregation entry point** for Tencent Cloud Live TUILiveKit, applicable to the following scenarios: 1. Users need live streaming features but have not specified a platform/framework 2. Need to understand capability differences and selection recommendations across platforms 3. Need cross-platform common concepts and knowledge **Platform-Specific Guidance**: Once the platform is determined, please use the corresponding sub-Skill: - `live/vue` - Vue3 Web Applications - `live/android` - Android Native Applications - `live/ios` - iOS Native Applications - `live/flutter` - Flutter Cross-Platform Applications --- ## π― When to Use Live vs Room ### Use Live (TUILiveKit) When: | Scenario | Example | Why Live? | |----------|---------|-----------| | **Live Streaming** | Influencer broadcasting | Host/audience role separation | | **Interactive Live** | Gaming live stream | Gifts, barrage, reactions | | **E-commerce Live** | Product showcase | Co-hosting, product links | | **Voice Chat Room** | Audio-only live room | Seat management, audio effects | | **Co-hosting** | Guest joins host | Built-in co-host flow | | **PK Battle** | Two hosts compete | Cross-room PK support | ### Use Room (TUIRoomKit) Instead When: | Scenario | Why Room? | |----------|-----------| | **Webinar** | Presenter + many attendees, Q&A focus | | **Video Conference** | Peer-to-peer collaboration | | **Online Classroom** | Teacher-student interaction, screen share | --- ## Core Features TUILiveKit provides two main scenarios: ### 1. Video Live ``` βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β VIDEO LIVE β β βββββββββββββββ βββββββββββββββββββββββββββ β β β HOST β βββΆ β AUDIENCE β β β β (1 host) β Stream β (Many viewers) β β β βββββββββββββββ βββββββββββββββββββββββββββ β β β β β β β Co-host β β β βΌ βΌ β β βββββββββββββββ βββββββββββββββββββββββββββ β β β Gifts β β Barrage/Comments β β β β Beauty β β Like/Reactions β β β β PK Battle β β Follow β β β βββββββββββββββ βββββββββββββββββββββββββββ β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ``` ### 2. Voice Chat Room ``` βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β VOICE CHAT ROOM β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β β β SEATS β β β β ββββββ ββββββ ββββββ ββββββ ββββββ ββββββ ββββββ β β β β β π€ β β π€ β β π€ β β π€ β β π€ β β π€ β β π€ β β β β β βHostβ βGuestβ βGuestβ βEmptyβ βEmptyβ βEmptyβ βEmptyβ β β β β ββββββ ββββββ ββββββ ββββββ ββββββ ββββββ ββββββ β β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β β β β β βΌ β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β β β AUDIENCE (listeners) β β β β - Request to take seat β β β β - Send gifts, barrage β β β β - Audio effects, voice changer β β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ``` --- ## π Scenario Selection When user's live requirement is ambiguous, clarify: ``` User: "Implement live streaming feature" Agent should ask: "Your live streaming requirement is: 1. **Video Live** (host on camera, audience watching) β Video Live 2. **Voice Chat Room** (multi-person voice interaction, seat management) β Voice Chat Room Please select your scenario, and I will load the corresponding integration guide." ``` --- ## Core Capabilities ### Basic Features | Feature | Video Live | Voice Room | |---------|-----------|------------| | Host streaming | β | β | | Audience viewing | β | β | | Room list | β | β | | Login/Auth | β | β | ### Interactive Features | Feature | Video Live | Voice Room | |---------|-----------|------------| | Co-hosting | β Video | β Audio seats | | PK Battle | β | β | | Audience management | β | β | ### Extra Features | Feature | Video Live | Voice Room | |---------|-----------|------------| | Beauty filters | β | - | | Audio effects | β | β | | Barrage/Comments | β | β | | Gifts | β | β | --- ## π΄ Mandatory MCP Tool Usage > **π Reference**: See ROOT SKILL "Global: MCP Tool Call Sequence Pattern" for universal sequence. ### Live-Specific Tools | Tool | Purpose | When to Use | |------|---------|-------------| | `present_scenario_choice` | Clarify video live vs voice room | When scenario unclear | | `get_native_live_uikit_integration` | Basic features (host/audience/list) | For Android/iOS/Flutter | | `get_native_live_uikit_interaction` | Interactive features (co-host/PK) | For advanced interactions | | `get_native_live_uikit_extra_features` | Extra features (beauty/gifts) | For enhanced UX | | `get_web_live_uikit_integration` | Web platform integration | For Vue web | ### Live-Specific Sequence Note Live has an **additional step** in the sequence for scenario selection: ``` Standard Sequence with Live-Specific Step: 1. record_prompt 2. present_framework_choice (if platform unclear) 3. π΄ present_scenario_choice (video live vs voice room) β LIVE-SPECIFIC 4. get_usersig 5. get_*_live_uikit_integration β interaction β extra_features 6. [Generate code] 7. record_result ``` --- ## π Sub-Skill Directory | Platform | Skill Path | Status | |----------|------------|--------| | Vue3 Web | `/live/vue/SKILL.md` | Planned | | Android | `/live/android/SKILL.md` | Planned | | iOS | `/live/ios/SKILL.md` | Planned | | Flutter | `/live/flutter/SKILL.md` | Planned | --- ## Keywords for Intent Matching When user prompt contains these keywords, this skill (or its sub-skills) should be considered: **Primary Keywords** (Stron
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4βv5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.