@tencent-rtc/mcp 1.3.9 → 1.4.1

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

@@ -1,941 +0,0 @@
-# Flutter TUIKit Chat Application Code Generation Workflow Instructions
-
-## 📋 Purpose of Instructions
-
-Provide Agents with a **code generation blueprint for implementing Flutter TUIKit Chat core features**, and guide Agents to **prioritize using the latest documentation content obtained in real-time through tools**, specifically for Flutter instant messaging chat application scenarios.
-
----
-
-## 🛑 Agent Execution Hard Constraints (Guardrails)
-
-Agents must strictly follow these instructions when generating code:
-
-### 0. 🚨 Core Page Code Source (Highest Priority)
-**This is the constraint most easily violated and must be emphasized first!**
-
-**Absolutely Prohibited Behaviors**:
-- ❌ **Strictly prohibited from writing any core page code yourself** (ConversationsPage, ChatPage, ContactsPage)
-- ❌ **Strictly prohibited from simplified implementations**, such as "simplified version" pages with only a few dozen lines of code
-- ❌ **Strictly prohibited from skipping page code generation**, directly asking users to "refer to official examples"
-
-**Mandatory Execution Requirements**:
-- ✅ **Must directly use the following official page files**:
-  - `TUIKit_Flutter/chat/uikit/lib/conversations_page.dart`
-  - `TUIKit_Flutter/chat/uikit/lib/chat_page.dart`
-  - `TUIKit_Flutter/chat/uikit/lib/contacts_page.dart`
-- ✅ **Must completely copy the above files from the `TUIKit_Flutter/chat/uikit/lib/` directory**
-- ✅ **Must include complete State classes, UI component trees, business logic**
-- ✅ **Must copy all dependent components and utility classes**, keeping the file structure intact
-
-**Verification Standard**: Generated core page code should match official source code and be fully functional
-
-### 1. Documentation-Driven Integration
-- Must strictly follow the steps in `llm_code_generation_instructions_md` from the tool return results
-- **Must strictly generate code according to the sample code in the integration documentation**, do not modify code structure and implementation methods without authorization
-- Code generation should fully follow the best practices and examples provided in the integration documentation to ensure code correctness and runnability
-
-### 2. Source Code Integration Method
-- TUIKit Flutter adopts **source code integration method**, requiring cloning from GitHub and copying core source code files
-- **Must clone the source code to the root directory of the user's project** (i.e., `project_root/TUIKit_Flutter/`)
-- Must follow the integration documentation guidance to copy the specified source code folders (`atomic-x`, `chat/uikit`) into the user's project
-- When copying, must ensure merging with existing folders in the user's project, avoid direct overwriting
-
-### 3. Silent Integration Execution
-- After all code is written, automatically install dependencies and start the project in the final step
-- **Flutter Command Execution Strategy (Multi-level Fallback, Ensure Success)**:
-  1. **First Priority**: Try to execute `flutter pub get` directly
-  2. **Second Priority**: If it fails, use `which flutter` to get the full path and execute
-  3. **Third Priority**: If it still fails, try common paths:
-     - macOS/Linux: `$HOME/flutter/bin/flutter`
-     - macOS (Homebrew): `/opt/homebrew/bin/flutter`
-  4. **Final Fallback**: If all fail, **guide users to execute manually** (see guidance below)
-- After successful startup, prompt users to run the application on simulator or real device
-
-#### 📋 Manual Dependency Installation Guidance
-
-**When automatic execution of `flutter pub get` fails, please guide users to follow these steps**:
-
-**Step 1: Open terminal and navigate to project directory**
-```bash
-cd /path/to/your/project  # Replace with actual project path
-```
-
-**Step 2: Manually install Flutter dependencies**
-```bash
-flutter pub get
-```
-
-**Step 3: (iOS Project) Install CocoaPods dependencies**
-```bash
-cd ios
-pod install
-cd ..
-```
-
-**Step 4: Verify dependency installation**
-```bash
-flutter doctor -v  # Check Flutter environment
-flutter pub deps   # View dependency tree
-```
-
-**Step 5: Start project**
-```bash
-# Method 1: Use simulator/real device
-flutter run
-
-# Method 2: Specify device
-flutter devices              # List available devices
-flutter run -d <device-id>   # Run on specified device
-```
-
-**💡 Common Issue Troubleshooting**
-
-| Error Phenomenon | Possible Cause | Solution |
-|---------|---------|---------|
-| `bash: flutter: command not found` | Flutter not added to PATH | Run `export PATH="$PATH:$HOME/flutter/bin"` or refer to [Flutter Installation Documentation](https://docs.flutter.dev/get-started/install) |
-| `Error: Cannot find package` | pubspec.yaml configuration error | Check if dependency paths are correct (`tuikit_atomic_x` should point to `TUIKit_Flutter/atomic-x`) |
-| `CocoaPods not installed` | iOS missing CocoaPods | Run `sudo gem install cocoapods` |
-| `version solving failed` | Dependency version conflict | Run `flutter pub upgrade` or use `dependency_overrides` |
-
-**⚠️ Remind Users**:
-1. Ensure Flutter environment is correctly installed (run `flutter doctor` to check)
-2. Ensure network can access `pub.dev` and `github.com`
-3. If in mainland China, it is recommended to configure mirrors:
-   ```bash
-   export PUB_HOSTED_URL=https://pub.flutter-io.cn
-   export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
-   ```
-
-### 4. Authentication Credential Configuration 🔴
-- **Must call the `get_usersig` tool to obtain SDKAppID, UserID, UserSig for testing**
-- UserID format: `userXXX` (XXX is a number), e.g., `user123`
-- **⚠️ Security Warning**: Must inform users that client-side generation of UserSig is only suitable for local testing, production environment must generate UserSig on the server side
-- Authentication information can be hard-coded in code for testing, but must be clearly marked in comments as for testing only
-
-### 5. LoginPage Implementation Constraints 🔴
-- **Must refer to `TUIKit_Flutter/chat/demo/lib/login_page.dart` to implement the login page** (note path prefix)
-- **SDKAppID, UserID, UserSig must directly use the information returned by the `get_usersig` tool**
-- **Prohibited from adding UserID input box in UI**, do not allow users to actively input UserID
-- **Prohibited from adding 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 the main page (ConversationsPage or ChatPage)
-
-### 6. chat-only Mode Feature Restrictions (⚠️ Default Constraints + Exceptions When Users Actively Request)
-
-**Default Behavior**:
-When users choose chat-only mode, Agent **by default excludes** the following extended features:
-- **By default, do not integrate ConversationsPage** (conversation list page)
-- **By default, do not integrate ContactsPage** (contacts page)
-- **By default, only retain core chat page**: `ChatPage`
-
-**Exception Handling**:
-If users **explicitly request** adding certain extended features (such as "need ConversationsPage", "want to integrate contacts", etc.), Agent **should allow and execute**:
-- ✅ On the basis of core chat page, additionally integrate features explicitly requested by users
-- ✅ Only add features explicitly requested by users, do not expand other features without authorization
-- ✅ Integrate required pages correctly according to integration documentation specifications
-
-**Judgment Criteria**:
-- User requirements contain explicit feature keywords (such as "ConversationsPage", "contacts", "search", "conversation list", etc.)
-- User explicitly states the need for a certain extended feature
-
-### 7. Package Name Import Constraints 🔴
-- **The correct package name is `package:tuikit_atomic_x/atomicx.dart`**
-- **Prohibited from using the following incorrect package names**:
-  - ❌ `package:tuikit_atomic_x/tuikit_atomicx.dart`
-  - ❌ `package:tuikit_atomic_x/tuikit_atomic_x.dart`
-- **Prohibited from guessing package names**, must strictly use them according to the sample code in the integration documentation
-- All import statements must use correct package name paths
-- **When using `BaseThemeProvider.colorsOf(context)`, must use correct property names** (see Section 9 for detailed specifications)
-
-### 8. Flutter Project Specifications
-- Use Flutter >= 3.29.0, Dart >= 3.7.0, Kotlin >= 1.9 versions
-- Follow Flutter official code style and best practices
-- Configure permissions and dependencies for Android and iOS platforms according to integration documentation
-- **🌐 Special Note: All UI Text Must Be in English**
-  - **All page text, button labels, prompts, and error messages must be in English**
-  - **Prohibited from hard-coding Chinese text** (such as `'登录'`, `'发送'`, `'确认'`)
-  - **Must use `atomicLocale` for internationalization** or hard-code English text directly
-  - **Examples**:
-    - ❌ Wrong: `Text('登录')`, `label: '聊天'`
-    - ✅ Correct: `Text(atomicLocale.login)`, `label: atomicLocale.chat`, or `Text('Login')`
-- **Must configure internationalization and LocaleProvider** (mandatory requirement):
-
-**⚠️ Critical: Initialize StorageUtil Before Setting Language**
-
-To ensure `LocaleProvider()..changeLanguage('en')` takes effect properly, **must call `StorageUtil.init()` in the `main()` function** before running the app.
-
-**Why is this necessary?**
-- `LocaleProvider()..changeLanguage('en')` relies on `StorageUtil` to persist language settings
-- Without initialization, the language setting may fail due to timing issues
-- `StorageUtil.init()` is an async operation and must be awaited before `runApp()`
-
-**Complete Example (main.dart):**
-```dart
-import 'package:flutter/material.dart';
-import 'package:flutter_localizations/flutter_localizations.dart';
-import 'package:provider/provider.dart';
-import 'package:tuikit_atomic_x/atomicx.dart';
-
-// ✅ STEP 1: Initialize StorageUtil in main() function
-void main() async {
-  WidgetsFlutterBinding.ensureInitialized();
-  await StorageUtil.init();  // CRITICAL: Must be called before runApp()
-  runApp(const MyApp());
-}
-
-// ✅ STEP 2: Configure LocaleProvider in MyApp
-class MyApp extends StatelessWidget {
-  const MyApp({super.key});
-
-  @override
-  Widget build(BuildContext context) {
-    return ComponentTheme(
-      child: MultiProvider(
-        providers: [
-          ChangeNotifierProvider(
-            create: (_) => LocaleProvider()..changeLanguage('en'),  // Set default to English
-          ),
-        ],
-        child: Builder(
-          builder: (context) {
-            final localeProvider = Provider.of<LocaleProvider>(context);
-            
-            return MaterialApp(
-              title: 'TUIKit Flutter Demo',
-              theme: ThemeData(
-                colorScheme: ColorScheme.fromSeed(seedColor: Colors.blue),
-                useMaterial3: true,
-              ),
-              localizationsDelegates: const [
-                AtomicLocalizations.delegate,          // TUIKit internationalization (required)
-                GlobalMaterialLocalizations.delegate,   // Material component internationalization
-                GlobalWidgetsLocalizations.delegate,    // Widget internationalization
-                GlobalCupertinoLocalizations.delegate,  // iOS style component internationalization
-              ],
-              supportedLocales: AtomicLocalizations.supportedLocales,  // Use TUIKit supported languages
-              locale: localeProvider.locale,  // Bind current language
-              home: const LoginPage(),  // Replace with your home Widget (e.g., HomePage, LoginScreen, etc.)
-            );
-          },
-        ),
-      ),
-    );
-  }
-}
-```
-
-**pubspec.yaml must add dependencies**:
-```yaml
-dependencies:
-  flutter_localizations:
-    sdk: flutter
-  provider: ^6.0.0  # Or latest version
-```
-
-**Widget Tree Structure Requirements** (from outer to inner):
-```
-ComponentTheme                        ← Outermost layer (TUIKit theme component)
-  └─ MultiProvider                    ← Provider container
-      └─ providers: [LocaleProvider]  ← Register LocaleProvider
-          └─ Builder                  ← For obtaining context
-              └─ MaterialApp          ← Application entry
-                  ├─ localizationsDelegates  ← Internationalization delegates
-                  │   ├─ AtomicLocalizations.delegate      (TUIKit internationalization, required)
-                  │   ├─ GlobalMaterialLocalizations.delegate
-                  │   ├─ GlobalWidgetsLocalizations.delegate
-                  │   └─ GlobalCupertinoLocalizations.delegate
-                  ├─ supportedLocales  ← AtomicLocalizations.supportedLocales
-                  ├─ locale            ← localeProvider.locale (bind language)
-                  └─ home: YourHomePage   ← Home page (replace according to actual situation)
-```
-
-**⚠️ Key Points**:
-1. **Must initialize StorageUtil in main() function** (`await StorageUtil.init()` before `runApp()`)
-2. **ComponentTheme must be at the outermost layer** (wrapping MultiProvider)
-3. **Must add AtomicLocalizations.delegate** (TUIKit internationalization delegate)
-4. **supportedLocales uses `AtomicLocalizations.supportedLocales`** (not manually specified)
-5. **Use Builder + Provider.of to get LocaleProvider** (implement language switching)
-6. **Use `ChangeNotifierProvider` with `create: (_) => LocaleProvider()..changeLanguage('en')`** (set default to English)
-7. **Add `const` constructors and constant Widgets** (performance optimization)
-8. **`home` parameter adjusted according to actual needs** (see explanation below)
-9. **🌐 All custom UI text must be in English** (button labels, prompts, error messages, etc.)
-
-**📱 `home` Parameter Usage Scenarios**:
-
-| Scenario | Recommended `home` Widget | Description |
-|-----|-------------------|------|
-| Need Login | `const LoginPage()` or `const LoginScreen()` | Users not logged in first enter login page |
-| Logged-in Users | `const HomePage()` | Directly enter home page (including TabBar) |
-| Debug Testing | `const ChatPage(conversationID: 'test')` | Directly enter a chat page |
-| Onboarding | `const OnboardingPage()` | Show onboarding on first use |
-
-**💡 Common Implementation Methods**:
-
-```dart
-// Method 1: Dynamically choose home page based on login status
-home: _isLoggedIn ? const HomePage() : const LoginPage(),
-
-// Method 2: Use route guards (recommended)
-initialRoute: '/',
-routes: {
-  '/': (context) => const SplashPage(),       // Splash page determines status
-  '/login': (context) => const LoginPage(),   // Login page
-  '/home': (context) => const HomePage(),     // Home page
-},
-```
-
-### 9. BaseThemeProvider Color Property Usage Specifications 🎨
-
-**Purpose**: Ensure correct usage of `BaseThemeProvider.colorsOf(context)` properties when integrating TUIKit Flutter components, preventing common property name errors.
-
-#### ⚠️ Common Mistakes to Avoid
-
-**❌ WRONG - These properties DO NOT exist:**
-- `bgColorContainer` ❌
-- `borderColorNormal` ❌
-- `bgColorCard` ❌
-- `bgColorPage` ❌
-
-**✅ CORRECT - Use these properties instead:**
-
-#### 📋 Available Background Colors (`bgColor*`)
-
-| Property Name | Usage Scenario |
-|--------------|----------------|
-| `bgColorTopBar` | Top navigation bar background |
-| `bgColorOperate` | Main operation area background (pages, screens) |
-| `bgColorDialog` | Dialog/modal background |
-| `bgColorDialogModule` | Sub-modules within dialogs |
-| `bgColorEntryCard` | Card/entry components (✅ Use this instead of `bgColorContainer`) |
-| `bgColorFunction` | Functional area background |
-| `bgColorBottomBar` | Bottom navigation bar background |
-| `bgColorInput` | Input field background |
-| `bgColorBubbleReciprocal` | Chat bubble background (received messages) |
-| `bgColorBubbleOwn` | Chat bubble background (sent messages) |
-| `bgColorDefault` | Default background color |
-| `bgColorTagMask` | Tag mask background |
-| `bgColorElementMask` | Element mask background |
-| `bgColorMask` | General mask background |
-| `bgColorMaskDisappeared` | Disappearing mask |
-| `bgColorMaskBegin` | Initial mask state |
-| `bgColorAvatar` | Avatar background |
-
-#### 📋 Available Border/Stroke Colors
-
-| Property Name | Usage Scenario |
-|--------------|----------------|
-| `strokeColorPrimary` | Primary borders (✅ Use this instead of `borderColorNormal`) |
-| `strokeColorSecondary` | Secondary borders |
-| `strokeColorModule` | Module dividers/borders |
-
-#### 📋 Available Text Colors
-
-| Property Name | Usage Scenario |
-|--------------|----------------|
-| `textColorPrimary` | Primary text |
-| `textColorSecondary` | Secondary/hint text |
-| `textColorTertiary` | Tertiary/less important text |
-| `textColorDisable` | Disabled text |
-| `textColorButton` | Button text |
-| `textColorLink` | Link text |
-| `textColorWarning` | Warning text |
-| `textColorSuccess` | Success text |
-| `textColorError` | Error text |
-
-#### 📋 Available Button Colors
-
-| Property Name | Usage Scenario |
-|--------------|----------------|
-| `buttonColorPrimaryDefault` | Primary button default state |
-| `buttonColorPrimaryHover` | Primary button hover state |
-| `buttonColorPrimaryActive` | Primary button active state |
-| `buttonColorPrimaryDisabled` | Primary button disabled state |
-| `buttonColorSecondaryDefault` | Secondary button default state |
-| `buttonColorSecondaryHover` | Secondary button hover state |
-| `buttonColorSecondaryActive` | Secondary button active state |
-| `buttonColorSecondaryDisabled` | Secondary button disabled state |
-
-**Usage Example:**
-```dart
-// ✅ Correct usage
-Container(
-  color: BaseThemeProvider.colorsOf(context).bgColorOperate,  // For page background
-  child: Card(
-    color: BaseThemeProvider.colorsOf(context).bgColorEntryCard,  // For card background
-    shape: RoundedRectangleBorder(
-      borderRadius: BorderRadius.circular(8),
-      side: BorderSide(
-        color: BaseThemeProvider.colorsOf(context).strokeColorPrimary,  // For border
-      ),
-    ),
-  ),
-)
-
-// ❌ Wrong usage - these properties don't exist
-Container(
-  color: BaseThemeProvider.colorsOf(context).bgColorContainer,  // ❌ Error
-  decoration: BoxDecoration(
-    border: Border.all(
-      color: BaseThemeProvider.colorsOf(context).borderColorNormal,  // ❌ Error
-    ),
-  ),
-)
-```
-
-### 10. Environment Dependency Preparation
-- Ensure users have installed Flutter SDK, Android Studio, and Xcode (macOS)
-- **Flutter command execution follows the multi-level fallback strategy in Section 3**
-- iOS platform requires additional execution of `cd ios && pod install && cd ..` to install Pods dependencies
-- **If automatic execution fails, must generate fallback scripts for users to execute manually**
-
----
-
-## 🛠️ Integration Mode Distribution (Goals)
-
-According to user requirements, Agent must choose the corresponding execution path:
-
-### 1. Full-Featured Integration (full-featured)
-
-**Goal**: Implement a complete IM application similar to WeChat
-
-**Core Pages**: 
-- `ConversationsPage` (conversation list)
-- `ChatPage` (chat page)
-- `ContactsPage` (contacts)
-
-**Execution Reference**: 
-- Refer to the `integration.md` instructions obtained in real-time from tool return results
-
-**Applicable Scenarios**:
-- Build standalone chat applications
-- Need complete conversation management, address book, group management features
-- As a core functional module of mobile applications
-
-**HomePage and TabBar Implementation Requirements** (🔴 Mandatory Requirements):
-
-If the project does not have TabBar navigation, **must create HomePage as the main page**, including the following requirements:
-
-1. **Must implement bottom TabBar**:
-   - By default, includes two tabs: **Chat** (ConversationsPage) and **Contacts** (ContactsPage)
-   - Use Flutter's `BottomNavigationBar` or `TabBar` component
-   
-2. **Tab clicks must navigate to real pages**:
-   - Click "Chat" Tab → Display `ConversationsPage` (conversation list)
-   - Click "Contacts" Tab → Display `ContactsPage` (contacts list)
-   - Use `PageView`, `IndexedStack`, or route switching to implement page switching
-   
-3. **HomePage Structure Example**:
-   ```dart
-   import 'package:flutter/material.dart';
-   import 'package:tuikit_atomic_x/atomicx.dart';
-   
-   class HomePage extends StatefulWidget {
-     @override
-     _HomePageState createState() => _HomePageState();
-   }
-   
-   class _HomePageState extends State<HomePage> {
-     int _selectedIndex = 0;
-     
-     final List<Widget> _pages = [
-       ConversationsPage(),  // Conversation list
-       ContactsPage(),       // Contacts
-     ];
-     
-     void _onItemTapped(int index) {
-       setState(() {
-         _selectedIndex = index;
-       });
-     }
-     
-     @override
-     Widget build(BuildContext context) {
-       return Scaffold(
-         body: IndexedStack(
-           index: _selectedIndex,
-           children: _pages,
-         ),
-         bottomNavigationBar: BottomNavigationBar(
-           items: [
-             BottomNavigationBarItem(
-               icon: Icon(Icons.chat_bubble_outline),
-               activeIcon: Icon(Icons.chat_bubble),
-               label: atomicLocale.chat,
-             ),
-             BottomNavigationBarItem(
-               icon: Icon(Icons.contacts_outlined),
-               activeIcon: Icon(Icons.contacts),
-               label: atomicLocale.contact,
-             ),
-           ],
-           currentIndex: _selectedIndex,
-           onTap: _onItemTapped,
-         ),
-       );
-     }
-   }
-   ```
-   
-**⚠️ TabBar label Internationalization Requirements**:
-- **Must use `atomicLocale` to read Tab label text**
-- ✅ Correct usage: `label: atomicLocale.chat`, `label: atomicLocale.contact`
-- `atomicLocale` will automatically return corresponding translated text based on current language environment
-   
-**💡 TabBar Best Practices**:
-- Use `icon` and `activeIcon` to distinguish selected/unselected states
-- Use semantic icons: Chat (`Icons.chat_bubble_outline` / `Icons.chat_bubble`), Contacts (`Icons.contacts_outlined` / `Icons.contacts`)
-- Variable name `_selectedIndex` is more semantic than `_currentIndex`
-
-4. **Navigate to HomePage after successful login**:
-   ```dart
-   // LoginPage.dart
-   await LoginStore.shared.login(...);
-   Navigator.pushReplacement(
-     context,
-     MaterialPageRoute(builder: (_) => HomePage()),  // Navigate to HomePage
-   );
-   ```
-
-5. **Prohibited Behaviors**:
-   - ❌ Directly navigate to a single page after login (such as ConversationsPage) without TabBar
-   - ❌ Create empty HomePage but without actual page switching logic
-   - ❌ TabBar has only one Tab (must have at least "Chat" and "Contacts")
-
----
-
-### 2. Chat Page Only Integration (chat-only)
-
-**Goal**: Suitable for pure conversation scenarios such as customer service, consultation, detail page private chat
-
-**Core Pages**: 
-- `ChatPage` (chat page)
-
-**Execution Reference**: 
-- Refer to the `integration.md` instructions obtained in real-time from tool return results
-
-**Applicable Scenarios**:
-- Customer service consultation scenario (users click consultation button to enter chat page)
-- Online medical consultation (patient and doctor one-on-one communication)
-- Order detail page private chat (buyer and seller communication)
-- Private message feature in social applications
-
-**💡 Page Navigation After Successful Login (chat-only Mode Guidance)**:
-
-**Default Behavior**: If the user does not specifically specify, after successful login, directly navigate to `ChatPage`, opening a single chat session with `administrator`.
-
-**Flexible Adjustment**: If the user has other requirements (such as opening chat page at a specific time, specifying other conversation targets), need to confirm navigation timing and target conversation according to user guidance.
-
-**Default Implementation Example**:
-
-```dart
-// ✅ Successful login, directly enter chat page
-Navigator.pushReplacement(
-  context,
-  MaterialPageRoute(
-    builder: (context) => const ChatPage(
-      conversationID: 'c2c_administrator',  // Default single chat with administrator
-    ),
-  ),
-);
-```
-
-**⚠️ Key Points**:
-1. **Use `Navigator.pushReplacement`** (replace login page, prevent going back)
-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**: By default, navigate immediately in the successful login callback, if user has special needs (such as navigate after clicking button), need to adjust according to user guidance
-
-**🔴 Default Excluded Features (Agent Must Comply)**:
-
-When generating chat-only mode code, Agent **by default excludes** the following features and pages:
-
-1. **By default, do not integrate ConversationsPage (conversation list)**
-   - By default, do not generate conversation list page
-   - By default, do not introduce conversation switching feature
-   - Chat page by default should be an independent, direct pure chat interface
-
-2. **By default, do not integrate ContactsPage (contacts)**
-   - By default, do not generate address book page
-   - By default, do not introduce contact management feature
-
-3. **By default, do not integrate bottom navigation bar (TabBar)**
-   - In chat-only mode, users specify conversation ID through external routing/parameters
-   - By default, no need for page switching feature
-
----
-
-**⚠️ Exception Handling When Users Actively Request**:
-
-If users **explicitly request** adding certain extended features in chat-only mode, Agent **should allow and execute**:
-
-**Trigger Conditions** (satisfy any one):
-- User explicitly states: "need ConversationsPage", "want to integrate conversation list", "add conversation switching feature"
-- User explicitly states: "need ContactsPage", "want to add contacts", "integrate address book"
-- User explicitly proposes other extended feature requirements
-
-**Agent Execution Process**:
-1. ✅ **Confirm user requirements**: Recognize that users actively request adding extended features
-2. ✅ **Allow integration**: On the basis of chat-only mode, additionally integrate pages requested by users
-3. ✅ **Maintain restraint**: Only add features explicitly requested by users, do not expand other features without authorization
-4. ✅ **Follow documentation**: Integrate required pages correctly according to integration documentation specifications
-
----
-
-## 📦 Core Version Requirements
-
-| Tool/Platform | Minimum Version Requirement |
-|----------|-------------|
-| **Flutter** | >= 3.29.0 |
-| **Dart** | >= 3.7.0 |
-| **Kotlin** | >= 1.9 |
-| **Android Studio** | Ladybug \| 2024.2.1 and above |
-| **Android Gradle Plugin** | >= 7.3.1 |
-| **JDK** | 17 |
-| **Xcode** | >= 12.0 (macOS) |
-
----
-
-## 📦 Installation Command Examples
-After Agent completes code generation, must execute the following commands in order:
-
-**⚠️ Important: Flutter Command Execution Specification**
-- Must use `which flutter` to get Flutter actual installation path
-- Use full path to execute commands, avoid environment variable issues
-- Ensure execution in user project directory
-
-```bash
-# 0. Get Flutter actual path (must execute first)
-FLUTTER_PATH=$(which flutter)
-
-# 1. Clean project
-$FLUTTER_PATH clean
-
-# 2. Get dependencies
-$FLUTTER_PATH pub get
-
-# 3. iOS dependency installation (macOS only)
-cd ios && pod install && cd ..
-
-# 4. Run project (choose device or simulator)
-$FLUTTER_PATH run
-```
-
-**Command Execution Strategy**:
-- First use full path obtained from `which flutter`
-- If `which flutter` fails, try common paths:
-  - macOS/Linux: `$HOME/flutter/bin/flutter`
-  - Custom user path (read from environment variable `FLUTTER_ROOT`)
-- If all paths fail, prompt user to check Flutter installation
-
----
-
-## 📱 Real Device Debugging Guide
-
-### iOS Real Device Debugging Steps
-
-#### 1. Hardware Preparation
-- Use USB cable to connect iPhone/iPad to Mac
-- Ensure device is unlocked and trusts this computer (prompt will pop up on first connection)
-
-#### 2. Configure Developer Account
-
-**⚠️ Important: Correctly Open iOS Project**
-
-When opening iOS project with Xcode, **must** open the `Runner.xcworkspace` file (not `Runner.xcodeproj`):
-
-```bash
-open ios/Runner.xcworkspace
-```
-
-**❌ Common Errors**:
-- Do not open `ios/Runner.xcodeproj` (will cause CocoaPods dependencies to not be recognized)
-- Do not double-click `ios` folder directly
-
-**✅ Correct Approach**:
-- Execute `open ios/Runner.xcworkspace` in terminal
-- Or find `ios/Runner.xcworkspace` in Finder, double-click to open
-
-**Configure Signing**:
-
-In Xcode:
-- Select **Runner** project → **Signing & Capabilities**
-- Check **Automatically manage signing**
-- Select your **Apple ID** (Team)
-- Modify **Bundle Identifier** (must be unique, recommended format: `com.yourname.appname`)
-
-#### 3. View Connected Devices
-```bash
-FLUTTER_PATH=$(which flutter)
-$FLUTTER_PATH devices
-```
-
-Example output:
-```
-iPhone 15 Pro (mobile) • 00008110-XXXXX • ios • iOS 17.2
-```
-
-#### 4. Run on Specified Device
-```bash
-# Method 1: Use device ID
-$FLUTTER_PATH run -d 00008110-XXXXX
-
-# Method 2: Let Flutter automatically choose connected iOS device
-$FLUTTER_PATH run -d ios
-```
-
-#### 5. First Run Authorization
-- Real device first run will prompt "Untrusted Developer"
-- On iPhone: **Settings → General → VPN & Device Management → Developer App → Trust**
-- Run again `$FLUTTER_PATH run -d ios`
-
-#### 6. Common Issues
-| Issue | Solution |
-|------|----------|
-| **Signing error** | Check Team and Bundle ID configuration in Xcode |
-| **Device not recognized** | Re-plug USB cable, ensure device is unlocked |
-| **Pod installation failed** | Execute `cd ios && pod repo update && pod install && cd ..` |
-
----
-
-### Android Real Device Debugging Steps
-
-#### 1. Hardware Preparation
-- Use USB cable to connect Android device to computer
-- Ensure device is charged (recommended > 50%)
-
-#### 2. Enable Developer Mode
-On Android device:
-1. Go to **Settings → About Phone**
-2. Tap **Build Number** 7 times continuously to enable developer mode
-3. Return to **Settings → System → Developer Options**
-4. Enable **USB Debugging**
-5. After connecting to computer, device will pop up **Allow USB Debugging** prompt, tap **Allow**
-
-#### 3. Verify Device Connection
-```bash
-# Method 1: Use adb command
-adb devices
-
-# Example output:
-# List of devices attached
-# XXXXXXXX	device
-
-# Method 2: Use Flutter command
-FLUTTER_PATH=$(which flutter)
-$FLUTTER_PATH devices
-```
-
-Example output:
-```
-SM G9900 (mobile) • XXXXXXXX • android-arm64 • Android 13 (API 33)
-```
-
-#### 4. Run on Specified Device
-```bash
-# Method 1: Use device ID
-$FLUTTER_PATH run -d XXXXXXXX
-
-# Method 2: Let Flutter automatically choose connected Android device
-$FLUTTER_PATH run -d android
-```
-
-#### 5. First Build Wait
-- First run will download Gradle dependencies (may take 5-10 minutes)
-- Wait for `Installing build/app/outputs/flutter-apk/app.apk...` to complete
-- App will automatically install and launch
-
-#### 6. Common Issues
-| Issue | Solution |
-|------|----------|
-| **Device unauthorized** | Tap "Allow USB Debugging" on phone, check "Always allow" |
-| **adb devices shows unauthorized** | Re-plug USB cable, re-authorize |
-| **Gradle download slow** | Configure domestic mirror (modify `android/build.gradle`) |
-| **Device offline** | Execute `adb kill-server && adb start-server` |
-
----
-
-## 🚀 Multi-Device Simultaneous Debugging
-
-If multiple devices are connected simultaneously, use the following commands to select:
-
-```bash
-FLUTTER_PATH=$(which flutter)
-
-# View all devices
-$FLUTTER_PATH devices
-
-# Run on specified device
-$FLUTTER_PATH run -d <device-id>
-
-# Example: Run simultaneously on iOS and Android
-$FLUTTER_PATH run -d ios &
-$FLUTTER_PATH run -d android &
-```
-
----
-
-## 📊 Debugging Recommendations
-
-### Hot Reload
-After app is running, code will automatically hot reload when saved:
-- Press `r` key in terminal to manually trigger hot reload
-- Press `R` key to trigger hot restart
-- Press `q` key to exit debugging
-
-### View Logs
-```bash
-# Flutter logs
-$FLUTTER_PATH logs
-
-# Android logs
-adb logcat | grep flutter
-
-# iOS logs (requires ios-deploy)
-ios-deploy --id <device-id> --debug
-```
-
-### Performance Analysis
-```bash
-# Start performance analysis
-$FLUTTER_PATH run --profile
-
-# Start debugging tools
-$FLUTTER_PATH pub global run devtools
-```
-
----
-
-## 🔄 Complete Automation Process
-
-```mermaid
-graph TD
-    A[Receive User Requirements] --> B[Get Flutter Actual Path: which flutter]
-    B --> C[Check Flutter Environment]
-    C --> D[Enter Project Parent Directory and Clone TUIKit_Flutter]
-    D --> E[Configure pubspec.yaml According to Integration Documentation]
-    E --> F[Configure iOS Podfile According to Integration Documentation]
-    F --> G[Configure main.dart According to Integration Documentation]
-    G --> H[Call get_usersig Tool to Obtain 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[Execute Using Full Path: $FLUTTER_PATH pub get]
-    L --> M{iOS Platform?}
-    M -->|Yes| N[Execute pod install]
-    M -->|No| O[Skip pod install]
-    N --> P[Guide Users to Connect Real Device Debugging]
-    O --> P
-    P --> Q{Choose Running Method}
-    Q -->|Simulator| R[Execute: $FLUTTER_PATH run]
-    Q -->|iOS Real Device| S[Execute: $FLUTTER_PATH run -d ios]
-    Q -->|Android Real Device| T[Execute: $FLUTTER_PATH run -d android]
-    R --> U[Project Startup Successful]
-    S --> U
-    T --> U
-```
-
----
-
-## 📝 Key Points Summary
-
-| Category | Requirement |
-|------|------|
-| **Framework Version** | Flutter >= 3.29.0, Dart >= 3.7.0, Kotlin >= 1.9 |
-| **Integration Method** | Source code integration (clone from GitHub and reference through local path) |
-| **Documentation First** | ⚠️ Strictly follow sample code in integration documentation, do not modify without authorization |
-| **Storage Initialization** | 🚨 **Must call `await StorageUtil.init()` in main() before runApp()** to ensure language settings work |
-| **Core Page Source** | 🚨 **Strictly prohibited from writing core page code yourself**, must completely copy official page files from `TUIKit_Flutter/chat/uikit/lib/` |
-| **Page Integrity Verification** | ⚠️ Core page code must be > 100 lines, including complete State classes, UI component trees, business logic |
-| **Silent Integration** | Automatically install dependencies and start project after code writing is complete, **must use `which flutter` to get actual path** |
-| **Credential Acquisition** | ⚠️ Must use `get_usersig` tool to obtain test authentication information |
-| **Security Reminder** | ⚠️ Must inform users: Client-side generation of UserSig is only suitable for testing, production environment must generate on server side |
-| **Result Recording** | ⚠️ Must call `record_result` tool to record results after integration is complete |
-| **Integration Mode** | Support full-featured (full) and chat-only (chat only) modes |
-| **chat-only Restrictions** | ⚠️ By default exclude ConversationsPage, ContactsPage, SearchPage; allow integration when users actively request |
-| **Package Name Constraints** | ⚠️ Must use `package:tuikit_atomic_x/atomicx.dart`, prohibited from guessing package names |
-| **Color Scheme Properties** | ⚠️ Must use correct `BaseThemeProvider.colorsOf(context)` property names (e.g., `bgColorOperate`, `strokeColorPrimary`), prohibited from using non-existent properties |
-
----
-
-## 🎯 Agent Execution Checklist
-
-After completing code generation, Agent must confirm all the following items:
-
-### Project Initialization
-- [ ] Entered user project parent directory
-- [ ] Cloned TUIKit_Flutter repository to correct location
-- [ ] Configured `pubspec.yaml` according to integration documentation
-- [ ] Configured iOS Podfile according to integration documentation (iOS platform)
-
-### Code Generation
-- [ ] Configured `main.dart` according to integration documentation
-- [ ] 🔴 **Added `await StorageUtil.init()` in main() function before runApp()**
-- [ ] 🔴 **Added `WidgetsFlutterBinding.ensureInitialized()` before StorageUtil.init()**
-- [ ] 🔴 **Called `get_usersig` tool to obtain SDKAppID, UserID, UserSig**
-- [ ] 🔴 **Referred to `TUIKit_Flutter/chat/demo/lib/login_page.dart` to implement login page** (note path prefix)
-- [ ] 🔴 **Login page does not contain UserID, SDKAppID, UserSig input boxes**
-- [ ] Implemented login logic according to integration documentation, automatically using credentials returned by `get_usersig`
-- [ ] 🔴 **Completely copied official page files from `TUIKit_Flutter/chat/uikit/lib/`**
-- [ ] 🔴 **Core page code lines > 100 lines (verify not simplified version)**
-- [ ] 🔴 **Core pages include complete State classes, UI component trees, business logic**
-- [ ] 🔴 **Strictly prohibited from writing simplified implementations yourself, strictly prohibited from skipping page code generation**
-- [ ] 🔴 **All imports use correct package name `package:tuikit_atomic_x/atomicx.dart`**
-- [ ] 🔴 **All `BaseThemeProvider.colorsOf(context)` properties use correct names** (e.g., `bgColorOperate`, `strokeColorPrimary`, not `bgColorContainer` or `borderColorNormal`)
-- [ ] Implemented navigation logic between pages according to integration documentation
-
-### Integration Mode
-- [ ] Selected correct integration mode according to user requirements (full-featured or chat-only)
-- [ ] full-featured mode: Integrated ConversationsPage, ChatPage, ContactsPage and other pages
-- [ ] chat-only mode: Integrated core page (ChatPage)
-- [ ] chat-only mode: Judged whether extended features need to be integrated according to user requirements
-  - [ ] If user did not actively request, confirmed not to include ConversationsPage, ContactsPage, SearchPage and other pages
-  - [ ] If user actively requested (such as "need ConversationsPage"), additionally integrated features explicitly requested by user
-
-### Security and Reminders
-- [ ] 🔴 **Informed user**: 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 Check
-- [ ] 🔴 **Called `record_result` tool to record integration results**
-- [ ] 🔴 **Used `which flutter` to get Flutter actual path**
-- [ ] Executed `$FLUTTER_PATH pub get` to install dependencies (using full path)
-- [ ] Executed `pod install` (iOS platform)
-- [ ] Executed `$FLUTTER_PATH run` to start project (using full path)
-- [ ] Prompted user to choose device or simulator to run
-- [ ] Project can run normally without errors
-
----
-
-## 🔗 Tools That Must Be Used
-
-### `get_usersig` - Obtain Test Authentication Information
-**Purpose**: Obtain Tencent Cloud IM test authentication information
-- `SDKAppID`: Application identifier
-- `UserID`: User ID
-- `UserSig`: User signature
-
-**Usage Constraints**:
-- ✅ Must use `get_usersig` tool to obtain test authentication
-- ❌ Prohibited from letting users manually input or copy from console
-- ⚠️ Must inform users: Client-side generation of UserSig 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
-
-**Calling Timing**: Call after completing all integration steps and successfully starting project
-
----
-
-## 📚 Related Resource Links
-
-- **TUIKit Flutter GitHub Repository**: https://github.com/Tencent-RTC/TUIKit_Flutter
-- **Tencent Cloud Instant Messaging Chat Console**: https://console.trtc.io/chat
-- **Server-side Generation of UserSig**: https://trtc.io/document/34385
-- **Activate Chat Service**: https://trtc.io/document/45907
-- **Flutter Official Documentation**: https://flutter.dev/docs
-
----
-
-**Applicable Platform**: Flutter (Android & iOS)  
-**TUIKit Version**: tuikit_atomic_x (AtomicXCore version)  
-**Minimum Requirements**: Flutter >= 3.29.0, Dart >= 3.7.0