@cometchat/skills 4.4.1 → 5.0.0

package/skills/cometchat-android-v6-extensions/SKILL.md

@@ -1,192 +1,52 @@
 ---
 name: cometchat-android-v6-extensions
-description: "CometChat Android UIKit v6 extension architecture — DataSource/Repository pattern, custom message types, and data-layer overrides"
+description: "Turn on CometChat Dashboard extensions in an Android v6 app — stickers, polls, collaborative whiteboard and document, message translation, link preview, thumbnail generation, message shortcuts — and know exactly where each one appears in the UI once enabled (mostly zero client code). Triggers: 'enable stickers android', 'add polls to my android chat', 'message translation android cometchat', 'link previews not showing', 'what extensions does the android ui kit support'."
 license: "MIT"
-compatibility: "Android 9.0+ (API 28); Kotlin 1.9+; com.cometchat:chatuikit-core-android:6.x"
+compatibility: "Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 OR com.cometchat:chatuikit-compose-android ^6 (6.0.x, verified 6.0.5); com.cometchat:chat-sdk-android ^5"
 metadata:
   author: "CometChat"
-  version: "3.0.0"
-  tags: "cometchat, android, extensions, datasource, repository, clean-architecture"
+  version: "1.0.0"
+  tags: "cometchat android extensions v6 stickers polls translation dashboard"
 ---
 
-> **Ground truth:** `com.cometchat:chatuikit-{compose,kotlin}-android:6.x` (+ `calls-sdk-android:5.x`) — resolved AAR (javap) + `ui-kit/android/v6`. **Official docs:** https://www.cometchat.com/docs/fundamentals/extensions-overview · **Docs MCP:** `claude mcp add --transport http cometchat-docs https://www.cometchat.com/docs/mcp` (or fetch the URL directly without MCP). Verify symbols against the installed package/source before relying on them.
+> **Ground truth:** `features.android-v6.json` (the extension entries + their `enablement`) + catalog `android-v6.json` + the live page `/ui-kit/android/extensions` (the manual — 8 built-ins) and each extension's `/fundamentals/*` page. Verify symbols against the catalog; fetch details from docs; never invent an extension.
 
-> **Companion skills:** cometchat-android-v6-features (feature catalog), cometchat-android-v6-kotlin-customization, cometchat-android-v6-compose-customization
-
-## Purpose
-
-Extend the CometChat UIKit v6 data layer using the clean architecture DataSource/Repository pattern. Create custom DataSource implementations, override repository behavior, and register custom message types.
+## Companion skills (read first)
+- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, the fetch map. Assumed here, never repeated.
+- `cometchat-android-v6-features` — the general feature-lookup skill; come here for the Dashboard-extension slice specifically.
 
 ## Use this skill when
+"enable stickers/polls/whiteboard/document/translation/link preview/thumbnails", "add message shortcuts", "which extensions work with the Android UI Kit?", "I enabled it in the Dashboard but nothing shows up".
 
-- Creating a custom DataSource implementation to change how data is fetched
-- Overriding default repository behavior
-- Registering custom message types
-- Understanding the data flow from DataSource → Repository → ViewModel
-
-## Do not use this skill when
-
-- Customizing UI/bubble rendering (use `cometchat-*-customization` — that's the BubbleFactory layer)
-- Working with component APIs (use `cometchat-*-components`)
-
-## 1. Clean Architecture Overview
-
-The `chatuikit-core` module follows clean architecture with three layers:
-
-```
-┌─────────────────────────────────────────┐
-│  UI Layer (chatuikit-kotlin / compose)  │
-│  Components observe ViewModel state     │
-├─────────────────────────────────────────┤
-│  ViewModel Layer (core/viewmodel/)      │
-│  Calls use cases / repositories         │
-├─────────────────────────────────────────┤
-│  Domain Layer (core/domain/)            │
-│  Repository interfaces, Use cases       │
-├─────────────────────────────────────────┤
-│  Data Layer (core/data/)                │
-│  DataSource interfaces + impls          │
-│  Repository implementations            │
-└─────────────────────────────────────────┘
-```
-
-## 2. DataSource Pattern
+## Prerequisites & install
+Same kit + `initFromSettings → login` as `core`. **No Gradle dependency and (for the 7 auto-rendered ones) no client code** — the UI Kit detects an enabled extension after init+login and renders it in the right component.
 
-Each feature area has a DataSource interface and default implementation:
-
-```
-core/data/datasource/
-├── ConversationListDataSource.kt       (interface)
-├── ConversationListDataSourceImpl.kt   (default implementation)
-├── MessageListDataSource.kt
-├── MessageListDataSourceImpl.kt
-├── ...
-```
-
-### 2.1 All DataSource Types
-
-| DataSource | Implementation | What it provides |
+## The 8 built-ins — enable in Dashboard, appears here
+| Extension | Enable | Where it appears once enabled |
 |---|---|---|
-| `CallButtonsDataSource` | `CallButtonsDataSourceImpl` | Call button actions |
-| `CallLogsDataSource` | `CallLogsDataSourceImpl` | Call history fetching |
-| `CollaborativeDataSource` | `CollaborativeDataSourceImpl` | Document/whiteboard data |
-| `ConversationListDataSource` | `ConversationListDataSourceImpl` | Conversation list fetching |
-| `GroupMembersDataSource` | `GroupMembersDataSourceImpl` | Group member operations |
-| `GroupsDataSource` | `GroupsDataSourceImpl` | Group list fetching |
-| `MessageComposerDataSource` | `MessageComposerDataSourceImpl` | Composer actions/attachments |
-| `MessageHeaderDataSource` | `MessageHeaderDataSourceImpl` | Header data (name, status) |
-| `MessageInformationDataSource` | `MessageInformationDataSourceImpl` | Read receipts, delivery info |
-| `MessageListDataSource` | `MessageListDataSourceImpl` | Message fetching/pagination |
-| `PollDataSource` | `PollDataSourceImpl` | Poll creation/voting |
-| `ReactionListDataSource` | `ReactionListDataSourceImpl` | Reaction data |
-| `SearchDataSource` | `SearchDataSourceImpl` | Global search |
-| `StickerDataSource` | `StickerDataSourceImpl` | Sticker fetching |
-| `UsersDataSource` | `UsersDataSourceImpl` | User list fetching |
-
-### 2.2 Additional DataSource
-
-| File | Purpose |
-|---|---|
-| `MessageReceiptEventListener.kt` | Listens for receipt events at the data layer |
-
-## 3. Repository Pattern
-
-Repositories in `core/data/repository/` implement domain interfaces from `core/domain/repository/`:
-
-```
-core/data/repository/
-├── CallButtonsRepositoryImpl.kt
-├── CallLogsRepositoryImpl.kt
-├── ConversationListRepositoryImpl.kt
-├── GroupMembersRepositoryImpl.kt
-├── GroupsRepositoryImpl.kt
-├── MessageComposerRepositoryImpl.kt
-├── MessageHeaderRepositoryImpl.kt
-├── MessageInformationRepositoryImpl.kt
-├── MessageListRepositoryImpl.kt
-├── PollRepositoryImpl.kt
-├── ReactionListRepositoryImpl.kt
-├── SearchRepositoryImpl.kt
-├── StickerRepositoryImpl.kt
-├── UsersRepositoryImpl.kt
-```
-
-Each repository wraps a DataSource and adds business logic, caching, or transformation.
-
-## 4. ViewModel Layer
-
-ViewModels in `core/viewmodel/` consume repositories and expose UI state:
-
-```kotlin
-// Example: CometChatConversationsViewModel
-// - Injected via CometChatConversationsViewModelFactory
-// - Exposes StateFlow<ConversationListUIState>
-// - Calls ConversationListRepositoryImpl internally
-```
-
-ViewModel factories in `core/factory/` handle dependency injection:
-
-| Factory | ViewModel |
-|---|---|
-| `CometChatConversationsViewModelFactory` | `CometChatConversationsViewModel` |
-| `CometChatMessageListViewModelFactory` | `CometChatMessageListViewModel` |
-| `CometChatGroupsViewModelFactory` | `CometChatGroupsViewModel` |
-| `CometChatUsersViewModelFactory` | `CometChatUsersViewModel` |
-| `CometChatCallLogsViewModelFactory` | `CometChatCallLogsViewModel` |
-| `CometChatMessageComposerViewModelFactory` | `CometChatMessageComposerViewModel` |
-| `CometChatMessageHeaderViewModelFactory` | `CometChatMessageHeaderViewModel` |
-| `CometChatGroupMembersViewModelFactory` | `CometChatGroupMembersViewModel` |
-| `CometChatMessageInformationViewModelFactory` | `CometChatMessageInformationViewModel` |
-| `CometChatReactionListViewModelFactory` | `CometChatReactionListViewModel` |
-| `CometChatSearchViewModelFactory` | `CometChatSearchViewModel` |
-| `CometChatCallButtonsViewModelFactory` | `CometChatCallButtonsViewModel` |
-| `CometChatCreatePollViewModelFactory` | `CometChatCreatePollViewModel` |
-| `CometChatThreadHeaderViewModelFactory` | `CometChatThreadHeaderViewModel` |
-| `CometChatStickerKeyboardViewModelFactory` | `CometChatStickerKeyboardViewModel` |
-| `CometChatIncomingCallViewModelFactory` | `CometChatIncomingCallViewModel` |
-| `CometChatOutgoingCallViewModelFactory` | `CometChatOutgoingCallViewModel` |
-| `CometChatAIAssistantChatHistoryViewModelFactory` | `CometChatAIAssistantChatHistoryViewModel` |
-
-## 5. UI State Classes
-
-Each ViewModel exposes a sealed UI state from `core/state/`:
-
-| State Class | Used By |
-|---|---|
-| `CallLogsUIState` | Call logs |
-| `MessageListUIState` | Message list |
-| `GroupsUIState` | Groups list |
-| `UsersUIState` | Users list |
-| `GroupMembersUIState` | Group members |
-| `MessageComposerUIState` | Composer |
-| `MessageHeaderUIState` | Header |
-| `MessageInformationUIState` | Message info |
-| `ReactionListUIState` | Reactions |
-| `SearchUIState` | Search |
-| `CallButtonsUIState` | Call buttons |
-| `CreatePollUIState` | Poll creation |
-| `ThreadHeaderUIState` | Thread header |
-| `StickerKeyboardUIState` | Sticker keyboard |
-| `IncomingCallUIState` | Incoming call |
-| `OutgoingCallUIState` | Outgoing call |
-| `ChatHistoryUIState` | AI chat history |
-| `ConversationStarterUIState` | AI conversation starter |
-| `ConversationSummaryUIState` | AI conversation summary |
-| `SmartRepliesUIState` | AI smart replies |
-| `DeleteState` | Delete operations |
-| `UIState` | Base UI state |
-
-## 6. Data Flow
-
-```
-User Action → Component → ViewModel → Repository → DataSource → CometChat SDK
-                                                                      ↓
-UI Update  ← Component ← ViewModel ← StateFlow ← Repository ← SDK Response
-```
-
-## Hard rules
-
-- DataSources are the DATA layer — they fetch and mutate data. Do NOT confuse with BubbleFactory which is the UI rendering layer
-- The v5 `DataSource` decorator / `ChatConfigurator` pattern for bubble customization does NOT exist in v6 — use BubbleFactory instead (see `cometchat-*-customization`)
-- ViewModels are shared across both UI stacks (Kotlin Views and Compose) — they live in `chatuikit-core`
-- Always use the provided ViewModel factories — do not instantiate ViewModels directly
+| **Stickers** | Dashboard → Extensions | Composer (sticker keyboard → `CometChatStickerKeyboard`; sent as `CometChatStickerBubble`) |
+| **Polls** | Dashboard → Extensions | Composer action sheet (`CometChatCreatePoll`; rendered as `CometChatPollBubble`) |
+| **Collaborative Whiteboard** | Dashboard → Extensions | Composer action sheet; opens as a collaborative bubble in the list |
+| **Collaborative Document** | Dashboard → Extensions | Composer action sheet; opens as a collaborative bubble in the list |
+| **Message Translation** | Dashboard → Extensions | Message long-press/action sheet in `CometChatMessageList` |
+| **Link Preview** | Dashboard → Extensions | Automatically inside message bubbles for URLs |
+| **Thumbnail Generation** | Dashboard → Extensions | Automatically on image/video bubbles (smaller previews) |
+| **Profanity Filter** | Dashboard → Extensions | Message bubbles (censored text) — ⚠️ **LEGACY** |
+
+**Message Shortcuts** is the one extension that is NOT zero-code: enable it in the Dashboard, then implement a shortcut formatter extending `CometChatTextFormatter` — build it from the docs recipe `/ui-kit/android/shortcut-formatter-guide` (→ `cometchat-android-v6-{kotlin,compose}-customization` for the formatter mechanism).
+
+## Enablement — the whole flow
+1. **Ask which are already enabled** — per-app Dashboard state is not readable from code; never assume OFF (and never re-suggest one that's already on).
+2. **Enable in the CometChat Dashboard** → your app → Extensions → the extension. That's the actual "installation".
+3. **Re-login / restart the app** — the kit picks extensions up at init+login; a session started before you toggled won't show it.
+4. **Verify in the right place** (table above). No code change, no rebuild, for the 7 auto-rendered ones.
+5. Only if the ask is *styling* the extension's UI → `cometchat-android-v6-{kotlin,compose}-customization`.
+
+## Deprecated / superseded — don't offer these
+**Profanity Filter is LEGACY**: the extensions page still lists it, but its guide points at the legacy-docs archive. For new work steer to the **Moderation** product (`features.android-v6.json` → `moderation`, dashboard-configured rules + AI moderation) — say this plainly rather than wiring the legacy path. Anything not in the table above and not in `features.android-v6.json` does not exist for this kit: don't invent extensions (no "reactions extension" — reactions are core in v6; same for mentions).
+
+## Common pitfalls
+Writing client code for an auto-rendered extension (never needed) · hand-rolling polls/stickers UI that the kit already renders · enabling in the Dashboard but not re-logging in · expecting an extension before `init`+`login` succeed · offering Profanity Filter for new work · treating reactions/mentions as extensions (they're core in v6) · assuming an extension enabled on one app applies to another (per-app setting).
+
+## Verify it works
+No catalog/compile change is expected for the auto-rendered ones (nothing was emitted); for Message Shortcuts, compile (`./gradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`) and confirm the formatter is registered. On device, after enabling + re-login: the extension's entry point is present where the table says (composer action sheet / sticker keyboard / message action sheet / inside the bubble) and a sent artifact renders as its bubble type. Nothing showing ⇒ check init/login succeeded, then the Dashboard toggle for THIS app, then re-login — in that order.

package/skills/cometchat-android-v6-features/SKILL.md

@@ -1,154 +1,85 @@
 ---
 name: cometchat-android-v6-features
-description: "CometChat Android UIKit v6 feature catalog — AI features, reactions, polls, stickers, moderation, collaborative, and media features"
+description: "Add or enable a specific CometChat feature in an Android v6 app — receipts, typing, reactions, mentions, threads, search, polls, stickers, translation, link previews, AI smart replies / conversation starter / summary, AI agents, moderation, notification feed, campaigns — by resolving the ask to the feature oracle and taking the right enablement path (already-on vs Dashboard toggle vs Gradle package vs code wiring). Triggers: 'add search to my android chat', 'enable polls android', 'turn on smart replies android', 'add reactions android', 'is X supported in the android ui kit'."
 license: "MIT"
-compatibility: "Android 9.0+ (API 28); Kotlin 1.9+; com.cometchat:chatuikit-compose-android:6.x / com.cometchat:chatuikit-kotlin-android:6.x"
+compatibility: "Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 (XML Views) OR com.cometchat:chatuikit-compose-android ^6 (Compose) — 6.0.x, verified 6.0.5; com.cometchat:chat-sdk-android ^5"
 metadata:
   author: "CometChat"
-  version: "3.0.0"
-  tags: "cometchat, android, features, ai, reactions, polls, stickers, moderation"
+  version: "1.0.0"
+  tags: "cometchat android features v6 enablement extensions ai search compose views"
 ---
 
-> **Ground truth:** `com.cometchat:chatuikit-{compose,kotlin}-android:6.x` + `packages/registry/v6/features/catalog.json`. (Official docs linked below.) Verify symbols against the installed package/source before relying on them.
+> **Ground truth:** `features.android-v6.json` (the feature-existence + enablement oracle) + catalog `android-v6.json` + the live feature pages (`core-features`, `extensions`, `ai-features`, `call-features`, the `guide-*` recipes). A feature not in the oracle does NOT exist for this kit — say so; never invent one. Fetch component params from docs (`core` → `references/docs-map.md`).
 
-> **Companion skills:** cometchat-android-v6-kotlin-components, cometchat-android-v6-compose-components, cometchat-android-v6-extensions (DataSource pattern), cometchat-android-v6-events, **cometchat-android-v6-calls** (voice/video calling enablement — recording is a paid add-on)
-
-## Purpose
-
-Catalog of all features available in CometChat UIKit v6, how they map to components and DataSources, and how to enable/disable them.
+## Companion skills (read first)
+- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, hot-path callbacks, the fetch map. Assumed here, never repeated.
+- Deeper slices: `cometchat-android-v6-extensions` (the 8 Dashboard extensions in detail) · `cometchat-android-v6-calls` (voice/video) · `cometchat-android-v6-push` (FCM) · `cometchat-android-v6-{kotlin,compose}-customization` (styling a feature's UI).
 
 ## Use this skill when
-
-- Enabling or disabling specific features (AI, reactions, polls, stickers)
-- Understanding what features are available out of the box
-- Mapping a feature to its component and DataSource
-
-## Do not use this skill when
-
-- Working with component APIs directly (use `cometchat-*-components`)
-- Customizing bubble rendering (use `cometchat-*-customization`)
-
-## 0. Feature categories — what work each needs
-
-> **Canonical public feature-availability matrix:** [Features & Extensions Guide](https://www.cometchat.com/docs/fundamentals/features-and-extensions-guide) — the authoritative source for which integration method (UI Kit / UI Kit Builder / Widget Builder / SDK) supports each feature + dashboard setup + whether code is required. It **outranks the local `catalog.json` snapshot on conflict**; consult it (WebFetch or docs MCP) for any availability decision.
-
-
-Before enabling anything, classify the feature by the product's 5-category "work needed" model:
-
-| Category | Work needed | Example |
-|---|---|---|
-| **Core (zero-setup)** | Nothing — renders out of the box | Typing indicators, reactions |
-| **Builder-enabled** | Dashboard API + toggle in the UI Kit Builder | Polls |
-| **Config-only** | Dashboard API enable; works automatically | Link preview |
-| **Config + settings** | Dashboard API + extra settings (API keys, thresholds) — no code | Smart replies (OpenAI key) |
-| **SDK-integrated** | Dashboard API + **custom client code** | Bitly |
-
-**Key rule:** only **SDK-integrated** features need client code — and **the implementation lives in the docs** (`cometchat features info <id> --json` shows what's needed; fetch + adapt the doc code, don't hand-roll). Everything else is enable-and-done.
-
-**Honest-automation boundary (what the CLI can vs can't do):**
-- **Extensions** (polls, link-preview, message-translation, reactions, etc.) → `cometchat apply-feature <id> --app-id <your-app-id>` makes the **real dashboard API call** to flip the toggle. No browser visit, no code. Never tell the user to "open the dashboard and toggle it" for an extension.
-- **AI features** → `cometchat apply-feature <id> --app-id <X> --openai-key sk-...` (sets the key, then enables) — see §1.
-- **Third-party dashboard-only features** (Giphy, Stipop, Tenor, Chatwoot, Intercom, Disappearing Messages, Message Shortcuts) → the CLI returns `manual-action-required` and prints the dashboard path. These need **your** third-party credentials and **cannot be automated** — state that honestly.
-- **Calls** → see `cometchat-android-v6-calls`. **Call recording is a paid plan add-on** — there is no dashboard toggle / CLI call to enable it; the user must contact CometChat support. Never claim recording was "enabled."
-
-## 1. AI Features
-
-AI features need an OpenAI API key on the app's AI settings. Enable each one with the CLI in stateless mode (Android projects don't write `.cometchat/state.json`):
-
-```bash
-cometchat apply-feature smart-replies --app-id <your-app-id> --openai-key sk-...
-cometchat apply-feature conversation-summary --app-id <your-app-id>
-cometchat apply-feature conversation-starter --app-id <your-app-id>
-```
-
-The OpenAI key is stored on the app once, so subsequent ai-feature applies don't need `--openai-key` repeated. Requires `cometchat auth login` once per machine.
-
-| Feature | Compose Component | Core DataSource | Description |
-|---|---|---|---|
-| AI Assistant Chat History | `CometChatAIAssistantChatHistory` | — | Shows AI bot conversation history |
-| AI Conversation Starter | Shared element in `presentation/shared/aiconversationstarter/` | — | Suggests conversation starters |
-| AI Conversation Summary | Shared element in `presentation/shared/aiconversationsummary/` | — | Summarizes long conversations |
-| AI Smart Replies | Shared element in `presentation/shared/aismartreplies/` | — | Suggests contextual replies |
-
-AI features integrate with `CometChatMessageList` via the `smartRepliesView` slot and AI-specific parameters.
-
-The `CometChatAIStreamService` in `chatuikit-core` handles streaming AI responses.
-
-## 2. Reactions
-
-| Feature | Component | DataSource | Description |
-|---|---|---|---|
-| Reaction List | `CometChatReactionList` | `ReactionListDataSource` | Shows who reacted with what |
-| Add Reaction | Shared element in `presentation/shared/reaction/` | — | Emoji picker for adding reactions |
-
-Reactions appear in the **footer slot** of message bubbles. Reaction events flow through `CometChatEvents.messageEvents`.
-
-## 3. Polls
-
-| Feature | Component | DataSource | Description |
-|---|---|---|---|
-| Create Poll | `CometChatCreatePoll` (Compose) | `PollDataSource` | Create a new poll |
-| Poll Bubble | Shared element in `presentation/shared/` | `PollDataSourceImpl` | Renders poll in message list |
-
-Polls are custom messages with type `extension_poll`. The `PollRepositoryImpl` handles vote submission.
-
-## 4. Stickers
-
-| Feature | Component | DataSource | Description |
-|---|---|---|---|
-| Sticker Keyboard | `CometChatStickerKeyboard` | `StickerDataSource` | Browse and send stickers |
-| Sticker Bubble | `stickerbubble/` (Kotlin Views) | `StickerDataSourceImpl` | Renders sticker in message list |
-
-Stickers integrate with `CometChatMessageComposer` as an auxiliary input.
-
-## 5. Moderation
-
-| Feature | Component | Description |
-|---|---|---|
-| Report/Flag Message | `CometChatFlagMessageDialog` (Views) / `CometChatFlagMessageDialog` (Compose) | Report inappropriate messages |
-
-Moderation views appear in the **bottom slot** of message bubbles when moderation is enabled.
-
-## 6. Collaborative Features
-
-| Feature | DataSource | Description |
-|---|---|---|
-| Collaborative Document | `CollaborativeDataSource` | Real-time document editing |
-| Collaborative Whiteboard | `CollaborativeDataSourceImpl` | Real-time whiteboard |
-
-## 7. Media Features
-
-| Feature | Component | Description |
+"add `<feature>` to my Android chat", "enable `<feature>`", "does the Android UI Kit support `<X>`?", "why isn't `<feature>` showing up?". The job: resolve the ask against the oracle, take the right enablement branch, wire only what needs wiring, and tell the user honestly what it needs (Dashboard? package? code?).
+
+## Prerequisites & install
+Same kit + `initFromSettings → login` gate as `core`. Some features add a Gradle artifact (calls, push) or need a Dashboard toggle — the branch below says which.
+
+## Feature lookup — resolve the ask, then branch
+1. **Find the id** in `features.android-v6.json` (table below). No match ⇒ the kit has no built-in for it: check whether the **Chat SDK** covers it (`core/references/docs-map.md` → SDK section) and say plainly that there's no UI-Kit component.
+2. **Read `enablement`** and take exactly one branch:
+   - **`auto`** — already ON in v6. Do NOT "add" it; confirm it's there and offer to *customize* it (`cometchat-android-v6-{kotlin,compose}-customization`). Applies to reactions, mentions, receipts, typing, presence, quoted replies, rich text, media, mark-as-unread, report.
+   - **`dashboard-toggle` / `dashboard-extension`** — enable it in the **CometChat Dashboard**; the kit auto-integrates it after `init`+`login`, **no client code**. Your job: tell the user exactly where it will appear (composer action sheet, message list, bubble) and how to verify. Ask which are already enabled — you cannot read per-app Dashboard state.
+   - **`gradle-package`** — add the artifact, then wire (calls: `com.cometchat:calls-sdk-android` + `uiKit.enableCalling` in `assets/cometchat-settings.json`; push: `com.cometchat:push-notifications-android` + Firebase). Route to the dedicated skill.
+   - **`code-prop`** — the kit ships the component/affordance but the HOST wires it (a screen, a callback, a formatter). This is real work: build it, wire the round-trip, verify.
+   - **`dashboard-only`** — no client code at all (moderation, campaigns); explain the effect users will see.
+3. **Check `needs_stitching` (⚙ below)** — a default-ON affordance that dead-ends until you wire a destination (or hide it). Wire it or hide it; never leave it inert.
+4. **Guide-first**: if the docs ship a `guide-*` recipe for this feature (see `core/references/docs-map.md` → "Task guides"), BUILD FROM the guide, then DIFF your implementation against it, then apply the hardening deltas (credentials via the settings file, init→login gate, thread targets, IME/insets sizing, listener teardown).
+5. **Wire the feature's `ui_components`** — fetch exact params for YOUR cohort from the component page's `.md` twin.
+
+## Feature table (BAKED from `features.android-v6.json` — ⚙ = needs stitching)
+| Feature id | Enablement | Components |
 |---|---|---|
-| Image Viewer | `CometChatImageViewerScreen` (Compose) | Full-screen image viewing with zoom |
-| Media Recorder | Shared element in `presentation/shared/mediarecorder/` | Audio/video recording |
-| Inline Audio Recorder | Shared element in `presentation/shared/inlineaudiorecorder/` | In-composer audio recording |
-| Media Selection | Shared element in `presentation/shared/mediaselection/` | Photo/video picker |
-
-## 8. Feature-to-DataSource Mapping
-
-All DataSources live in `chatuikit-core/data/datasource/`:
-
-| DataSource Interface | Implementation | Feature Area |
-|---|---|---|
-| `CallButtonsDataSource` | `CallButtonsDataSourceImpl` | Audio/video call buttons |
-| `CallLogsDataSource` | `CallLogsDataSourceImpl` | Call history |
-| `CollaborativeDataSource` | `CollaborativeDataSourceImpl` | Documents/whiteboards |
-| `ConversationListDataSource` | `ConversationListDataSourceImpl` | Conversation list |
-| `GroupMembersDataSource` | `GroupMembersDataSourceImpl` | Group member management |
-| `GroupsDataSource` | `GroupsDataSourceImpl` | Group list |
-| `MessageComposerDataSource` | `MessageComposerDataSourceImpl` | Message input |
-| `MessageHeaderDataSource` | `MessageHeaderDataSourceImpl` | Chat header |
-| `MessageInformationDataSource` | `MessageInformationDataSourceImpl` | Message info/receipts |
-| `MessageListDataSource` | `MessageListDataSourceImpl` | Message list |
-| `PollDataSource` | `PollDataSourceImpl` | Polls |
-| `ReactionListDataSource` | `ReactionListDataSourceImpl` | Reactions |
-| `SearchDataSource` | `SearchDataSourceImpl` | Global search |
-| `StickerDataSource` | `StickerDataSourceImpl` | Stickers |
-| `UsersDataSource` | `UsersDataSourceImpl` | User list |
-
-## Hard rules
-
-- AI features require dashboard configuration — they cannot be enabled purely from client code
-- Polls and stickers are custom message types — they require the corresponding extensions enabled on the dashboard
-- Do NOT confuse DataSources (data layer in core) with BubbleFactory (UI layer in kotlin/compose) — DataSources fetch data, BubbleFactories render bubbles
+| `text-messaging` | auto | CometChatMessageList, CometChatMessageComposer |
+| `media-file-attachments` | auto | CometChatMessageComposer, CometChatMessageList |
+| `delivery-read-receipts` | auto | CometChatMessageList, CometChatReceipts, CometChatConversations |
+| `mark-as-unread` | auto | CometChatConversations |
+| `typing-indicators` | auto | CometChatMessageList, CometChatConversations |
+| `user-presence` | auto | CometChatConversations, CometChatMessageHeader, CometChatStatusIndicator |
+| `reactions` | auto | CometChatMessageList |
+| `mentions` | auto | CometChatMessageComposer, CometChatMessageList, CometChatMentionsFormatter |
+| `rich-text-formatting` | auto | CometChatMessageComposer, CometChatRichTextFormatter |
+| `quoted-replies` | auto | CometChatMessageList, CometChatMessageComposer |
+| `users-groups` | auto | CometChatUsers, CometChatGroups, CometChatGroupMembers |
+| `report-message` | auto | CometChatMessageList |
+| `threaded-replies` | code-prop ⚙ | CometChatMessageList, CometChatThreadHeader, CometChatMessageComposer |
+| `message-search` | code-prop ⚙ | CometChatSearch |
+| `custom-message-types` | code-prop | CometChatMessageList |
+| `text-formatters` | code-prop | CometChatTextFormatter, CometChatMentionsFormatter, CometChatRichTextFormatter |
+| `notification-feed` | code-prop | CometChatNotificationFeed |
+| `stickers` | dashboard-extension | CometChatMessageComposer, CometChatStickerBubble, CometChatStickerKeyboard |
+| `polls` | dashboard-extension | CometChatMessageComposer, CometChatCreatePoll, CometChatPollBubble |
+| `collaborative-whiteboard` | dashboard-extension | CometChatMessageComposer, CometChatMessageList |
+| `collaborative-document` | dashboard-extension | CometChatMessageComposer, CometChatMessageList |
+| `message-translation` | dashboard-extension | CometChatMessageList |
+| `link-preview` | dashboard-extension | CometChatMessageList |
+| `thumbnail-generation` | dashboard-extension | CometChatMessageList |
+| `message-shortcuts` | dashboard-extension ⚙ | CometChatTextFormatter |
+| `profanity-filter` | dashboard-extension **LEGACY** | CometChatMessageList |
+| `smart-reply` | dashboard-toggle | CometChatMessageComposer |
+| `conversation-starter` | dashboard-toggle | CometChatMessageList |
+| `conversation-summary` | dashboard-toggle | CometChatMessageComposer |
+| `ai-assistant` | dashboard-toggle ⚙ | CometChatAIAssistantChatHistory, CometChatAIAssistantBubble, CometChatMessageList, CometChatMessageComposer |
+| `moderation` | dashboard-only | — (dashboard rules; no client code) |
+| `campaigns` | dashboard-only | — (authored in Dashboard) |
+| `voice-video-calls` | gradle-package ⚙ | CometChatCallButtons, CometChatIncomingCall, CometChatOutgoingCall, CometChatCallLogs, CometChatCallActivity |
+| `push-notifications` | gradle-package ⚙ | — (SDK token registration + FCM) |
+
+## Enablement rules that trip people up
+- **`reactions` and `mentions` are ON BY DEFAULT in v6** (core messaging). Never offer to "add" or "enable" them — if asked, say they're already on and offer to customize them.
+- **`profanity-filter` is LEGACY** — its guide points at legacy docs; steer to **`moderation`** instead. Never suggest it as a new feature.
+- **Dashboard-gated ≠ broken**: if a toggled feature doesn't appear, the usual cause is the Dashboard toggle or a stale session — re-login after enabling.
+- **Pinned messages / saved messages / thread subscription** are NOT in the current v6 docs set (they're pending on a docs branch). Don't claim them; say they're not documented for v6 yet and offer the SDK path if one exists.
+- A feature's UI appears **only after `init` + `login` succeed** — a "missing feature" is often an init/login failure (`core/references/troubleshooting.md`).
+
+## Common pitfalls
+Suggesting an `auto` feature as new work · hand-rolling a feature the kit auto-renders (translation, previews, stickers) · wiring a `code-prop` feature's entry point but no way back (dead-end) · a thread screen missing the `user`/`group` target (replies silently don't send) · assuming Dashboard state instead of asking · adding the calls/push artifact without the Dashboard side · guessing component params instead of fetching.
+
+## Verify it works
+Every symbol you emitted is in the catalog (Tier-1) and the app compiles (`./gradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`). On device: the feature's UI appears where the docs say (composer action sheet / message list / bubble / its own screen); a stitched feature round-trips (open AND back); an `auto` feature was left alone; anything requiring the Dashboard was called out explicitly to the user with where-to-click. If it doesn't show, check init/login, then the Dashboard toggle, then re-login — in that order.