@tencent-rtc/mcp 1.3.9 → 1.4.1

package/resource/doc/chatuikit/android/workflow.md

@@ -1,713 +0,0 @@
-# Android TUIKit Compose Chat Application Code Generation Workflow Instructions
-
-## 📋 Instruction Purpose
-
-To provide Agents with a **code generation blueprint for implementing core functionality of Android TUIKit Compose Chat**, and guide Agents to **prioritize using real-time latest documentation content obtained through tools**, specifically for Android instant messaging chat application scenarios.
-
-
----
-
-## 🛑 Agent Execution Hard Constraints (Guardrails)
-
-Agents must strictly follow these instructions when generating code:
-
-### 0. 🔴 Environment Check and Configuration Replacement (First Step Before Integration - Highest Priority)
-**⚠️ Strictly replace according to the exact configuration code provided in the documentation**
-
-**Core Principle**: Must use the exact configuration code provided in the documentation to replace user project configuration files, ensuring configuration consistency and compatibility
-
-**🚨 Mandatory Environment Requirements**:
-- ✅ **Android Studio**: Ladybug | 2024.2.1 and above
-- ✅ **Android System**: Android 5.0 (API 21) and above
-- ✅ **Gradle**: 8.9 and above
-- ✅ **Android Gradle Plugin**: 8.6 and above
-- ✅ **JDK**: 17 and above
-- ✅ **Kotlin**: 1.9.0 and above
-
-### 1. 🔴 Configuration File Replacement Principles (Highest Priority)
-
-**Core Requirement**: All configurations in the project must be strictly replaced according to the code provided in the documentation. When compilation errors occur due to configuration conflicts or missing dependencies, directly provide the error information to AI for resolution.
-
-**✅ Mandatory Execution Requirements**:
-1. **Must use exact configuration code provided in documentation**:
-   - All configuration code must come from code blocks explicitly provided in integration documentation
-   - **gradle/libs.versions.toml configuration must be read in real-time from integration documentation through MCP tools**
-   - Each configuration item must be completely consistent with examples in integration documentation
-   - Prohibited to modify, simplify, or optimize configuration code provided in integration documentation
-
-2. **Must perform complete configuration replacement**:
-   - User project configuration files must be completely replaced with documentation-provided configurations
-   - Must not retain conflicting configurations from user's original project
-   - Ensure configuration consistency and compatibility
-
-3. **Configuration File Replacement Checklist**:
-   - `app/build.gradle.kts`: Must replace with complete configuration provided in documentation
-   - `AndroidManifest.xml`: Must replace with configuration provided in documentation
-   - `proguard-rules.pro`: Must replace with configuration provided in documentation
-   - `gradle/libs.versions.toml`: **Must read complete configuration from integration documentation**
-   - `settings.gradle.kts`: Must replace with configuration provided in documentation
-
-**🔍 Execution Verification Mechanism**:
-Before generating each configuration file, Agent must ask themselves:
-- [ ] Have I called MCP tools to get the latest documentation?
-- [ ] Have I completely copied the configuration code from the documentation?
-- [ ] Have I avoided using configurations from memory?
-- [ ] Have I ensured the configuration is completely consistent with documentation examples?
-
-**📋 Configuration Replacement Checklist**:
-- [ ] Have I strictly configured according to the code provided in documentation?
-- [ ] Have I avoided synchronizing any configuration files from atomicx?
-- [ ] Are all configuration items completely consistent with documentation examples?
-- [ ] Have I performed complete configuration replacement rather than partial modifications?
-- [ ] Do configuration files maintain consistency and compatibility?
-
-### 2. 🚨 Core Page Code Source (Highest Priority)
-**This is the most easily violated constraint and must be emphasized first!**
-
-**Absolutely Prohibited Behaviors**:
-- ❌ **Strictly prohibited to write any core page code yourself** (ConversationsPage, ChatPage, ContactsPage)
-- ❌ **Strictly prohibited to implement simplified versions**, such as writing "simplified" pages with only dozens of lines of code
-- ❌ **Strictly prohibited to skip page code generation**, directly telling users to "refer to official examples"
-
-**Mandatory Execution Requirements**:
-- ✅ **Must directly use the following official page files**:
-  - `TUIKit_Android_Compose/chat/uikit/src/main/java/io/trtc/tuikit/chat/pages/ConversationsPage.kt`
-  - `TUIKit_Android_Compose/chat/uikit/src/main/java/io/trtc/tuikit/chat/pages/ChatActivity.kt`
-  - `TUIKit_Android_Compose/chat/uikit/src/main/java/io/trtc/tuikit/chat/pages/ContactsPage.kt`
-- ✅ **Must completely copy the above files from the official `TUIKit_Android_Compose/chat/uikit/src/main/java/io/trtc/tuikit/chat/pages/` directory**
-- ✅ **Must include complete Activity/Composable, UI component tree, business logic**
-- ✅ **Must copy all dependent components and utility classes**, maintaining complete file structure
-
-**Verification Standard**: Generated core page code should be consistent with official source code and functionally complete
-
-### 3. Documentation-Driven Integration
-- Must strictly follow the steps in `llm_code_generation_instructions_md` from tool return results
-- **Must strictly generate code according to example code in integration documentation**, not allowed to modify code structure and implementation methods arbitrarily
-- Code generation should completely follow best practices and examples provided in integration documentation to ensure code correctness and runnability
-
-### 4. Source Code Integration Method
-- TUIKit Android Compose uses **source code integration method**, requiring cloning from GitHub and copying core source code files
-- **Must clone source code to the same level directory as user project** (i.e., `../TUIKit_Android_Compose/`)
-- Must follow integration documentation guidance to copy specified source code folders (`atomicx`, `chat/uikit`) to user project
-- When copying, must ensure merging with existing folders in user project, avoiding direct overwriting
-
-### 5. Silent Integration Execution
-- After all code writing is completed, prompt user to execute Gradle Sync and start project in the final step
-- **Android Project Configuration Standards**:
-  1. **First Priority**: Prompt user to click "File > Sync Project with Gradle Files" in Android Studio
-  2. **Second Priority**: Wait for Gradle sync to complete, analyze and fix immediately if errors occur
-  3. **Third Priority**: Guide user to click Run button to start project
-  4. **Final Fallback**: If sync fails, provide detailed error troubleshooting guidance
-
-#### 📋 Manual Gradle Sync Guidance
-
-**When automatic Gradle sync fails, please guide users to follow these steps**:
-
-**Step 1: Manual sync in Android Studio**
-- Click menu **File** → **Sync Project with Gradle Files**
-- Or click the **Sync** icon in toolbar (double arrow cycle icon)
-
-**Step 2: Check sync status**
-- View the **Build** window at the bottom, wait for sync completion
-- If red error messages appear, record complete error logs
-
-**Step 3: Common error handling**
-```bash
-# Clean project cache
-./gradlew clean
-
-# Re-download dependencies
-./gradlew --refresh-dependencies
-```
-
-**💡 Common Issue Troubleshooting**
-
-| Error Phenomenon | Possible Cause | Solution |
-|---------|---------|---------|
-| `Project 'atomicx' not found` | settings.gradle.kts configuration error | Check same-level directory reference path |
-| `Unresolved reference: Material3` | Missing dependency configuration | Check libs.versions.toml configuration |
-| `Duplicate class found` | Dependency version conflict | Unify dependency versions |
-| `AGP version requires Java 17` | JDK version too low | Upgrade to JDK 17+ |
-
-**⚠️ User Reminders**:
-1. Ensure Android Studio version >= Ladybug | 2024.2.1
-2. Ensure JDK version >= 17
-3. Ensure network can access `maven.google.com` and `mavenCentral()`
-4. If in mainland China, recommend configuring mirrors:
-   ```kotlin
-   // Add in settings.gradle.kts
-   dependencyResolutionManagement {
-       repositories {
-           maven { url = uri("https://maven.aliyun.com/repository/google") }
-           maven { url = uri("https://maven.aliyun.com/repository/central") }
-           google()
-           mavenCentral()
-       }
-   }
-   ```
-
-### 6. Authentication Credential Configuration (Important)
-- **Must call `get_usersig` tool to get test SDKAppID, UserID, UserSig**
-- UserID format: `userXXX` (XXX is numbers), e.g., `user123`
-- During testing phase, authentication information can be hardcoded in code, but must be clearly marked in comments as for testing only
-- **Prohibited to create `.env` files** for production environment configuration
-- **⚠️ Security Warning**: Must inform users that client-side UserSig generation is only suitable for local testing, production environment must generate UserSig on server side
-
-### 7. LoginPage Implementation Constraints 🔴
-- **Must refer to `TUIKit_Android_Compose/chat/demo/app/src/main/java/io/trtc/tuikit/chat/login/LoginPage.kt` to implement login page**
-- **SDKAppID, UserID, UserSig must directly use information returned by `get_usersig` tool**
-- **Prohibited to add UserID input box in UI**, not allowing users to actively input UserID
-- **Prohibited to add SDKAppID and UserSig input boxes in UI**
-- **Login interface must call `LoginStore.shared.login`**, passing complete credentials obtained from `get_usersig`
-- After successful login, automatically navigate to main page (ConversationsPage or ChatActivity)
-
-### 8. chat-only Mode Function Limitations (⚠️ Default Constraints + Exceptions When User Actively Requests)
-
-**Default Behavior**:
-When users choose chat-only mode, Agent **excludes by default** the following extended functions:
-- **Does not integrate ConversationsPage by default** (conversation list page)
-- **Does not integrate ContactsPage by default** (contacts page)
-- **Retains only core chat page by default**: `ChatActivity`
-
-**Exception Handling**:
-If users **explicitly request** adding certain extended functions (such as "need ConversationsPage", "want to integrate contacts", etc.), Agent **should allow and execute**:
-- ✅ On the basis of core chat page, additionally integrate functions explicitly requested by users
-- ✅ Only add functions explicitly requested by users, do not arbitrarily expand other functions
-- ✅ Correctly integrate required pages according to integration documentation standards
-
-**Judgment Criteria**:
-- User requirements contain explicit function keywords (such as "ConversationsPage", "contacts", "search", "conversation list", etc.)
-- User explicitly states the need for certain extended functions
-
-### 9. Import Path Constraints 🔴
-- **Correct package paths must strictly follow usage in official example code**
-- **Prohibited to speculate any package paths**:
-  - ❌ `io.trtc.tuikit.core.xxx` (speculated wrong path)
-  - ❌ Any wildcard imports
-- **Prohibited to speculate package names yourself**, must strictly use according to example code in integration documentation
-- All import statements must use correct package name paths
-
-### 10. Android Project Standards
-- Use Android Studio >= Ladybug | 2024.2.1, JDK >= 17, Kotlin >= 1.9.0 versions
-- Follow Android official code style and best practices
-- Configure Android platform permissions and dependencies according to integration documentation
-- **Must configure Compose and theme system** (mandatory requirement):
-
-**Complete Activity Structure Example**:
-```kotlin
-import android.os.Bundle
-import androidx.activity.ComponentActivity
-import androidx.activity.compose.setContent
-import androidx.compose.foundation.layout.fillMaxSize
-import androidx.compose.material3.MaterialTheme
-import androidx.compose.material3.Surface
-import androidx.compose.ui.Modifier
-import io.trtc.tuikit.atomicx.theme.LocalTheme
-
-class MainActivity : ComponentActivity() {
-    override fun onCreate(savedInstanceState: Bundle?) {
-        super.onCreate(savedInstanceState)
-        setContent {
-            MaterialTheme {
-                Surface(
-                    modifier = Modifier.fillMaxSize(),
-                    color = LocalTheme.current.colors.background
-                ) {
-                    // Your main page content
-                    HomePage()
-                }
-            }
-        }
-    }
-}
-```
-
-**⚠️ Key Points**:
-1. **Must use `LocalTheme.current.colors` to get theme colors**
-2. **Directly use Compose content in `setContent`**
-3. **Optionally use `MaterialTheme` and `Surface` to provide background color**
-4. **Refer to implementation in official demo examples**
-
-**📋 Official MainActivity Reference Implementation**:
-- **Must refer to official example**: `TUIKit_Android_Compose/chat/demo/app/src/main/java/io/trtc/tuikit/chat/MainActivity.kt`
-- **Page callback implementation**: Refer to page navigation and callback handling logic in official examples
-- **Bottom navigation structure**: Follow navigation bar design patterns in official demo
-- **Event handling mechanism**: Copy click events and page switching logic from official examples
-
-### 11. Environment Dependency Preparation
-- Ensure users have installed Android Studio, JDK 17+
-- **Gradle sync follows multi-level fallback strategy in Section 3**
-- **If automatic sync fails, must generate fallback guidance for users to execute manually**
-
----
-
-## 🛠️ Integration Mode Distribution (Goals)
-
-Based on user requirements, Agent must choose the corresponding execution path:
-
-### 1. Full-Featured Integration (full-featured)
-
-**Objective**: Implement complete IM application similar to WeChat
-
-**Core Pages**: 
-- `ConversationsPage` (conversation list)
-- `ChatActivity` (chat page)
-- `ContactsPage` (contacts)
-
-**Execution Reference**: 
-- Refer to `integration.md` instructions obtained in real-time from tool return results
-
-**Applicable Scenarios**:
-- Building independent chat applications
-- Need complete conversation management, address book, group management functions
-- As core functional modules of mobile applications
-
-**MainActivity and Bottom Navigation Implementation Requirements** (🔴 Mandatory Requirements):
-
-If the project does not have bottom navigation, **must create MainActivity as main page**, including the following requirements:
-
-1. **Must implement bottom navigation bar**:
-   - Default includes two Tabs: **Messages** (ConversationsPage) and **Contacts** (ContactsPage)
-   - Use Compose Navigation or Scaffold's bottomBar
-   
-2. **Tab clicks must be able to navigate to real pages**:
-   - Click "Messages" Tab → Display `ConversationsPage` (conversation list)
-   - Click "Contacts" Tab → Display `ContactsPage` (contact list)
-   - Use Compose Navigation or state management to implement page switching
-   
-3. **MainActivity Implementation Requirements**:
-   - **Directly refer to official source code**: `TUIKit_Android_Compose/chat/demo/app/src/main/java/io/trtc/tuikit/chat/MainActivity.kt`
-   - **Completely copy official implementation logic**: Including page structure, callback handling, navigation logic, etc.
-   - **Keep consistent with official examples**: Ensure functional completeness and best practices
-
-   **🔴 Official MainActivity Reference Requirements**:
-   - **Mandatory reference**: `TUIKit_Android_Compose/chat/demo/app/src/main/java/io/trtc/tuikit/chat/MainActivity.kt`
-   - **Page callbacks must be completely implemented**:
-     - `ConversationsPage`'s `onConversationClick` callback → Navigate to `ChatActivity`
-     - `ContactsPage`'s `onGroupClick` and `onContactClick` callbacks → Navigate to `ChatSettingActivity`
-   - **Callback parameter passing**: Strictly pass parameters like `conversationID`, `contactID` according to official examples
-   - **Intent startup method**: Use `Intent` and `putExtra` methods from official examples
-
-4. **Navigate to MainActivity after successful login**:
-   ```kotlin
-   // LoginPage.kt
-   LoginStore.shared.login(...) { success ->
-       if (success) {
-           val intent = Intent(context, MainActivity::class.java)
-           context.startActivity(intent)
-           (context as Activity).finish()  // Close login page
-       }
-   }
-   ```
-
-5. **Prohibited Behaviors**:
-   - ❌ Navigate directly to single page (like ConversationsPage) after login without bottom navigation
-   - ❌ Create empty MainActivity without actual page switching logic
-   - ❌ Bottom navigation with only one Tab (must have at least "Messages" and "Contacts")
-
----
-
-### 2. Chat Page Only Integration (chat-only)
-
-**Objective**: Suitable for customer service, consultation, detail page private chat and other pure conversation scenarios
-
-**Core Pages**: 
-- `ChatActivity` (chat page)
-
-**Execution Reference**: 
-- Refer to `integration.md` instructions obtained in real-time from tool return results
-
-**Applicable Scenarios**:
-- Customer service consultation scenarios (users click consultation button to enter chat page)
-- Medical online consultation (patient and doctor one-on-one communication)
-- Order detail page private chat (buyer and seller communication)
-- Private message function in social applications
-
-**💡 Page Navigation After Successful Login (chat-only Mode Guidance)**:
-
-**Default Behavior**: If users don't specify otherwise, navigate directly to `ChatActivity` after successful login, opening single chat conversation with `administrator`.
-
-**Flexible Adjustment**: If users have other requests (such as opening chat page at specific timing, specifying other conversation objects), need to confirm navigation timing and target conversation according to user guidance.
-
-**Default Implementation Example**:
-
-```kotlin
-// ✅ Successful login, directly enter chat page
-val intent = Intent(context, ChatActivity::class.java).apply {
-    putExtra("conversationID", "c2c_administrator")  // Default single chat with administrator
-}
-context.startActivity(intent)
-(context as Activity).finish()  // Close login page
-```
-
-**⚠️ Key Points**:
-1. **Use `Intent` to pass conversationID** (avoid hardcoding)
-2. **conversationID format**: Single chat `'c2c_<userID>'`, group chat `'group_<groupID>'`
-3. **Default conversation ID**: `'c2c_administrator'` (can be adjusted to other userID or groupID according to user needs)
-4. **Navigation timing**: Default immediate navigation in successful login callback, if users have special needs (such as navigation after button click), need to adjust according to user guidance
-
-**🔴 Default Excluded Functions (Agent Must Comply)**:
-
-When generating chat-only mode code, Agent **excludes by default** the following functions and pages:
-
-1. **Does not integrate ConversationsPage (conversation list) by default**
-   - Does not generate conversation list page by default
-   - Does not introduce conversation switching function by default
-   - Chat page should be independent, direct pure chat interface by default
-
-2. **Does not integrate ContactsPage (contacts) by default**
-   - Does not generate address book page by default
-   - Does not introduce contact management function by default
-
-3. **Does not integrate bottom navigation bar (TabBar) by default**
-   - In chat-only mode, users specify conversation ID through external routing/parameters
-   - No need for page switching function by default
-
----
-
-**⚠️ Exception Handling When User Actively Requests**:
-
-If users **explicitly request** adding certain extended functions in chat-only mode, Agent **should allow and execute**:
-
-**Trigger Conditions** (satisfying any one):
-- User explicitly states: "need ConversationsPage", "want to integrate conversation list", "add conversation switching function"
-- User explicitly states: "need ContactsPage", "want to add contacts", "integrate address book"
-- User explicitly proposes other extended function requirements
-
-**Agent Execution Process**:
-1. ✅ **Confirm user requirements**: Recognize that user actively requests adding extended functions
-2. ✅ **Allow integration**: On the basis of chat-only mode, additionally integrate pages requested by users
-3. ✅ **Maintain restraint**: Only add functions explicitly requested by users, do not arbitrarily expand other functions
-4. ✅ **Follow documentation**: Correctly integrate required pages according to integration documentation standards
-
----
-
-## 📦 Core Version Requirements
-
-| Tool/Platform | Minimum Version Requirement |
-|----------|-------------|
-| **Android Studio** | Ladybug \| 2024.2.1 and above |
-| **Android System** | >= 5.0 (API 21) |
-| **Gradle** | >= 8.9 |
-| **Android Gradle Plugin** | >= 8.6 |
-| **JDK** | >= 17 |
-| **Kotlin** | >= 1.9.0 |
-
----
-
-## 📦 Installation Command Examples
-After Agent completes code generation, must guide users to execute the following steps in order:
-
-**⚠️ Important: Android Project Configuration Standards**
-- After Android project configuration is completed, **must execute Gradle Sync**
-- No need for manual command line operations
-- IDE will automatically download dependencies and build project
-
-### 🔴 Step 1: Environment Check and Configuration File Replacement (Must Execute Before Integration - Highest Priority)
-
-**⚠️ Before executing any integration operations, Agent must first perform environment check and configuration file replacement**:
-
-#### 1.1 Mandatory Environment Check
-**Agent must first verify the following environment requirements**:
-- ✅ **Android Studio**: Ladybug | 2024.2.1 and above
-- ✅ **Android System**: Android 5.0 (API 21) and above  
-- ✅ **Gradle**: 8.9 and above
-- ✅ **Android Gradle Plugin**: 8.6 and above
-- ✅ **JDK**: 17 and above
-- ✅ **Kotlin**: 1.9.0 and above
-
-**If environment does not meet requirements, Agent must**:
-1. Clearly inform users of current environment deficiencies
-2. Provide detailed environment upgrade guidance
-3. Pause integration operations until environment meets requirements
-
-#### 1.2 Complete Configuration File Replacement (Mandatory Execution)
-**Agent must execute configuration file replacement in the following order**:
-
-1. **Call MCP tools to get latest integration documentation**
-2. **Completely replace the following configuration files**:
-   - `gradle/libs.versions.toml` - **Must read in real-time from integration documentation**
-   - `app/build.gradle.kts` - Use complete configuration provided in documentation
-   - `AndroidManifest.xml` - Use configuration provided in documentation
-   - `proguard-rules.pro` - Use configuration provided in documentation
-   - `settings.gradle.kts` - Use configuration provided in documentation
-
-3. **Execute verification check**:
-   - [ ] Have I called MCP tools to get latest documentation?
-   - [ ] Have I completely copied configuration code from documentation?
-   - [ ] Have I avoided using configurations from memory?
-   - [ ] Have I ensured configuration is completely consistent with documentation examples?
-
-**⚠️ Only after completing environment check and configuration file replacement can subsequent steps continue**
-
-### 🔴 Step 2: Dependency Completeness Check (Second Priority)
-
-**After completing environment check and configuration file replacement, Agent must execute the following checks**:
-
-1. **Automatically scan all import statements in generated code**:
-   - Use `search_content` tool to search all generated `.kt` files
-   - Extract all package names from `import` statements
-   
-2. **Verify dependency configuration completeness**:
-   - Check `dependencies` block in `build.gradle.kts` or `build.gradle`
-   - Verify all libraries used in code are declared in dependencies
-   
-3. **Key dependencies that must be checked**:
-   - **Read complete dependency configuration from integration documentation**
-   - **Strictly configure according to versions in gradle/libs.versions.toml**
-   - **Ensure all dependencies are completely consistent with integration documentation**
-
-4. **Handling when missing dependencies are found**:
-   - **Refer to complete configuration in integration documentation**
-   - **Supplement missing dependencies to gradle/libs.versions.toml according to integration documentation**
-   - **Explain to users** which dependencies were added and why
-   - **Do not wait for user confirmation**, fix directly
-
-**Example check process**:
-- Agent scans all import statements in generated code
-- Compare with dependency configuration in integration documentation
-- Ensure project configuration is completely consistent with integration documentation
-
-### 🔴 Step 3: Gradle Sync and Compilation Verification
-
-**After Agent completes configuration file replacement, must guide users to execute Gradle sync**:
-
-**Recommended execution method**:
-- Agent must clearly inform users to click "File > Sync Project with Gradle Files" in Android Studio
-- Wait for Gradle sync to complete
-- If compilation errors occur, immediately inform Agent of error information
-- Agent will supplement missing dependencies or fix code based on error information
-
-**Common compilation errors and handling**:
-| Error Type | Error Message Example | Agent Handling Method |
-|---------|------------|--------------|
-| Missing dependency | `Unresolved reference: Material3` | Check libs.versions.toml configuration |
-| Missing module | `Project 'atomicx' not found` | Check `settings.gradle.kts` configuration |
-| Version conflict | `Duplicate class found` | Check dependency versions and unify |
-| Import error | `Unresolved reference: LoginStore` | Check import paths, refer to official examples |
-
-**Fallback strategy**:
-- If IDE sync fails, prompt users to check network connection
-- If dependency download fails, suggest configuring domestic mirrors
-- If build errors occur, **immediately read error logs**, analyze missing dependencies or import issues
-- **Do not let users fix themselves**, Agent should actively analyze and fix
-
----
-
-## 📱 Real Device Debugging Guidance
-
-### Android Real Device Debugging Steps
-
-#### 1. Hardware Preparation
-- Use USB data cable to connect Android device to computer
-- Ensure device has enabled developer options and USB debugging mode
-
-#### 2. Enable Developer Options
-On Android device:
-- Go to **Settings** → **About Phone**
-- Tap **Build Number** 7 times continuously until "You are now a developer" appears
-- Return to settings main page, enter **Developer Options**
-- Enable **USB Debugging**
-
-#### 3. View Connected Devices
-```bash
-# Method 1: Use adb command
-adb devices
-
-# Output example:
-# List of devices attached
-# XXXXXXXX	device
-
-# Method 2: View in Android Studio
-# Toolbar → Device Manager → Physical
-```
-
-#### 4. Run in Android Studio
-- Click **Run** button in toolbar (green triangle)
-- Select connected Android device in device selection dialog
-- Wait for application installation and startup
-
----
-
-## 🚀 Multi-Device Simultaneous Debugging
-
-### Connect Multiple Devices Simultaneously
-```bash
-# View all devices
-adb devices
-
-# Run on specific device (select corresponding device in Android Studio)
-# Example: Run simultaneously on different Android devices
-```
-
----
-
-## 📊 Debugging Suggestions
-
-### Log Viewing
-```bash
-# Android logs
-adb logcat | grep "TUIKit"
-
-# Performance analysis startup
-# Use Profiler tool in Android Studio
-```
-
-### Common Issue Troubleshooting
-- **Device not recognized**: Check USB drivers and debugging mode
-- **Application installation failed**: Check device storage space and permissions
-- **Network connection issues**: Ensure device network is normal
-
----
-
-## 🔄 Complete Automation Process
-
-```mermaid
-graph TD
-    A[Receive User Requirements] --> B[Check Android Environment Configuration]
-    B --> C[Enter Project Parent Directory and Clone TUIKit_Android_Compose]
-    C --> D[Configure settings.gradle.kts According to Integration Documentation]
-    D --> E[Configure app/build.gradle.kts According to Integration Documentation]
-    E --> F[Configure AndroidManifest.xml According to Integration Documentation]
-    F --> G[Configure libs.versions.toml According to Integration Documentation]
-    G --> H[Call get_usersig Tool to Get Authentication Information]
-    H --> I[Implement Login Logic According to Integration Documentation]
-    I --> J[Implement Core Pages According to Integration Documentation]
-    J --> K[Call record_result to Record Integration Results]
-    K --> L[Guide User to Execute Gradle Sync]
-    L --> M{Sync Successful?}
-    M -->|Yes| N[Guide User to Connect Real Device for Debugging]
-    M -->|No| O[Provide Error Troubleshooting Guidance]
-    N --> P[Guide User to Click Run to Start Project]
-    O --> P
-    P --> Q[Project Started Successfully]
-```
-
----
-
-## 📝 Key Points Summary
-
-| Category | Requirement |
-|------|------|
-| **Framework Version** | Android Studio >= Ladybug \| 2024.2.1, JDK >= 17, Kotlin >= 1.9.0 |
-| **Integration Method** | Source code integration (clone from GitHub and reference through local path) |
-| **Documentation Priority** | ⚠️ Strictly follow example code in integration documentation, not allowed to modify arbitrarily |
-| **Core Page Source** | 🚨 **Strictly prohibited to write core page code yourself**, must completely copy page files from official demo directory |
-| **Page Completeness Verification** | ⚠️ Core page code must include complete Activity/Composable, UI component tree, business logic |
-| **Silent Integration** | Guide user to execute Gradle Sync and start project after code writing is completed |
-| **Credential Acquisition** | ⚠️ Must use `get_usersig` tool to get test authentication information |
-| **Security Reminder** | ⚠️ Must inform users: Client-side UserSig generation is only suitable for testing, production environment must generate on server side |
-| **Result Recording** | ⚠️ Must call `record_result` tool to record results after integration completion |
-| **Integration Modes** | Support full-featured (complete) and chat-only (chat only) two modes |
-| **chat-only Limitations** | ⚠️ Exclude ConversationsPage, ContactsPage by default; allow integration when user actively requests |
-| **Import Constraints** | ⚠️ Must strictly follow package paths in official example code, prohibited to speculate any paths |
-
----
-
-## 🎯 Agent Execution Checklist
-
-After completing code generation, Agent must confirm all the following items:
-
-### MCP Tool Call Verification
-- [ ] ✅ **Called `get_native_chat_uikit_integration` to get latest integration documentation**
-- [ ] ✅ **Extracted all configuration code from integration documentation**
-- [ ] ✅ **Called `get_usersig` to get test authentication information**
-- [ ] ❌ **Strictly prohibited to use any configuration code from memory**
-
-### Configuration File Completeness Verification
-- [ ] ✅ **gradle/libs.versions.toml completely sourced from integration documentation**
-- [ ] ✅ **app/build.gradle.kts completely sourced from integration documentation**
-- [ ] ✅ **AndroidManifest.xml completely sourced from integration documentation**
-- [ ] ✅ **proguard-rules.pro completely sourced from integration documentation**
-- [ ] ✅ **settings.gradle.kts completely sourced from integration documentation**
-
-### Code Implementation Verification
-- [ ] ✅ **All import paths sourced from official example code**
-- [ ] ✅ **All API call methods consistent with official examples**
-- [ ] ✅ **All class names, function names consistent with official examples**
-- [ ] ❌ **Strictly prohibited to speculate or simplify any implementation**
-
-### Project Initialization
-- [ ] Entered user project's parent directory
-- [ ] Cloned TUIKit_Android_Compose repository to same-level directory
-- [ ] Configured `settings.gradle.kts` according to integration documentation
-- [ ] Configured `app/build.gradle.kts` according to integration documentation
-
-### Code Generation
-- [ ] 🔴 **Called `get_usersig` tool to get SDKAppID, UserID, UserSig**
-- [ ] 🔴 **Referred to official LoginPage to implement login page** (Path: `TUIKit_Android_Compose/chat/demo/app/src/main/java/io/trtc/tuikit/chat/login/LoginPage.kt`)
-- [ ] 🔴 **Login page does not include UserID, SDKAppID, UserSig input boxes**
-- [ ] Implemented login logic according to integration documentation, automatically using credentials returned by `get_usersig`
-- [ ] 🔴 **Completely copied page files from official demo directory**
-- [ ] 🔴 **Core pages include complete Activity/Composable, UI component tree, business logic**
-- [ ] 🔴 **Strictly prohibited to write simplified implementations yourself, strictly prohibited to skip page code generation**
-- [ ] 🔴 **All imports use correct package paths, strictly following official examples**
-- [ ] Implemented inter-page navigation logic according to integration documentation
-
-### Integration Modes
-- [ ] Selected correct integration mode based on user requirements (full-featured or chat-only)
-- [ ] full-featured mode: Integrated ConversationsPage, ChatActivity, ContactsPage and other pages
-- [ ] full-featured mode: Implemented MainActivity and bottom navigation bar
-- [ ] chat-only mode: Integrated core pages (ChatActivity)
-- [ ] chat-only mode: Determined whether to integrate extended functions based on user requirements
-  - [ ] If user did not actively request, confirmed not including ConversationsPage, ContactsPage and other pages
-  - [ ] If user actively requested (such as "need ConversationsPage"), additionally integrated functions explicitly requested by user
-
-### Security and Reminders
-- [ ] 🔴 **Informed users**: Currently generated code is only suitable for local testing, production environment must generate UserSig on server side
-- [ ] Marked location of test configuration in code comments
-
-### Final Delivery Verification
-- [ ] ✅ **Generated code can be directly compiled and run**
-- [ ] ✅ **No need for users to manually modify any configuration**
-- [ ] ✅ **All functions consistent with official demo effects**
-
-### Final Check
-- [ ] 🔴 **Called `record_result` tool to record integration results**
-- [ ] 🔴 **Guided user to execute Gradle Sync**
-- [ ] Guided user to connect device or start emulator
-- [ ] Guided user to click Run button to run project
-- [ ] Project can run normally without errors
-
----
-
-## 🔗 Required Tools
-
-**⚠️ MCP Tool Call Parameter Notes**:
-When calling MCP tools, must use correct parameter names to avoid call failures due to parameter errors:
-- ✅ **Correct**: `get_native_chat_uikit_integration` uses parameter `"framework"`
-- ❌ **Wrong**: Using parameter `"platform"` will cause call failure
-- Before calling any MCP tool, Agent must first call `mcp_get_tool_description` to confirm correct parameter names
-
-### `get_usersig` - Get Test Authentication Information
-**Purpose**: Get Tencent Cloud IM test authentication information
-- `SDKAppID`: Application identifier
-- `UserID`: User ID
-- `UserSig`: User signature
-
-**Usage Constraints**:
-- ✅ Must use `get_usersig` tool to get test authentication
-- ❌ Prohibited to let users manually input or copy from console
-- ⚠️ Must inform users: Client-side UserSig generation is only suitable for testing, production environment must generate on server side
-
-### `record_result` - Record Integration Results
-**Purpose**: Record integration process and results for statistics and analysis
-
-**Call Timing**: Call after completing all integration steps and successfully guiding user to run project
-
----
-
-## 📚 Related Resource Links
-
-- **TUIKit Android Compose GitHub Repository**: https://github.com/Tencent-RTC/TUIKit_Android_Compose
-- **Tencent Cloud Instant Messaging Chat Console**: https://console.trtc.io/
-- **Server-side UserSig Generation**: https://console.trtc.io/usersig
-- **Enable Chat Service**: https://trtc.io/document/45907?product=chat&menulabel=uikit&platform=android
-- **Jetpack Compose Official Documentation**: https://developer.android.com/jetpack/compose
-- **Android Official Documentation**: https://developer.android.com/
-
----
-
-**Applicable Platform**: Android  
-**TUIKit Version**: TUIKit Compose (based on AtomicXCore)  
-**Minimum Requirements**: Android Studio >= Ladybug | 2024.2.1, JDK >= 17, Kotlin >= 1.9