@cometchat/skills 4.4.2 → 5.0.1

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

@@ -1,131 +0,0 @@
----
-name: cometchat-android-v5-features
-description: "Add features (calls, reactions, polls, file sharing, AI, etc.) to an already-integrated CometChat project. Routes to the right sub-flow based on feature type."
-license: "MIT"
-compatibility: "Android 7.0+; Java 8+; Kotlin 1.8+; com.cometchat:chat-uikit-android:5.x"
-metadata:
-  author: "CometChat"
-  version: "3.0.0"
-  tags: "cometchat android features extensions calls reactions polls ai-features"
----
-
-> **Ground truth:** `com.cometchat:chat-uikit-android:5.x` (legacy/maintenance-only; +`calls-sdk-android:5.x`) — resolved AAR (javap) + `ui-kit/android`. **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.
-
-> **Companion skills:** `cometchat-android-v5-core` covers initialization;
-> `cometchat-android-v5-customization` covers deeper component customization;
-> `cometchat-android-v5-extensions` covers the extension architecture.
-
-## Purpose
-
-This skill teaches how CometChat features are structured and what work is required to enable each one. Most features require zero code — they are either already built into the UI Kit, toggled via the `cometchat apply-feature` CLI (extensions + AI features), or activated by adding a dependency (calls).
-
----
-
-## Use this skill when
-
-- "Add reactions to my chat"
-- "Add video calling"
-- "Enable polls"
-- "Add file sharing"
-- "Enable smart replies"
-
-## Do not use this skill when
-
-- Customizing how a feature looks → use `cometchat-android-v5-customization`
-- Setting up the initial integration → use `cometchat-android-v5-core`
-
----
-
-## 1. Feature types
-
-| Type | What it means | Action required |
-|---|---|---|
-| Type 1 — Default | Built into the UI Kit at compile time | None — already there |
-| Type 2a — Extension | Backend extension, pure boolean toggle | `cometchat apply-feature <id> --app-id <X>` (CLI hits dashboard API) |
-| Type 2b — AI feature | Backend AI feature requiring an OpenAI key | `cometchat apply-feature <id> --app-id <X> --openai-key sk-...` |
-| Type 2c — Dashboard-only | Third-party API key / multi-field config (Giphy, Stipop, Tenor, Chatwoot, Intercom) | Open https://app.cometchat.com → Chat & Messaging → Features → configure |
-| Type 3 — Package-install | Requires a separate SDK dependency | Add Gradle dependency |
-| Type 4 — Component-toggle | Hide/show via `setHide*` / `disable*` methods on the relevant component | Call the setter on the component instance (see catalog) |
-
----
-
-## 2. Type 1 — Default features (already enabled)
-
-| Feature | Component | Notes |
-|---|---|---|
-| Text messaging | `CometChatMessageComposer` + `CometChatMessageList` | Core feature |
-| Media sharing (image/video/audio/file) | `CometChatMessageComposer` | Attachment button |
-| Read receipts | `CometChatMessageList` | `setReceiptsVisibility()` |
-| Typing indicators | `CometChatMessageList` + `CometChatConversations` | Auto-enabled |
-| User presence (online/offline) | `CometChatConversations`, `CometChatUsers` | Requires `subscribePresenceForAllUsers()` in init |
-| Reactions | `CometChatMessageList` | Long-press message → react |
-| Mentions (@user, @all) | `CometChatMessageComposer` | Type `@` to trigger |
-| Threaded conversations | `CometChatMessageList` | `setReplyInThreadOptionVisibility()` |
-| Quoted replies | `CometChatMessageList` | Swipe to reply |
-| Edit/delete messages | `CometChatMessageList` | Long-press options |
-| Group chat | All components | Use `setGroup()` instead of `setUser()` |
-| Report message | `CometChatMessageList` | Long-press → Report |
-| Search | `CometChatSearch` | Standalone component |
-
----
-
-## 3. Type 2 — Backend toggle features (no code needed)
-
-Android projects don't run `cometchat apply`, so call the CLI in stateless mode with `--app-id`:
-
-```bash
-# Pure boolean extensions:
-cometchat apply-feature polls --app-id <your-app-id>
-cometchat apply-feature stickers --app-id <your-app-id>
-
-# AI features (require OpenAI key):
-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>
-```
-
-Requires `cometchat auth login` once per machine.
-
-**Extensions (CLI-toggleable — pure boolean):**
-- User Engagement: Polls, Message Translation, Reminders
-- Collaboration: Collaborative Document, Collaborative Whiteboard
-- Security: Disappearing Messages, E2E Encryption (Enterprise)
-- Moderation: Profanity Filter, Image Moderation, Data Masking, Sentiment Analysis, XSS Filter
-
-**AI Features (CLI-toggleable — needs `--openai-key`):**
-Conversation Starter, Conversation Summary, Smart Reply
-
-**Dashboard-only (third-party config — open https://app.cometchat.com → Chat & Messaging → Features):**
-Stickers (Stipop), Giphy, Tenor, Chatwoot, Intercom — these require API keys / webhooks the user must enter manually.
-
----
-
-## 4. Type 3 — Package-install features
-
-### Voice/Video Calling
-
-Add the calling SDK:
-
-```groovy
-implementation 'com.cometchat:calls-sdk-android:5.+'
-```
-
-The UI Kit auto-detects the calling SDK and enables call buttons in `CometChatMessageHeader`. No additional code needed — `CometChatIncomingCall`, `CometChatOutgoingCall`, and `CometChatOngoingCall` activate automatically.
-
-Configure call buttons visibility:
-
-```java
-CometChatMessageHeader header = findViewById(R.id.header);
-header.setVoiceCallButtonVisibility(View.VISIBLE);
-header.setVideoCallButtonVisibility(View.VISIBLE);
-```
-
----
-
-## Hard rules
-
-- **Don't write code for Type 1 features.** They're already there. Tell the user where to find them.
-- **Don't write code for Type 2a/2b features.** Run `cometchat apply-feature <id> --app-id <X>` (extension) or `... --openai-key sk-...` (ai-feature). The CLI flips the dashboard toggle via API. Never tell the user to "open the dashboard and toggle X" for an extension or ai-feature — that's what the CLI does.
-- **For Type 2c (dashboard-only) features**, the CLI cannot automate (third-party keys / multi-field config). Walk the user through the dashboard path returned by `cometchat apply-feature <id>`'s `manual-action-required` response.
-- **For Type 3 (calls), just add the Gradle dependency.** The UI Kit handles the rest.
-- **Always run `cometchat apply-feature <id>` first** for extensions and AI features. If the user reports a "missing feature," it's almost always an unflipped toggle the CLI can fix in one call.

package/skills/cometchat-android-v5-placement/SKILL.md

@@ -1,277 +0,0 @@
----
-name: cometchat-android-v5-placement
-description: "Where to put CometChat in your Android app — Activity, Fragment, BottomSheet, Dialog, Tab, or embedded patterns."
-license: "MIT"
-compatibility: "Android 7.0+; Java 8+; Kotlin 1.8+; com.cometchat:chat-uikit-android:5.x"
-metadata:
-  author: "CometChat"
-  version: "3.0.0"
-  tags: "chat cometchat android placement activity fragment bottomsheet dialog tabs integration"
----
-
-> **Ground truth:** `com.cometchat:chat-uikit-android:5.x` (legacy/maintenance-only) views + `docs/ui-kit/android`. **Official docs:** https://www.cometchat.com/docs/ui-kit/android/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.
-
-> **Companion skills:** `cometchat-android-v5-core` covers init and login;
-> `cometchat-android-v5-components` provides the component catalog.
-
-## Purpose
-
-This skill teaches WHERE to put CometChat in an existing Android project. It covers six placement patterns: dedicated Activity, Fragment, BottomSheet, Dialog, Tab/ViewPager, and embedded view. Each pattern includes step-by-step instructions and code examples in both Java and Kotlin.
-
----
-
-## Use this skill when
-
-- Integrating CometChat into an existing Android app
-- Deciding between Activity vs Fragment vs BottomSheet
-- "Where should I put the chat screen?"
-- "How do I add chat as a tab?"
-- "How do I show chat in a bottom sheet?"
-
-## Do not use this skill when
-
-- Setting up init/login → use `cometchat-android-v5-core`
-- Looking up component APIs → use `cometchat-android-v5-components`
-- Customizing appearance → use `cometchat-android-v5-theming`
-
----
-
-## 1. Placement recommendation
-
-| User intent | Recommended placement | Why |
-|---|---|---|
-| Messaging app | Dedicated Activity with bottom tabs | Full-screen chat experience |
-| Marketplace | Chat button → new Activity | Separate context from product browsing |
-| SaaS / dashboard | Fragment in existing Activity | Chat alongside other features |
-| Social / community | ViewPager + BottomNav tabs | Multi-section messenger |
-| Support / helpdesk | BottomSheet overlay | Non-intrusive, dismissible |
-| Quick reply | Dialog | Lightweight, modal |
-| Embedded widget | View in existing layout | Inline chat within a screen |
-
----
-
-## 2. Pattern A — Dedicated Activity
-
-The simplest and most common pattern. A full-screen Activity for the message view.
-
-**MessagesActivity layout (`activity_messages.xml`):**
-```xml
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical">
-
-    <com.cometchat.chatuikit.messageheader.CometChatMessageHeader
-        android:id="@+id/header"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content" />
-
-    <com.cometchat.chatuikit.messagelist.CometChatMessageList
-        android:id="@+id/messageList"
-        android:layout_width="match_parent"
-        android:layout_height="0dp"
-        android:layout_weight="1" />
-
-    <com.cometchat.chatuikit.messagecomposer.CometChatMessageComposer
-        android:id="@+id/composer"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content" />
-</LinearLayout>
-```
-
-**Java:**
-```java
-public class MessagesActivity extends AppCompatActivity {
-    @Override
-    protected void onCreate(Bundle savedInstanceState) {
-        super.onCreate(savedInstanceState);
-        setContentView(R.layout.activity_messages);
-
-        CometChatMessageHeader header = findViewById(R.id.header);
-        CometChatMessageList messageList = findViewById(R.id.messageList);
-        CometChatMessageComposer composer = findViewById(R.id.composer);
-
-        String uid = getIntent().getStringExtra("uid");
-        String guid = getIntent().getStringExtra("guid");
-
-        if (uid != null) {
-            CometChat.getUser(uid, new CometChat.CallbackListener<User>() {
-                @Override
-                public void onSuccess(User user) {
-                    header.setUser(user);
-                    messageList.setUser(user);
-                    composer.setUser(user);
-                }
-                @Override
-                public void onError(CometChatException e) { }
-            });
-        } else if (guid != null) {
-            CometChat.getGroup(guid, new CometChat.CallbackListener<Group>() {
-                @Override
-                public void onSuccess(Group group) {
-                    header.setGroup(group);
-                    messageList.setGroup(group);
-                    composer.setGroup(group);
-                }
-                @Override
-                public void onError(CometChatException e) { }
-            });
-        }
-
-        header.setBackIconVisibility(View.VISIBLE);
-        header.setOnBackPress(() -> finish());
-    }
-}
-```
-
-**Kotlin:**
-```kotlin
-class MessagesActivity : AppCompatActivity() {
-    override fun onCreate(savedInstanceState: Bundle?) {
-        super.onCreate(savedInstanceState)
-        setContentView(R.layout.activity_messages)
-
-        val header = findViewById<CometChatMessageHeader>(R.id.header)
-        val messageList = findViewById<CometChatMessageList>(R.id.messageList)
-        val composer = findViewById<CometChatMessageComposer>(R.id.composer)
-
-        val uid = intent.getStringExtra("uid")
-        val guid = intent.getStringExtra("guid")
-
-        when {
-            uid != null -> CometChat.getUser(uid, object : CometChat.CallbackListener<User>() {
-                override fun onSuccess(user: User) {
-                    header.setUser(user)
-                    messageList.setUser(user)
-                    composer.setUser(user)
-                }
-                override fun onError(e: CometChatException) { }
-            })
-            guid != null -> CometChat.getGroup(guid, object : CometChat.CallbackListener<Group>() {
-                override fun onSuccess(group: Group) {
-                    header.setGroup(group)
-                    messageList.setGroup(group)
-                    composer.setGroup(group)
-                }
-                override fun onError(e: CometChatException) { }
-            })
-        }
-
-        header.setBackIconVisibility(View.VISIBLE)
-        header.setOnBackPress { finish() }
-    }
-}
-```
-
----
-
-## 3. Pattern B — Fragment
-
-Embed chat in a Fragment within an existing Activity. Useful for SaaS apps or multi-pane layouts.
-
-**Java:**
-```java
-public class ChatFragment extends Fragment {
-    @Override
-    public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
-        View view = inflater.inflate(R.layout.fragment_chat, container, false);
-
-        CometChatConversations conversations = view.findViewById(R.id.conversations);
-        conversations.setOnItemClick((v, position, conversation) -> {
-            // Navigate to messages — either replace fragment or start Activity
-        });
-
-        return view;
-    }
-}
-```
-
-**Kotlin:**
-```kotlin
-class ChatFragment : Fragment() {
-    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View {
-        val view = inflater.inflate(R.layout.fragment_chat, container, false)
-
-        val conversations = view.findViewById<CometChatConversations>(R.id.conversations)
-        conversations.setOnItemClick { v, position, conversation ->
-            // Navigate to messages — either replace fragment or start Activity
-        }
-
-        return view
-    }
-}
-```
-
----
-
-## 4. Pattern C — BottomSheet
-
-Show chat as a bottom sheet overlay. Good for support/helpdesk.
-
-**Java:**
-```java
-BottomSheetDialog bottomSheet = new BottomSheetDialog(this);
-View view = getLayoutInflater().inflate(R.layout.bottom_sheet_chat, null);
-
-CometChatMessageList messageList = view.findViewById(R.id.messageList);
-CometChatMessageComposer composer = view.findViewById(R.id.composer);
-
-messageList.setUser(user);
-composer.setUser(user);
-
-bottomSheet.setContentView(view);
-bottomSheet.show();
-```
-
-**Kotlin:**
-```kotlin
-val bottomSheet = BottomSheetDialog(this)
-val view = layoutInflater.inflate(R.layout.bottom_sheet_chat, null)
-
-val messageList = view.findViewById<CometChatMessageList>(R.id.messageList)
-val composer = view.findViewById<CometChatMessageComposer>(R.id.composer)
-
-messageList.setUser(user)
-composer.setUser(user)
-
-bottomSheet.setContentView(view)
-bottomSheet.show()
-```
-
----
-
-## 5. Pattern D — Bottom Navigation Tabs
-
-Full messenger with Conversations, Users, Groups, and Calls as tabs.
-
-**Java:**
-```java
-binding.bottomNavigationView.setOnItemSelectedListener(item -> {
-    Fragment fragment;
-    int id = item.getItemId();
-    if (id == R.id.nav_chats) {
-        fragment = new ChatsFragment();      // Contains CometChatConversations
-    } else if (id == R.id.nav_users) {
-        fragment = new UsersFragment();      // Contains CometChatUsers
-    } else if (id == R.id.nav_groups) {
-        fragment = new GroupsFragment();     // Contains CometChatGroups
-    } else if (id == R.id.nav_calls) {
-        fragment = new CallsFragment();      // Contains CometChatCallLogs
-    } else {
-        return false;
-    }
-    getSupportFragmentManager().beginTransaction()
-        .replace(R.id.fragment_container, fragment)
-        .commit();
-    return true;
-});
-```
-
----
-
-## Hard rules
-
-- **Always set `User` or `Group` on message components.** `CometChatMessageList`, `CometChatMessageComposer`, and `CometChatMessageHeader` require either `setUser()` or `setGroup()` — never both, never neither.
-- **Fetch the `User`/`Group` object before setting it.** Use `CometChat.getUser(uid)` or `CometChat.getGroup(guid)` — don't construct objects manually.
-- **Set back icon visibility on `CometChatMessageHeader`.** The method is `setBackIconVisibility()`. Default is `GONE`. Set to `VISIBLE` when the user needs to navigate back.
-- **Register the Activity in `AndroidManifest.xml`.** Every new Activity needs a manifest entry.

package/skills/cometchat-android-v5-production/SKILL.md

@@ -1,95 +0,0 @@
----
-name: cometchat-android-v5-production
-description: "Production readiness for CometChat Android — server-side token auth, user management CRUD, ProGuard rules, and security checklist."
-license: "MIT"
-compatibility: "Android 7.0+; Java 8+; Kotlin 1.8+; com.cometchat:chat-uikit-android:5.x"
-metadata:
-  author: "CometChat"
-  version: "3.0.0"
-  tags: "cometchat android production auth token security user-management proguard"
----
-
-> **Ground truth:** `com.cometchat:chat-uikit-android:5.x` (legacy/maintenance-only; +`calls-sdk-android:5.x`) — resolved AAR (javap) + `ui-kit/android`. **Official docs:** https://www.cometchat.com/docs/fundamentals/user-auth · **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.
-
-> **Companion skills:** `cometchat-android-v5-core` covers dev-mode login;
-> `cometchat-android-v5-push` covers push notification setup for production.
-
-## Purpose
-
-This skill covers hardening a CometChat Android integration for production: replacing client-side Auth Key with server-side token generation, user management CRUD, ProGuard/R8 rules, and security best practices.
-
----
-
-## Use this skill when
-
-- "Set up production auth"
-- "Replace Auth Key with tokens"
-- "ProGuard is breaking CometChat"
-- "How do I create CometChat users from my backend?"
-
-## Do not use this skill when
-
-- Setting up dev-mode login → use `cometchat-android-v5-core`
-- Adding features → use `cometchat-android-v5-features`
-
----
-
-## 1. Why production auth matters
-
-In dev mode, `CometChatUIKit.login(uid)` uses the Auth Key embedded in your app. Anyone can decompile the APK, extract the key, and login as ANY user. Production deployments MUST use server-side token generation.
-
-## 2. Token auth flow
-
-```
-Client → Your Server → CometChat REST API → auth token → Client
-Client calls CometChatUIKit.loginWithAuthToken(token)
-```
-
-Your server calls: `POST https://{APP_ID}.api-{REGION}.cometchat.io/v3/users/{uid}/auth_tokens`
-with headers: `appId`, `apiKey` (REST API Key, NOT Auth Key).
-
-## 3. Client-side implementation
-
-**Java:**
-```java
-// Fetch token from YOUR backend
-String token = fetchTokenFromYourServer(currentUserId);
-
-CometChatUIKit.loginWithAuthToken(token, new CometChat.CallbackListener<User>() {
-    @Override
-    public void onSuccess(User user) {
-        // Navigate to chat
-    }
-    @Override
-    public void onError(CometChatException e) {
-        // Handle error
-    }
-});
-```
-
-## 4. ProGuard/R8 rules
-
-Add to `proguard-rules.pro`:
-
-```
--keep class com.cometchat.** { *; }
--keep class com.cometchat.chatuikit.** { *; }
--dontwarn com.cometchat.**
-```
-
-## 5. Security checklist
-
-- [ ] Auth Key removed from client code
-- [ ] REST API Key stored server-side only
-- [ ] `loginWithAuthToken()` used instead of `login(uid)`
-- [ ] ProGuard rules added
-- [ ] Network security config allows CometChat domains
-- [ ] Push token unregistered on logout
-
----
-
-## Hard rules
-
-- **Never ship Auth Key in production APKs.** Use `loginWithAuthToken()`.
-- **REST API Key ≠ Auth Key.** REST API Key is server-only. Auth Key is client-side dev-only.
-- **Add ProGuard keep rules.** R8 can strip CometChat classes needed at runtime.