@cometchat/skills 4.4.2 → 5.0.1

package/skills/.claude-plugin/marketplace.json

@@ -1,86 +0,0 @@
-{
-  "name": "cometchat-skills",
-  "display_name": "CometChat Skills for Claude",
-  "description": "AI-native skill suite for integrating CometChat React UI Kit v6 into any React project. Skills teach Claude integration patterns, component APIs, and production hardening instead of relying on templates.",
-  "version": "3.0.0",
-  "skills": [
-    {
-      "name": "cometchat",
-      "path": "skills/cometchat/SKILL.md",
-      "group": "core",
-      "description": "Entry-point dispatcher. Detects framework, understands the project, recommends integration shape, and routes to the right skills."
-    },
-    {
-      "name": "cometchat-core",
-      "path": "skills/cometchat-core/SKILL.md",
-      "group": "core",
-      "description": "Foundational rules — initialization, login, CSS, env vars, SSR safety, provider pattern, and anti-patterns."
-    },
-    {
-      "name": "cometchat-components",
-      "path": "skills/cometchat-components/SKILL.md",
-      "group": "core",
-      "description": "Complete catalog of CometChat React UI Kit v6 components — names, props, and composition patterns."
-    },
-    {
-      "name": "cometchat-placement",
-      "path": "skills/cometchat-placement/SKILL.md",
-      "group": "core",
-      "description": "Where to put chat — route, modal, drawer, embedded panel, or floating widget patterns."
-    },
-    {
-      "name": "cometchat-react-patterns",
-      "path": "skills/cometchat-react-patterns/SKILL.md",
-      "group": "framework",
-      "description": "Integration patterns for React projects (Vite or CRA) — provider setup, routing, env vars."
-    },
-    {
-      "name": "cometchat-nextjs-patterns",
-      "path": "skills/cometchat-nextjs-patterns/SKILL.md",
-      "group": "framework",
-      "description": "Integration patterns for Next.js (App Router + Pages Router) — SSR prevention, dynamic imports, API routes."
-    },
-    {
-      "name": "cometchat-react-router-patterns",
-      "path": "skills/cometchat-react-router-patterns/SKILL.md",
-      "group": "framework",
-      "description": "Integration patterns for React Router (v6 library + v7 framework mode) — outlet nesting, SSR guards."
-    },
-    {
-      "name": "cometchat-astro-patterns",
-      "path": "skills/cometchat-astro-patterns/SKILL.md",
-      "group": "framework",
-      "description": "Integration patterns for Astro — React islands, client:only rendering, island communication."
-    },
-    {
-      "name": "cometchat-theming",
-      "path": "skills/cometchat-theming/SKILL.md",
-      "group": "features",
-      "description": "Theme customization — CSS variable overrides, preset themes, dark mode, brand color mapping."
-    },
-    {
-      "name": "cometchat-features",
-      "path": "skills/cometchat-features/SKILL.md",
-      "group": "features",
-      "description": "Feature catalog — calls, reactions, polls, AI features, and how to enable each one."
-    },
-    {
-      "name": "cometchat-production",
-      "path": "skills/cometchat-production/SKILL.md",
-      "group": "features",
-      "description": "Production readiness — server-side token auth, user management CRUD, environment hardening, security checklist."
-    },
-    {
-      "name": "cometchat-customization",
-      "path": "skills/cometchat-customization/SKILL.md",
-      "group": "features",
-      "description": "Component customization — four-tier discovery, custom view slots, request builders, event subscriptions, and CSS overrides."
-    },
-    {
-      "name": "cometchat-troubleshooting",
-      "path": "skills/cometchat-troubleshooting/SKILL.md",
-      "group": "features",
-      "description": "Diagnostics — verify checks, drift detection, error decoding, and targeted fixes."
-    }
-  ]
-}

package/skills/cometchat/references/asking-questions.md

@@ -1,48 +0,0 @@
-# Clarification contract (all coding agents)
-
-Every place a CometChat skill says **"ask the user"**, **"render an `AskUserQuestion`"**, **"MUST ask"**, or **"NON-NEGOTIABLE prompt"** means: **follow this contract.** It is **model-agnostic** — it works on Claude Code, Codex, Cursor, Gemini CLI, OpenAI coding agents, Windsurf, and any future agent. `AskUserQuestion` is merely Claude Code's name for step 1; every agent has an equivalent, and if it doesn't, the text fallback below is mandatory.
-
-## The contract
-
-1. **RENDER a structured choice.**
-   - If your runtime has a native structured-question primitive (Claude Code: `AskUserQuestion`; others may differ), use it.
-   - **If it does not, render a numbered text list** — a one-line header, the question, then each option on its own numbered line — and ask the user to reply with a number or the option text. Never skip the prompt just because you lack a GUI primitive.
-
-2. **WAIT for a real answer. Do NOT proceed on a guess.**
-   - Do not pick a default, do not infer the answer from the repo, the project name, or "what's most common."
-   - **Auto / YOLO / "moving fast for the demo" / approval-mode does NOT authorize skipping a user-facing decision.** Those modes govern *tool and shell approvals*, not product choices. Surface the prompt regardless of approval mode.
-
-3. **MAP the answer by VALUE / LABEL — never by ordinal position.**
-   - The user may reply with the option text, a number, or free text. Resolve it to the option's *meaning*, not "they typed 1 so it's the first option."
-   - This matters because different agents render options in different orders; matching on position silently corrupts the choice.
-
-4. **ACCEPT a free-text fallback.**
-   - If the answer isn't one of the listed options (a different `uid`, region, app name, framework version…), treat it as a valid custom value — do not loop re-prompting the same list.
-
-5. **ONE decision per prompt** unless the choices are genuinely independent. Don't bundle unrelated decisions (e.g. framework + uid + region) into a single question.
-
-6. **SELF-VERIFY before moving on.** Confirm you have an explicit answer for every *required* prompt of the current step. If you are running **headless / non-interactive** (no stdin, CI, cron), do **not** guess — STOP and emit the exact question + options so a human can answer, then resume.
-
-## Canonical text rendering (for agents without a structured primitive)
-
-```
-❓ <one-line question>   (reply with the number or the text)
-  1) <Option label> — <short description>
-  2) <Option label> — <short description>
-  3) <Option label> — <short description>
-  Or type your own answer.
-```
-
-Wait for the reply. Resolve it to an option by label/text (or accept a custom value). Then continue.
-
-## Prompts in the CometChat skills that MUST follow this contract
-
-These are load-bearing — skipping them silently picks defaults the user never saw, which corrupts downstream routing or ships broken code:
-
-- **Greenfield framework choice** (when `detect` returns no framework) — never scaffold a framework the user didn't choose.
-- **Android version** (V5 vs V6) and **Flutter version** (V5 vs V6) when the project is greenfield — these route to *different* SDKs; guessing wrong emits unusable code.
-- **Android/Flutter surface** (Compose vs Kotlin Views; which screen) when both are present.
-- **Dev-mode login UID** — never hardcode `cometchat-uid-1`; ask which test user. A default UID flagged as a Bot in the dashboard fails auth with an opaque error.
-- **Sign-up flow choices** — product, role, intent, app name, region, industry. These mirror the dashboard browser flow and drive downstream recommendations.
-- **Calling mode** (default UI calling vs session-mode vs raw SDK), **chat-only vs chat+calls**, and **custom-UI vs UI-Kit** when the journey forks.
-- **Existing-integration decisions** — when a competing chat SDK, existing Firebase/push, or an existing auth system is detected (see the dispatcher's pre-flight scan), ask how to proceed rather than clobbering.

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

@@ -1,121 +0,0 @@
----
-name: cometchat-android-v5
-description: "Entry-point dispatcher for CometChat Android UI Kit v5. Detects project setup, understands what the dev is building, and routes to the right sub-skills."
-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 dispatcher entry-point integration"
----
-
-> **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/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.
-
-## Purpose
-
-This is the entry-point skill for CometChat Android UI Kit v5. It helps you understand what the developer is building, detects their project setup, and routes to the correct sub-skill for the task at hand.
-
-**All skills are designed to work with both Java and Kotlin projects.** Code examples in each skill are provided in both languages.
-
----
-
-## Use this skill when
-
-- A developer asks to "add chat to my Android app"
-- Starting a new CometChat integration
-- Unsure which skill to use for a specific task
-- Need an overview of what CometChat Android UI Kit v5 offers
-
-## Do not use this skill when
-
-- You already know which specific skill is needed (go directly to it)
-
----
-
-## 1. Project detection
-
-Before writing any code, detect the project setup:
-
-| Check | How | Why |
-|---|---|---|
-| Language | Look for `.kt` files in `src/main/java/` or `src/main/kotlin/` | Determines Java vs Kotlin code examples |
-| Gradle version | Check `gradle-wrapper.properties` for `distributionUrl` | Affects dependency syntax (Groovy vs Kotlin DSL) |
-| Min SDK | Check `build.gradle` for `minSdkVersion` | Must be 24+ for CometChat |
-| Existing CometChat | Search for `com.cometchat` in `build.gradle` | Avoid duplicate setup |
-| Calling SDK | Search for `com.cometchat:calls-sdk-android` | Determines if voice/video is already available |
-
----
-
-## 2. What are you building?
-
-Ask the developer what they're building to recommend the right placement:
-
-| Intent | Recommended placement | Components |
-|---|---|---|
-| Messaging app | Dedicated Activity with bottom tabs | `CometChatConversations` + `CometChatMessageList` + `CometChatMessageComposer` + `CometChatMessageHeader` |
-| Marketplace / platform | Chat button on product screen + inbox Activity | Single thread (button trigger) + multi-conversation (inbox) |
-| SaaS / dashboard | Chat Fragment in existing Activity | `CometChatConversations` in a Fragment |
-| Social / community | Full messenger with tabs | Conversations + Users + Groups + Calls in ViewPager/BottomNav |
-| Support / helpdesk | BottomSheet or Dialog overlay | `CometChatMessageList` + `CometChatMessageComposer` in BottomSheet |
-| Just exploring | Minimal single-Activity demo | `CometChatConversations` with pre-logged-in test user |
-
----
-
-## 3. Skill routing reference
-
-| Skill | When to load |
-|---|---|
-| `cometchat-android-v5-core` | **Always** — before any integration code. Init, login, builder, dependencies. |
-| `cometchat-android-v5-components` | **Always** — before writing component code. Full catalog of all CometChat views. |
-| `cometchat-android-v5-placement` | When integrating — Activity, Fragment, BottomSheet, Dialog, Tab patterns. |
-| `cometchat-android-v5-theming` | When customizing look and feel — colors, fonts, dark mode, style classes. |
-| `cometchat-android-v5-features` | When adding features — calls, reactions, polls, AI, extensions. |
-| `cometchat-android-v5-customization` | When writing custom templates, events, DataSource decorators. |
-| `cometchat-android-v5-production` | When setting up production auth or user management. |
-| `cometchat-android-v5-troubleshooting` | When diagnosing problems — Gradle errors, crashes, rendering issues. |
-| `cometchat-android-v5-extensions` | When working with extensions (polls, stickers, collaborative, etc.). |
-| `cometchat-android-v5-push` | When setting up push notifications (FCM, token lifecycle, deep-link). |
-| `cometchat-android-v5-testing` | When adding tests (unit, UI, instrumented, E2E, CI). |
-
----
-
-## 4. Integration order
-
-Every integration follows this sequence:
-
-```
-1. Dependencies (Gradle)          → cometchat-android-v5-core §1
-2. Manifest permissions            → cometchat-android-v5-core §5
-3. App theme setup                 → cometchat-android-v5-core §5b (must inherit CometChatTheme.DayNight — Material 2 parent)
-4. Init + Login                    → cometchat-android-v5-core §2-3
-5. Place components in your app    → cometchat-android-v5-placement
-6. Customize appearance            → cometchat-android-v5-theming
-7. Add features                    → cometchat-android-v5-features
-8. Production hardening            → cometchat-android-v5-production
-```
-
----
-
-## 5. Iteration menu
-
-After the initial integration, the developer can:
-
-1. **Customize look and feel** — Theme presets, brand colors, dark mode
-2. **Add a feature** — Calls, reactions, polls, AI smart replies, file sharing
-3. **Customize a component** — Custom message bubbles, headers, composer actions
-4. **Set up production auth** — Replace dev Auth Key with server-side tokens
-5. **Set up push notifications** — FCM setup, token lifecycle, deep-link on tap
-6. **Add tests** — Unit tests, UI tests, E2E with Maestro
-7. **Troubleshoot an issue** — Gradle errors, runtime crashes, rendering problems
-
-Route each choice to the appropriate skill.
-
----
-
-## Hard rules
-
-- **Always read `cometchat-android-v5-core` first.** It covers init, login, and dependencies — prerequisites for everything else.
-- **Always read `cometchat-android-v5-components` before writing component code.** Never invent component names or method signatures from memory.
-- **Provide both Java and Kotlin examples.** The v5 UIKit is written in Java but is fully interoperable with Kotlin. Client devs use both.
-- **Ask, don't assume.** Every integration decision (placement, features, auth mode) should be confirmed with the developer.
-- **Always read existing files before modifying them.** Never blindly overwrite project files.