[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFJQRR8AFKH5H2WBV6JRKE":3,"skill-same:01M6MFJQRR8AFKH5H2WBV6JRKE":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MFJQRR8AFKH5H2WBV6JRKE","cometchat-react-v7-core",null,"Add CometChat chat to a React app end-to-end — detect the project, get & verify dashboard credentials, init→login→render with CometChatProvider, and the drop-in conversation UI. The core knowledge every other React v7 skill builds on. Triggers: 'add chat to my react app', 'integrate cometchat react', 'set up cometchat credentials', 'show conversations and messages'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"cometchat react v7 core","cometchat","react","core","end","next","dashboard","credentials","drop","knowledge","init","up","render","messages","project","conversations","get","show","conversation","app","SET","2026-11-10 10:12:30",false,"---\nname: cometchat-react-v7-core\ndescription: \"Add CometChat chat to a React app end-to-end — detect the project, get & verify dashboard credentials, init→login→render with CometChatProvider, and the drop-in conversation UI. The core knowledge every other React v7 skill builds on. Triggers: 'add chat to my react app', 'integrate cometchat react', 'set up cometchat credentials', 'show conversations and messages'.\"\nlicense: \"MIT\"\ncompatibility: \"Node.js >=18; React >=18; Vite >=4 \u002F CRA \u002F Next.js; @cometchat\u002Fchat-uikit-react ^7 (7.2.x, verified 7.2.4); @cometchat\u002Fchat-sdk-javascript ^4.1.9\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.3.0\"\n  tags: \"cometchat react core chat integration uikit v7 setup credentials\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7` + `@cometchat\u002Fchat-sdk-javascript@^4.1.9`. Symbols sourced from live v7 docs. This file is the THIN map loaded every run; deep detail is in `references\u002F*` loaded ONLY when the task needs it. Anything marked **[v7-verify]** is a v6 carry-over to confirm against v7 docs\u002Fcatalog before shipping.\n\n\u003C!-- core is the companion the other react v7 skills read; it has no Companion block of its own. -->\n\n## Use this skill when\n\"add chat to my React app\", \"set up CometChat credentials\", \"integrate CometChat in React\", \"show a conversations + messages UI\", \"build a full chat app\". An unscoped \"add chat\" means a **production-ready core chat surface** (a `CometChatConversations` list ↔ a message pane, wrapped in `CometChatErrorBoundary`, sized, affordances wired-or-hidden, mobile collapse) — NOT a bare two-pane demo, and NOT the whole combined app. See the golden path below. It **grows on request** (users\u002Fgroups\u002Fcalls tabs, a details\u002Fthread\u002Fsearch side panel, calls) to the full combined app — that recipe lives in `cometchat-react-v7-placement`.\n\n## Install\n`npm i @cometchat\u002Fchat-uikit-react@7 @cometchat\u002Fchat-sdk-javascript@4 dompurify` (keep the `@7`\u002F`@4` major pins — a bare install resolves to `latest` and can pull the wrong major). `dompurify` is required by the kit — the docs install includes it. Voice\u002Fvideo calling also needs `@cometchat\u002Fcalls-sdk-javascript` (see `cometchat-react-v7-features`).\n\n## Setup & credentials (essentials — full detail: `references\u002Fsetup-credentials.md`)\n1. **Detect** React + bundler (Vite→`VITE_`, CRA→`REACT_APP_`, Next→`NEXT_PUBLIC_`\u002F`.env.local`). Reuse existing `.cometchat`\u002Fenv if present (skip re-setup).\n2. **version_conflict — STOP** if a non-v7 UI Kit is installed; reconcile first (never mix majors — `RULES.md`).\n3. **Credentials — OFFER the dashboard fetch FIRST, default to it** (never silently \"paste it yourself\", never defer to a \"to finish, add them yourself\" TODO — AUDIT-039). Reuse existing `.cometchat`\u002Fenv if present (skip). Else offer both, defaulting to fetch: **(a) account fetch (recommended)** through the CometChat MCP — `cometchat_whoami`, **pick an EXISTING app** (`cometchat_list_apps`; **never auto-create**), `cometchat_get_app_credentials` returns the creds plus ready env lines (it writes no file); **(b) manual paste** — Dashboard → Credentials (dev-only Auth Key). **Then the SKILL writes the framework env (§4)** — the MCP only returns values; framework detection, env-writing, and codegen are the SKILL's job (AUDIT-059). Ask & wait if the user must choose or the MCP isn't connected. Full flow: `references\u002Fsetup-credentials.md`.\n4. **Write env** (correct prefix), gitignore it, never echo the Auth Key. Prod → server-side auth token, not the Auth Key.\n5. **Authorize** = `init()` + `login()` resolve; auth error usually means wrong Region.\n\n## Integration ordering (BAKED — invariant; docs: \"init() must resolve before login()\")\n`init()` once at startup → `login(UID)` after init resolves (guard with the sync `CometChatUIKit.getLoggedInUser()`) → render inside `CometChatProvider`.\n\n```tsx\nimport { CometChatUIKit } from \"@cometchat\u002Fchat-uikit-react\";\n\u002F\u002F initFromSettings (NOT the classic UIKitSettingsBuilder init) sets integrationSource=\"ai-agent\"\n\u002F\u002F for telemetry attribution — and routes the Calls SDK through initFromSettings too (AUDIT-084).\nawait CometChatUIKit.initFromSettings({\n  appId: import.meta.env.VITE_COMETCHAT_APP_ID,\n  region: import.meta.env.VITE_COMETCHAT_REGION,\n  credentials: { authKey: import.meta.env.VITE_COMETCHAT_AUTH_KEY }, \u002F\u002F dev only; prod → server-minted auth token\n  chatSDK: { presenceSubscription: { type: \"ALL_USERS\" } },         \u002F\u002F = the classic subscribePresenceForAllUsers()\n});                                                                  \u002F\u002F must resolve first\nif (!CometChatUIKit.getLoggedInUser()) await CometChatUIKit.login(UID);   \u002F\u002F sync getter — capital \"In\"\n```\n> Init once + StrictMode double-init, concurrent-login guard, and the reusable provider: `references\u002Flifecycle.md`.\n> **Which UID?** `login()` needs a user that ALREADY EXISTS — never invent\u002Fhardcode a guessed one. ASK, or take one from Dashboard → **Users** (fresh apps seed `cometchat-uid-1...`). **Never suggest `superhero1..5` or any remembered \"classic sample\" UID (not seeded in modern apps); don't fabricate UIDs from memory — the only tentative suggestion is `cometchat-uid-1`, labelled \"if this is a fresh app.\"** Prod → per-user auth token + `loginWithAuthToken`. Detail: `references\u002Fsetup-credentials.md` §6.\n\n## Component \u002F API map (BAKED closed list)\nInit\u002Fprovider: `CometChatUIKit`, `UIKitSettingsBuilder`, `CometChatProvider`, `CometChatErrorBoundary` (wraps the surface — production must-have). Core-surface drop-ins: `CometChatConversations`, `CometChatMessageHeader`, `CometChatMessageList`, `CometChatMessageComposer`; wired affordances `CometChatThreadHeader`, `CometChatSearch`. Grow set (added on request): `CometChatUsers`, `CometChatGroups`, `CometChatCallLogs`, `CometChatGroupMembers`, `CometChatIncomingCall`.\n\n## Hot-path props (BAKED — the golden path needs NO fetch)\nThe ~12 props you actually wire for \"add chat\". Do NOT fetch docs for these; do NOT read `.d.ts`.\n- `CometChatConversations`: `onItemClick(conversation)` (select → drives the message pane) · `activeConversation` · `showSearchBar` (default `true`; wire `onSearchBarClicked`→`CometChatSearch` or set `false`) · `selectionMode` (default `\"none\"`) · `conversationsRequestBuilder` — **scope the list to the REQUEST**: a 1:1\u002FDM-only ask → `new CometChat.ConversationsRequestBuilder().setLimit(30).setConversationType(\"user\")` so the app's seeded groups don't show (`\"group\"` for groups-only); pass the builder INSTANCE, not `.build()`. **`.setLimit(n)` is REQUIRED on a custom builder** — without it the list renders the kit's \"something went wrong\" state (verified 7.2.0, AUDIT-245; STOPGAP: the docs' filter-recipe table omits it — remove this note once that docs recipe is fixed). See the data-scope note below.\n- `CometChatMessageHeader`: `onItemClick` (open profile) · `showSearchOption` (default `true`) + `onSearchOptionClicked` → **open a SCOPED `CometChatSearch` (`uid`\u002F`guid` of the current chat) in the side panel (in-chat message search, default-on; opt-out via `showSearchOption={false}`)** · `hideBackButton` (default `false`) + `onBack` (mobile → pop to list).\n- `CometChatMessageList`: `onThreadRepliesClick(message)` → **open the thread panel (DEFAULT — threaded replies ship with a first-time \"add chat\")**; `hideReplyInThreadOption` ONLY if the user explicitly opts out of threads.\n- `CometChatMessageComposer`: `placeholder` (default `\"Type a message...\"`); a plain send needs no props.\n- `CometChatProvider`: `theme` (`\"light\"` default — no OS-follow; sync to `prefers-color-scheme`, see `references\u002Ftheming.md`).\n> **Stable props + view slots for the 4 drop-ins are BAKED in `references\u002Fcomponent-props.md`** — use them: custom UI goes IN the component's slot (search → Conversations `headerView` \u002F MessageHeader `trailingView`), NEVER as a sibling on top. Exhaustive\u002Frare props or any OTHER component → fetch its `.md` twin via `references\u002Fdocs-map.md`; NEVER read `node_modules\u002F.d.ts`. Full catalog: `cometchat-react-v7-components`.\n\n\n## Golden path — the production-ready CORE surface (default for an unscoped \"add chat\"; grows on request)\nSetup → guarded init\u002Flogin → wrap the app in `CometChatProvider` **inside `CometChatErrorBoundary`** → build the core surface: a `CometChatConversations` LIST ↔ a MESSAGE pane (`CometChatMessageHeader` + `CometChatMessageList` + `CometChatMessageComposer`) for the selected conversation, a small host state object coordinating {selected conversation, side view: thread | in-chat-search | none}, collapsing to one pane on mobile. Complete and wired but LEAN — NOT a bare two-pane demo, NOT the whole combined app. Reuse existing routing\u002Flayout\u002Fauth; add files + wiring only, never rewrite. Least-code = reach for the drop-ins\u002Fslots (HOW). **The compile-verified TSX + the required column CSS live in `references\u002Flayout.md` (sizing) and `cometchat-react-v7-placement\u002Freferences\u002Frecipes.md` (the Core-surface recipe) — build from those; this entry stays the thin map.**\n\nWire every default-on affordance so nothing dead-ends, and keep these INVARIANTS:\n- **Threads are DEFAULT** (ship with a first-time \"add chat\"). Wire `CometChatMessageList onThreadRepliesClick(m)` → a thread panel (`CometChatThreadHeader` + a thread `CometChatMessageList` + `CometChatMessageComposer`) with a close\u002Fback round-trip. **The thread list AND composer take BOTH the current target (`user` OR `group`, same as the main pane) AND `parentMessageId`; passing `parentMessageId` ALONE silently NEVER SENDS (AUDIT-060).** Set `hideReplyInThreadOption` only on explicit opt-out. **Differentiate the thread MESSAGE LIST** (not just the wrapper): scope `--cometchat-message-list-bg: var(--cometchat-background-color-01)` on the thread wrapper — the list paints its own opaque bg so a wrapper bg can't reach it (verified vs 7.1.0; recipe in `cometchat-react-v7-customization`).\n- **Two searches, both default-on, both need the FULL round-trip (AUDIT-017).** GLOBAL conversation search over the LIST column (`CometChatConversations onSearchBarClicked` → `CometChatSearch`, no uid\u002Fguid — or `showSearchBar={false}`); IN-CHAT scoped search in the SIDE PANEL (`CometChatMessageHeader showSearchOption` default `true` → `onSearchOptionClicked` → `CometChatSearch` with the current `uid`\u002F`guid`, mutually exclusive with the thread). Each renders a back button (`onBack`) you MUST wire to close + return, PLUS `onConversationClicked`\u002F`onMessageClicked` to select the hit — a companion you open, you must also close. (Real server-side search may also need a Dashboard toggle — VERIFY.)\n- **SIZE per the ONE standard — `references\u002Flayout.md`.** The kit fills its parent and ships its own `loadingView`\u002F`emptyView`, so a broken-looking surface is a HOST container-sizing defect (a content-driven box), not a kit bug — two modes: static collapse (~0px sliver) and load-transition reflow (grows into place as content loads). Satisfy the 5 invariants: prepare\u002FRESET the ancestor chain (`html,body,#root{height:100%;margin:0}` + undo the Vite\u002FCRA\u002FNext scaffold center+cap+pad, AUDIT-019\u002F035) · pin the surface to a content-INDEPENDENT `100dvh` (never `min-height`\u002F`auto`) · size COLUMNS with `min-height:0`\u002F`overflow:hidden` (scroll, don't grow the parent) · let the kit loading state fill the pinned box · no `transform`\u002F`filter` ancestors. The 2-column CSS is in `layout.md`; the 3-column\u002Fembedded\u002Fpopup\u002Fsidebar recipes in `cometchat-react-v7-placement`. Keep `CometChatProvider` WRAPPING `.cc-app`, not inside it (the `.cometchat` wrapper breaks the row — AUDIT-036).\n- **Match data scope to the REQUEST (AUDIT-038).** A 1:1\u002FDM-only ask must NOT show the app's seeded groups — scope with the built-in `conversationsRequestBuilder` prop (pass the `CometChat.ConversationsRequestBuilder` INSTANCE, `.setLimit(30).setConversationType(\"user\")` — `setLimit` required; `\"group\"` for groups-only; **reuse the prop, don't hand-roll a client-side filter**), and scope the selector to match (no Groups tab on a 1:1-only app). A generic unscoped \"add chat\" keeps BOTH. Example in `references\u002Fcomponent-props.md`.\n- **Theme:** the kit defaults to `light` and does NOT follow the OS (no `theme=\"system\"`) — sync `CometChatProvider theme=` to `prefers-color-scheme` by default (`references\u002Ftheming.md`, AUDIT-004).\n- **Reuse built-in triggers — don't hand-roll buttons (AUDIT-006).** Wire the props components already expose; custom UI goes IN the component's view slot (search icon → Conversations `headerView` \u002F MessageHeader `trailingView`), NEVER a sibling on top (slot map: `references\u002Fcomponent-props.md`). Unclear prop → fetch its `.md` twin (`references\u002Fdocs-map.md`), never the `.d.ts`.\n- **`CometChatErrorBoundary` wraps the surface** (children required; optional `onError`\u002F`fallbackView`\u002F`componentName`) — a render error then shows a localized fallback + retry, not a blank white screen. It is NOT the initializer (init\u002Flogin still happen first). Leave header call buttons + composer attach\u002Femoji\u002Fvoice as built-in defaults; do NOT turn on gated extensions\u002FAI\u002Fplugins; do NOT add selector tabs \u002F a details or scoped-search side panel \u002F call logs \u002F incoming call (those are the GROWTHS) unless asked — **but the thread panel IS part of the default.** **Prod auth: `loginWithAuthToken` with a per-user server-minted token; the Auth Key is dev-only** (`references\u002Flifecycle.md`).\n\n**Grows on request → the full combined app** (users\u002Fgroups\u002Fcalls **tabs**, a details\u002Fthread\u002Fscoped-search **side panel**, `CometChatIncomingCall` at root, **calls**, individual **features**) — the UNION of these growths. The compile-verified combined-app recipe (with the required column CSS + `CometChatErrorBoundary`) is baked in **`cometchat-react-v7-placement`**; build the grown app from it. A user who scopes DOWN (embed\u002Fpopup\u002Fsidebar) → the matching `cometchat-react-v7-placement` variant.\n\n## Deep references (load ONLY when the task needs them — keeps this file light on run)\n- `references\u002Fsetup-credentials.md` — detect, config reuse, version_conflict, dashboard creds, env, authorize.\n- `references\u002Flifecycle.md` — init-once + StrictMode, concurrent-login guard (`ensureLoggedIn`), get-current-UID (sync vs async), prod auth-token, logout, the full `CometChatProvider`.\n- `references\u002Flayout.md` — **the ONE reflow-free-surface sizing standard** (the 5 invariants: prepared ancestor chain · pinned content-independent height · `min-height:0` columns · kit loading state inside the pinned box = NO load-transition reflow · no `transform`\u002F`filter` ancestors). `placement` + `calls` reference it too — change sizing rules HERE.\n- `references\u002Fssr.md` — Next.js \u002F Astro \u002F React Router SSR safety (`\"use client\"`, `ssr:false`, `client:only`).\n- `references\u002Ftheming.md` — CSS import-once + `--cometchat-*` variables (depth: `cometchat-react-v7-customization`).\n- Localization \u002F RTL \u002F accessibility → the cross-family **`cometchat-i18n`** + **`cometchat-a11y`** skills. Don't render a raw key (`group_info`) — the provider auto-wires localization. React theme tokens: `references\u002Ftheming.md`.\n- `references\u002Fanti-patterns.md` — the 15 real-bug anti-patterns (incl. `transform`\u002FTailwind overlay bug, container dimensions, **scaffold-boilerplate** = centered\u002Fcapped\u002Fgutter-boxed chat (#15), **global-CSS-leak** = centered names \u002F expanding header, **raw-i18n-key** rendering).\n- `references\u002Fdependencies.md` — packages, major pins, `CometChat.*` SDK types, bundle-size cost transparency.\n- `references\u002Fcomponent-props.md` — **BAKED stable props + view slots** for the 4 drop-ins (where custom UI goes IN each component — search → Conversations `headerView`, MessageHeader `trailingView`, etc.).\n- `references\u002Fdocs-map.md` — intent → the exact docs `.md` twin to fetch (replaces reading `.d.ts`); **for a whole feature\u002Ftask, its \"Task guides (recipes)\" section says to BUILD FROM the official guide + COMPARE your implementation against it (docs-maximal), then apply the hardening deltas.**\n- Symptom → cause → fix (blank screen, SSR `window is not defined`, ~0px collapse, kit error state, empty lists, events not firing, `version_conflict`) → the **`cometchat-react-v7-troubleshooting`** skill.\n\n> **Visual Builder (VCB) is out of scope.** If asked to integrate a VCB export, point to the CometChat Visual Builder docs (via `references\u002Fdocs-map.md`); don't hand-roll a builder-export flow.\n\n## Common pitfalls (top 4 — full list in `references\u002Fanti-patterns.md`)\nversion_conflict (v6 installed) · wrong Region or env prefix · Auth Key shipped to prod client · rendering\u002Flogin before init resolves.\n\n## Verify it works\nStart the app → confirm `init()` then `login()` resolve → the `CometChatConversations` list renders inside `CometChatProvider` (itself inside `CometChatErrorBoundary`) at full size (not a collapsed sliver); open a conversation → the message pane loads and messages send\u002Freceive; **clicking \"reply in thread\" opens the thread panel (default) and its back\u002Fclose returns to the list** (hidden only if the user opted out), and the thread's MESSAGE LIST reads as a distinct surface matching its own header\u002Fcomposer (not the same shade as the main list — the `--cometchat-message-list-bg` override is scoped on the thread wrapper); **clicking the message-header search icon opens an in-chat search in the side panel scoped to THAT conversation (default), with back to close**; the conversations search bar is wired-or-hidden (no dead-ends); on a narrow viewport it collapses to one pane at a time (list → message → thread\u002Fsearch → back). Blank white screen ⇒ something rendered before `init()` resolved, the Region \u002F env prefix is wrong, or an unbounded render error escaped (add `CometChatErrorBoundary`). A list + message pane with no sizing \u002F no error boundary \u002F dead-ending affordances ⇒ under-delivery (see the golden path). Growing to the full app (tabs + side panel + incoming call) ⇒ verify per `cometchat-react-v7-placement`.\n\n## Explain what you built (REQUIRED close)\nAfter it builds + verifies, don't dump silently — tell the user briefly: **(1) what I wired** (3–5 bullets, NAME the files); **(2) decisions & why**, flagging dev-only AS dev-only (dev **Auth Key** → server auth token for prod; the `\u003Cuid>`; OS-follow theme); **(3) what I did NOT touch** (additive — routing\u002Fauth\u002Fstyles intact). Then **(4) offer these THREE options as a SELECTABLE choice and WAIT for the user's pick — do NOT auto-continue:**\n- **(1) Add another feature** → **first check what's ALREADY there, then suggest only the GAP (AUDIT-043).** Read what's wired (the emitted code you built) and ASK which dashboard-gated extensions are already enabled (you can't reliably read per-app dashboard state — don't assume OFF). SUGGEST 3–4 grow-set items that are NEITHER wired NOR already enabled (voice\u002Fvideo **calls** · **search** · **threads** if off · **push** · **AI\u002Fsmart-replies** · **moderation** · polls\u002Fstickers\u002Ftranslation) — **never re-suggest something already on (e.g. translation already enabled in the dashboard)**. **Do NOT suggest `reactions` or `mentions` — they are ON BY DEFAULT in v7 (core messaging; their dashboard extensions are \"(Legacy)\", already in core — AUDIT-077); if the user asks, say they're already on and offer to customize them.** Then build the chosen one (→ `cometchat-react-v7-features` \u002F `cometchat-react-v7-calls`).\n- **(2) Customize theming** → ask whether they already have a **preset \u002F brand theme** (a brand color, light\u002Fdark, or match an existing design system) or want to talk through the options, then wire it (→ `cometchat-react-v7-customization`).\n- **(3) Test it manually** → do NOTHING further — hand it back so the user runs and checks it themselves.\n\nA PARKED capability (push · migration · SDK-only) → isn't in this pack yet: say so honestly + link CometChat's docs. **This 3-option close runs after EVERY implementation (`RULES.md` §19 \u002F AUDIT-040).**\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7` + `@cometchat\u002Fchat-sdk-javascript@^4.1.9`. Symbols sourced from live v7 docs. This file is the THIN map loaded every run; deep detail is in `references\u002F*` loaded ONLY when the task needs it. Anything marked **[v7-verify]** is a v6 carry-over to confirm against v7 docs\u002Fcatalog before shipping.\n\n\u003C!-- core is the companion the other react v7 skills read; it has no Companion block of its own. -->\n\n## Use this skill when\n\"add chat to my React app\", \"set up CometChat credentials\", \"integrate CometChat in React\", \"show a conversations + messages UI\", \"build a full chat app\". An unscoped \"add chat\" means a **production-ready core chat surface** (a `CometChatConversations` list ↔ a message pane, wrapped in `CometChatErrorBoundary`, sized, affordances wired-or-hidden, mobile collapse) — NOT a bare two-pane demo, and NOT the whole combined app. See the golden path below. It **grows on request** (users\u002Fgroups\u002Fcalls tabs, a details\u002Fthread\u002Fsearch side panel, calls) to the full combined app — that recipe lives in `cometchat-react-v7-placement`.\n\n## Install\n`npm i @cometchat\u002Fchat-uikit-react@7 @cometchat\u002Fchat-sdk-javascript@4 dompurify` (keep the `@7`\u002F`@4` major pins — a bare install resolves to `latest` and can pull the wrong major). `dompurify` is required by the kit — the docs install includes it. Voice\u002Fvideo calling also needs `@cometchat\u002Fcalls-sdk-javascript` (see `cometchat-react-v7-features`).\n\n## Setup & credentials (essentials — full detail: `references\u002Fsetup-credentials.md`)\n1. **Detect** React + bundler (Vite→`VITE_`, CRA→`REACT_APP_`, Next→`NEXT_PUBLIC_`\u002F`.env.local`). Reuse existing `.cometchat`\u002Fenv if present (skip re-setup).\n2. **version_conflict — STOP** if a non-v7 UI Kit is installed; reconcile first (never mix majors — `RULES.md`).\n3. **Credentials — OFFER the dashboard fetch FIRST, default to it** (never silently \"paste it yourself\", never defer to a \"to finish, add them yourself\" TODO — AUDIT-039). Reuse existing `.cometchat`\u002Fenv if present (skip). Else offer both, defaulting to fetch: **(a) account fetch (recommended)** through the CometChat MCP — `cometchat_whoami`, **pick an EXISTING app** (`cometchat_list_apps`; **never auto-create**), `cometchat_get_app_credentials` returns the creds plus ready env lines (it writes no file); **(b) manual paste** — Dashboard → Credentials (dev-only Auth Key). **Then the SKILL writes the framework env (§4)** — the MCP only returns values; framework detection, env-writing, and codegen are the SKILL's job (AUDIT-059). Ask & wait if the user must choose or the MCP isn't connected. Full flow: `references\u002Fsetup-credentials.md`.\n4. **Write env** (correct prefix), gitignore it, never echo the Auth Key. Prod → server-side auth token, not the Auth Key.\n5. **Authorize** = `init()` + `login()` resolve; auth error usually means wrong Region.\n\n## Integration ordering (BAKED — invariant; docs: \"init() must resolve before login()\")\n`init()` once at startup → `login(UID)` after init resolves (guard with the sync `CometChatUIKit.getLoggedInUser()`) → render inside `CometChatProvider`.\n\n```tsx\nimport { CometChatUIKit } from \"@cometchat\u002Fchat-uikit-react\";\n\u002F\u002F initFromSettings (NOT the classic UIKitSettingsBuilder init) sets integrationSource=\"ai-agent\"\n\u002F\u002F for telemetry attribution — and routes the Calls SDK through initFromSettings too (AUDIT-084).\nawait CometChatUIKit.initFromSettings({\n  appId: import.meta.env.VITE_COMETCHAT_APP_ID,\n  region: import.meta.env.VITE_COMETCHAT_REGION,\n  credentials: { authKey: import.meta.env.VITE_COMETCHAT_AUTH_KEY }, \u002F\u002F dev only; prod → server-minted auth token\n  chatSDK: { presenceSubscription: { type: \"ALL_USERS\" } },         \u002F\u002F = the classic subscribePresenceForAllUsers()\n});                                                                  \u002F\u002F must resolve first\nif (!CometChatUIKit.getLoggedInUser()) await CometChatUIKit.login(UID);   \u002F\u002F sync getter — capital \"In\"\n```\n> Init once + StrictMode double-init, concurrent-login guard, and the reusable provider: `references\u002Flifecycle.md`.\n> **Which UID?** `login()` needs a user that ALREADY EXISTS — never invent\u002Fhardcode a guessed one. ASK, or take one from Dashboard → **Users** (fresh apps seed `cometchat-uid-1...`). **Never suggest `superhero1..5` or any remembered \"classic sample\" UID (not seeded in modern apps); don't fabricate UIDs from memory — the only tentative suggestion is `cometchat-uid-1`, labelled \"if this is a fresh app.\"** Prod → per-user auth token + `loginWithAuthToken`. Detail: `references\u002Fsetup-credentials.md` §6.\n\n## Component \u002F API map (BAKED closed list)\nInit\u002Fprovider: `CometChatUIKit`, `UIKitSettingsBuilder`, `CometChatProvider`, `CometChatErrorBoundary` (wraps the surface — production must-have). Core-surface drop-ins: `CometChatConversations`, `CometChatMessageHeader`, `CometChatMessageList`, `CometChatMessageComposer`; wired affordances `CometChatThreadHeader`, `CometChatSearch`. Grow set (added on request): `CometChatUsers`, `CometChatGroups`, `CometChatCallLogs`, `CometChatGroupMembers`, `CometChatIncomingCall`.\n\n## Hot-path props (BAKED — the golden path needs NO fetch)\nThe ~12 props you actually wire for \"add chat\". Do NOT fetch docs for these; do NOT read `.d.ts`.\n- `CometChatConversations`: `onItemClick(conversation)` (select → drives the message pane) · `activeConversation` · `showSearchBar` (default `true`; wire `onSearchBarClicked`→`CometChatSearch` or set `false`) · `selectionMode` (default `\"none\"`) · `conversationsRequestBuilder` — **scope the list to the REQUEST**: a 1:1\u002FDM-only ask → `new CometChat.ConversationsRequestBuilder().setLimit(30).setConversationType(\"user\")` so the app's seeded groups don't show (`\"group\"` for groups-only); pass the builder INSTANCE, not `.build()`. **`.setLimit(n)` is REQUIRED on a custom builder** — without it the list renders the kit's \"something went wrong\" state (verified 7.2.0, AUDIT-245; STOPGAP: the docs' filter-recipe table omits it — remove this note once that docs recipe is fixed). See the data-scope note below.\n- `CometChatMessageHeader`: `onItemClick` (open profile) · `showSearchOption` (default `true`) + `onSearchOptionClicked` → **open a SCOPED `CometChatSearch` (`uid`\u002F`guid` of the current chat) in the side panel (in-chat message search, default-on; opt-out via `showSearchOption={false}`)** · `hideBackButton` (default `false`) + `onBack` (mobile → pop to list).\n- `CometChatMessageList`: `onThreadRepliesClick(message)` → **open the thread panel (DEFAULT — threaded replies ship with a first-time \"add chat\")**; `hideReplyInThreadOption` ONLY if the user explicitly opts out of threads.\n- `CometChatMessageComposer`: `placeholder` (default `\"Type a message...\"`); a plain send needs no props.\n- `CometChatProvider`: `theme` (`\"light\"` default — no OS-follow; sync to `prefers-color-scheme`, see `references\u002Ftheming.md`).\n> **Stable props + view slots for the 4 drop-ins are BAKED in `references\u002Fcomponent-props.md`** — use them: custom UI goes IN the component's slot (search → Conversations `headerView` \u002F MessageHeader `trailingView`), NEVER as a sibling on top. Exhaustive\u002Frare props or any OTHER component → fetch its `.md` twin via `references\u002Fdocs-map.md`; NEVER read `node_modules\u002F.d.ts`. Full catalog: `cometchat-react-v7-components`.\n\n\n## Golden path — the production-ready CORE surface (default for an unscoped \"add chat\"; grows on request)\nSetup → guarded init\u002Flogin → wrap the app in `CometChatProvider` **inside `CometChatErrorBoundary`** → build the core surface: a `CometChatConversations` LIST ↔ a MESSAGE pane (`CometChatMessageHeader` + `CometChatMessageList` + `CometChatMessageComposer`) for the selected conversation, a small host state object coordinating {selected conversation, side view: thread | in-chat-search | none}, collapsing to one pane on mobile. Complete and wired but LEAN — NOT a bare two-pane demo, NOT the whole combined app. Reuse existing routing\u002Flayout\u002Fauth; add files + wiring only, never rewrite. Least-code = reach for the drop-ins\u002Fslots (HOW). **The compile-verified TSX + the required column CSS live in `references\u002Flayout.md` (sizing) and `cometchat-react-v7-placement\u002Freferences\u002Frecipes.md` (the Core-surface recipe) — build from those; this entry stays the thin map.**\n\nWire every default-on affordance so nothing dead-ends, and keep these INVARIANTS:\n- **Threads are DEFAULT** (ship with a first-time \"add chat\"). Wire `CometChatMessageList onThreadRepliesClick(m)` → a thread panel (`CometChatThreadHeader` + a thread `CometChatMessageList` + `CometChatMessageComposer`) with a close\u002Fback round-trip. **The thread list AND composer take BOTH the current target (`user` OR `group`, same as the main pane) AND `parentMessageId`; passing `parentMessageId` ALONE silently NEVER SENDS (AUDIT-060).** Set `hideReplyInThreadOption` only on explicit opt-out. **Differentiate the thread MESSAGE LIST** (not just the wrapper): scope `--cometchat-message-list-bg: var(--cometchat-background-color-01)` on the thread wrapper — the list paints its own opaque bg so a wrapper bg can't reach it (verified vs 7.1.0; recipe in `cometchat-react-v7-customization`).\n- **Two searches, both default-on, both need the FULL round-trip (AUDIT-017).** GLOBAL conversation search over the LIST column (`CometChatConversations onSearchBarClicked` → `CometChatSearch`, no uid\u002Fguid — or `showSearchBar={false}`); IN-CHAT scoped search in the SIDE PANEL (`CometChatMessageHeader showSearchOption` default `true` → `onSearchOptionClicked` → `CometChatSearch` with the current `uid`\u002F`guid`, mutually exclusive with the thread). Each renders a back button (`onBack`) you MUST wire to close + return, PLUS `onConversationClicked`\u002F`onMessageClicked` to select the hit — a companion you open, you must also close. (Real server-side search may also need a Dashboard toggle — VERIFY.)\n- **SIZE per the ONE standard — `references\u002Flayout.md`.** The kit fills its parent and ships its own `loadingView`\u002F`emptyView`, so a broken-looking surface is a HOST container-sizing defect (a content-driven box), not a kit bug — two modes: static collapse (~0px sliver) and load-transition reflow (grows into place as content loads). Satisfy the 5 invariants: prepare\u002FRESET the ancestor chain (`html,body,#root{height:100%;margin:0}` + undo the Vite\u002FCRA\u002FNext scaffold center+cap+pad, AUDIT-019\u002F035) · pin the surface to a content-INDEPENDENT `100dvh` (never `min-height`\u002F`auto`) · size COLUMNS with `min-height:0`\u002F`overflow:hidden` (scroll, don't grow the parent) · let the kit loading state fill the pinned box · no `transform`\u002F`filter` ancestors. The 2-column CSS is in `layout.md`; the 3-column\u002Fembedded\u002Fpopup\u002Fsidebar recipes in `cometchat-react-v7-placement`. Keep `CometChatProvider` WRAPPING `.cc-app`, not inside it (the `.cometchat` wrapper breaks the row — AUDIT-036).\n- **Match data scope to the REQUEST (AUDIT-038).** A 1:1\u002FDM-only ask must NOT show the app's seeded groups — scope with the built-in `conversationsRequestBuilder` prop (pass the `CometChat.ConversationsRequestBuilder` INSTANCE, `.setLimit(30).setConversationType(\"user\")` — `setLimit` required; `\"group\"` for groups-only; **reuse the prop, don't hand-roll a client-side filter**), and scope the selector to match (no Groups tab on a 1:1-only app). A generic unscoped \"add chat\" keeps BOTH. Example in `references\u002Fcomponent-props.md`.\n- **Theme:** the kit defaults to `light` and does NOT follow the OS (no `theme=\"system\"`) — sync `CometChatProvider theme=` to `prefers-color-scheme` by default (`references\u002Ftheming.md`, AUDIT-004).\n- **Reuse built-in triggers — don't hand-roll buttons (AUDIT-006).** Wire the props components already expose; custom UI goes IN the component's view slot (search icon → Conversations `headerView` \u002F MessageHeader `trailingView`), NEVER a sibling on top (slot map: `references\u002Fcomponent-props.md`). Unclear prop → fetch its `.md` twin (`references\u002Fdocs-map.md`), never the `.d.ts`.\n- **`CometChatErrorBoundary` wraps the surface** (children required; optional `onError`\u002F`fallbackView`\u002F`componentName`) — a render error then shows a localized fallback + retry, not a blank white screen. It is NOT the initializer (init\u002Flogin still happen first). Leave header call buttons + composer attach\u002Femoji\u002Fvoice as built-in defaults; do NOT turn on gated extensions\u002FAI\u002Fplugins; do NOT add selector tabs \u002F a details or scoped-search side panel \u002F call logs \u002F incoming call (those are the GROWTHS) unless asked — **but the thread panel IS part of the default.** **Prod auth: `loginWithAuthToken` with a per-user server-minted token; the Auth Key is dev-only** (`references\u002Flifecycle.md`).\n\n**Grows on request → the full combined app** (users\u002Fgroups\u002Fcalls **tabs**, a details\u002Fthread\u002Fscoped-search **side panel**, `CometChatIncomingCall` at root, **calls**, individual **features**) — the UNION of these growths. The compile-verified combined-app recipe (with the required column CSS + `CometChatErrorBoundary`) is baked in **`cometchat-react-v7-placement`**; build the grown app from it. A user who scopes DOWN (embed\u002Fpopup\u002Fsidebar) → the matching `cometchat-react-v7-placement` variant.\n\n## Deep references (load ONLY when the task needs them — keeps this file light on run)\n- `references\u002Fsetup-credentials.md` — detect, config reuse, version_conflict, dashboard creds, env, authorize.\n- `references\u002Flifecycle.md` — init-once + StrictMode, concurrent-login guard (`ensureLoggedIn`), get-current-UID (sync vs async), prod auth-token, logout, the full `CometChatProvider`.\n- `references\u002Flayout.md` — **the ONE reflow-free-surface sizing standard** (the 5 invariants: prepared ancestor chain · pinned content-independent height · `min-height:0` columns · kit loading state inside the pinned box = NO load-transition reflow · no `transform`\u002F`filter` ancestors). `placement` + `calls` reference it too — change sizing rules HERE.\n- `references\u002Fssr.md` — Next.js \u002F Astro \u002F React Router SSR safety (`\"use client\"`, `ssr:false`, `client:only`).\n- `references\u002Ftheming.md` — CSS import-once + `--cometchat-*` variables (depth: `cometchat-react-v7-customization`).\n- Localization \u002F RTL \u002F accessibility → the cross-family **`cometchat-i18n`** + **`cometchat-a11y`** skills. Don't render a raw key (`group_info`) — the provider auto-wires localization. React theme tokens: `references\u002Ftheming.md`.\n- `references\u002Fanti-patterns.md` — the 15 real-bug anti-patterns (incl. `transform`\u002FTailwind overlay bug, container dimensions, **scaffold-boilerplate** = centered\u002Fcapped\u002Fgutter-boxed chat (#15), **global-CSS-leak** = centered names \u002F expanding header, **raw-i18n-key** rendering).\n- `references\u002Fdependencies.md` — packages, major pins, `CometChat.*` SDK types, bundle-size cost transparency.\n- `references\u002Fcomponent-props.md` — **BAKED stable props + view slots** for the 4 drop-ins (where custom UI goes IN each component — search → Conversations `headerView`, MessageHeader `trailingView`, etc.).\n- `references\u002Fdocs-map.md` — intent → the exact docs `.md` twin to fetch (replaces reading `.d.ts`); **for a whole feature\u002Ftask, its \"Task guides (recipes)\" section says to BUILD FROM the official guide + COMPARE your implementation against it (docs-maximal), then apply the hardening deltas.**\n- Symptom → cause → fix (blank screen, SSR `window is not defined`, ~0px collapse, kit error state, empty lists, events not firing, `version_conflict`) → the **`cometchat-react-v7-troubleshooting`** skill.\n\n> **Visual Builder (VCB) is out of scope.** If asked to integrate a VCB export, point to the CometChat Visual Builder docs (via `references\u002Fdocs-map.md`); don't hand-roll a builder-export flow.\n\n## Common pitfalls (top 4 — full list in `references\u002Fanti-patterns.md`)\nversion_conflict (v6 installed) · wrong Region or env prefix · Auth Key shipped to prod client · rendering\u002Flogin before init resolves.\n\n## Verify it works\nStart the app → confirm `init()` then `login()` resolve → the `CometChatConversations` list renders inside `CometChatProvider` (itself inside `CometChatErrorBoundary`) at full size (not a collapsed sliver); open a conversation → the message pane loads and messages send\u002Freceive; **clicking \"reply in thread\" opens the thread panel (default) and its back\u002Fclose returns to the list** (hidden only if the user opted out), and the thread's MESSAGE LIST reads as a distinct surface matching its own header\u002Fcomposer (not the same shade as the main list — the `--cometchat-message-list-bg` override is scoped on the thread wrapper); **clicking the message-header search icon opens an in-chat search in the side panel scoped to THAT conversation (default), with back to close**; the conversations search bar is wired-or-hidden (no dead-ends); on a narrow viewport it collapses to one pane at a time (list → message → thread\u002Fsearch → back). Blank white screen ⇒ something rendered before `init()` resolved, the Region \u002F env prefix is wrong, or an unbounded render error escaped (add `CometChatErrorBoundary`). A list + message pane with no sizing \u002F no error boundary \u002F dead-ending affordances ⇒ under-delivery (see the golden path). Growing to the full app (tabs + side panel + incoming call) ⇒ verify per `cometchat-react-v7-placement`.\n\n## Explain what you built (REQUIRED close)\nAfter it builds + verifies, don't dump silently — tell the user briefly: **(1) what I wired** (3–5 bullets, NAME the files); **(2) decisions & why**, flagging dev-only AS dev-only (dev **Auth Key** → server auth token for prod; the `\u003Cuid>`; OS-follow theme); **(3) what I did NOT touch** (additive — routing\u002Fauth\u002Fstyles intact). Then **(4) offer these THREE options as a SELECTABLE choice and WAIT for the user's pick — do NOT auto-continue:**\n- **(1) Add another feature** → **first check what's ALREADY there, then suggest only the GAP (AUDIT-043).** Read what's wired (the emitted code you built) and ASK which dashboard-gated extensions are already enabled (you can't reliably read per-app dashboard state — don't assume OFF). SUGGEST 3–4 grow-set items that are NEITHER wired NOR already enabled (voice\u002Fvideo **calls** · **search** · **threads** if off · **push** · **AI\u002Fsmart-replies** · **moderation** · polls\u002Fstickers\u002Ftranslation) — **never re-suggest something already on (e.g. translation already enabled in the dashboard)**. **Do NOT suggest `reactions` or `mentions` — they are ON BY DEFAULT in v7 (core messaging; their dashboard extensions are \"(Legacy)\", already in core — AUDIT-077); if the user asks, say they're already on and offer to customize them.** Then build the chosen one (→ `cometchat-react-v7-features` \u002F `cometchat-react-v7-calls`).\n- **(2) Customize theming** → ask whether they already have a **preset \u002F brand theme** (a brand color, light\u002Fdark, or match an existing design system) or want to talk through the options, then wire it (→ `cometchat-react-v7-customization`).\n- **(3) Test it manually** → do NOTHING further — hand it back so the user runs and checks it themselves.\n\nA PARKED capability (push · migration · SDK-only) → isn't in this pack yet: say so honestly + link CometChat's docs. **This 3-option close runs after EVERY implementation (`RULES.md` §19 \u002F AUDIT-040).**\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"cometchat react core chat integration uikit v7 setup credentials","CometChat","1.3.0","Node.js >=18; React >=18; Vite >=4 \u002F CRA \u002F Next.js; @cometchat\u002Fchat-uikit-react ^7 (7.2.x, verified 7.2.4); @cometchat\u002Fchat-sdk-javascript ^4.1.9","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-core",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-core",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002FSKILL.md",true,[79,85,89,93,97,101,105,109,113],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fanti-patterns.md","REFERENCE","参考文档",7982,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fanti-patterns.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcomponent-props.md",9763,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fcomponent-props.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdependencies.md",1352,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fdependencies.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fdocs-map.md",9836,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fdocs-map.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Flayout.md",9934,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Flifecycle.md",6171,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Flifecycle.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsetup-credentials.md",9529,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fsetup-credentials.md",{"path":110,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fssr.md",1185,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Fssr.md",{"path":114,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Ftheming.md",5388,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-core\u002Freferences\u002Ftheming.md",[118,127,135,143,151,159],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":126},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":126},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":126},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":126},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":155,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":126},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":126},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]