[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFKQ06WRT2535TYAB4QRQK":3,"skill-same:01M6MFKQ06WRT2535TYAB4QRQK":85},{"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},"01M6MFKQ06WRT2535TYAB4QRQK","cometchat-react-v7-placement",null,"Where CometChat chat goes in a React app shell and how to wire each layout — full-screen, sidebar\u002Fsplit, popup\u002Fwidget, or embedded in an existing page. Triggers: 'add chat as a sidebar', 'full screen chat page', 'chat popup widget', 'embed chat in my dashboard'.","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-placement\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 placement","cometchat","react","add","embed","split","uikit","Existing","triggers","page","as","goes","app","full","my","verified","screen","how","layout","dashboard","how to","2026-11-10 10:12:30",false,"---\nname: cometchat-react-v7-placement\ndescription: \"Where CometChat chat goes in a React app shell and how to wire each layout — full-screen, sidebar\u002Fsplit, popup\u002Fwidget, or embedded in an existing page. Triggers: 'add chat as a sidebar', 'full screen chat page', 'chat popup widget', 'embed chat in my dashboard'.\"\nlicense: \"MIT\"\ncompatibility: \"React >=18; @cometchat\u002Fchat-uikit-react ^7 (7.2.x, verified 7.2.4)\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.1.0\"\n  tags: \"cometchat react placement layout uikit v7\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7`. Uses only components defined in `cometchat-react-v7-core`\u002F`-components` (from live v7 docs). Status: **catalog-verified vs installed 7.1.0 (exports-only web-v7.json).** Fetch layout-specific props from the component's **`.md` twin** (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`).\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — install, `init→login→render`, provider. This skill ASSUMES it.\n- `cometchat-react-v7-components` — the component catalog this composes.\n\n## Use this skill when\nDeciding\u002F​wiring WHERE chat lives — and either (a) **growing the core surface into the whole combined chat app** (selector tabs ↔ messages ↔ details\u002Fthread\u002Fsearch side panel + incoming call) when the user asks for the full app, or (b) a scoped-down sidebar\u002Fsplit, popup\u002Ffloating widget, or embedded panel. Triggers: \"build a full chat app\", \"add users\u002Fgroups\u002Fcalls tabs and a side panel\", \"add chat as a sidebar\", \"full screen chat page\", \"chat popup widget\", \"embed chat in my dashboard\". Note: a plain unscoped \"add chat\" defaults to the production-ready CORE surface (list ↔ message pane) in `cometchat-react-v7-core` — grow to the combined app below only on request.\n\n## Prerequisites & install\nCovered by core. No new package.\n\n## Placement patterns (BAKED) — each composes core components\n- **Core surface (THE DEFAULT for an unscoped \"add chat\") — production-ready, but lean.** Inside `CometChatErrorBoundary` → ONE `CometChatProvider`, a **two-column** layout: a `CometChatConversations` LIST ↔ a MESSAGE pane (`CometChatMessageHeader` + `CometChatMessageList` + `CometChatMessageComposer`), sized per `..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`, with the **thread-replies panel** and the **in-chat scoped message search** wired by DEFAULT (opt-out only) and the global conversation search bar wired-or-hidden, collapsing to one pane on mobile. One small host state object coordinates {selected conversation, which side view (thread | in-chat-search | none)}. Complete and wired — NOT a bare demo — but NOT the whole app. See the \"Core-surface recipe\" below.\n- **Grow to the full combined app (on request) — the whole app the official sample ships.** When the user asks for the full app, grow the core surface into a **three-column** layout, all under `CometChatErrorBoundary` → ONE `CometChatProvider`: a SELECTOR column (the list for the active tab — `CometChatConversations` \u002F `CometChatUsers` \u002F `CometChatGroups` \u002F `CometChatCallLogs` — + a tab bar), a MESSAGE pane, and a mutually-exclusive SIDE panel (user\u002Fgroup details, a thread `CometChatThreadHeader` + list\u002Fcomposer, or a scoped `CometChatSearch`), plus `CometChatIncomingCall` mounted at root. One host state object coordinates {active tab, selected user\u002Fgroup, thread parent, which side panel}. It is the UNION of the core surface + these growths — see the \"Combined-app recipe (grow target)\" below. Least-code = reach for these drop-ins (HOW).\n- **Sidebar \u002F split:** conversations list in a fixed side panel; the message pane fills the rest. Selection state links list → message pane. (Scoped-down variant.)\n- **Popup \u002F floating widget:** a toggle button mounts the chat panel in an overlay; keep `CometChatProvider` mounted at app root so init\u002Flogin persist across open\u002Fclose. (Scoped-down variant.)\n- **Embedded panel:** drop the message components into an existing page region; reuse the host layout\u002Fcontainers. (Scoped-down variant.)\n\n> Default to the CORE surface for a plain \"add chat\"; grow to the full combined app when the user asks for the whole app; honor an explicit smaller scope (the narrower three).\n\n\n## Recipes (FETCH — `references\u002Frecipes.md`)\nThe two production recipes — full TSX + the 3-column CSS — live in `references\u002Frecipes.md` (progressive disclosure; load it when you build):\n- **Core-surface recipe** — THE DEFAULT for a plain \"add chat\": `CometChatErrorBoundary` → one `CometChatProvider` → two-column list ↔ message pane, thread panel + in-chat scoped search wired by default, mobile one-pane collapse.\n- **Combined-app recipe** — the GROW target (whole app, on request): three columns (selector tabs ↔ message pane ↔ mutually-exclusive details\u002Fthread\u002Fsearch side panel) + `CometChatIncomingCall`.\n\nBoth encode the same invariants — **keep them when you emit the code**:\n> **Selection has THREE obligations (AUDIT-079)** — a selection that only opens a pane is a dead-end: (1) render the pane; (2) REFLECT it in the list (pass `activeConversation`\u002F`activeUser`\u002F`activeGroup` so the row highlights); (3) every opened side panel is CLOSEABLE (wire `onBack`\u002F`onClose`).\n> **A list-header action (\"New chat\"\u002F\"Create group\") goes in the list's `headerView`** — which REPLACES the default header, so render the title AND the button together inside it — NOT a sibling above the list (AUDIT-083; pattern in `..\u002Fcometchat-react-v7-core\u002Freferences\u002Fcomponent-props.md`).\n\nBoth satisfy the reflow-free-surface standard (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`) and collapse to one pane on mobile (below). The recipes use the `useIsMobile` hook defined in the **Responsive \u002F mobile** section below.\n\n## Responsive \u002F mobile — one screen at a time (MANDATORY for any multi-pane layout)\nEvery pattern above that shows more than one pane (full-screen two-pane, sidebar\u002Fsplit, list+thread\u002Fdetail) MUST collapse to a SINGLE screen at a time on small viewports — a fixed side-by-side layout that squashes on a phone is a defect (`RULES.md` §14), not a style choice. The kit has **no responsive shell** (no `WithMessages`\u002F`CometChatUI`); you compose it from the same selection state, gated by a breakpoint.\n- **Mobile = a navigation stack:** conversations list → tap a conversation → the message pane REPLACES the list full-screen → tap the header → the profile\u002Fthread panel REPLACES the message pane. Wide viewport → the SAME state renders side-by-side.\n- **Reuse the built-in back button (don't hand-roll one):** `CometChatMessageHeader` ships `hideBackButton` (default `false`) + `onBack()`. On mobile wire `onBack` to clear the selection (pop to the list) and keep the button visible; on wide set `hideBackButton` (the list is always there).\n\n```tsx\n\u002F\u002F SSR-guarded breakpoint hook\nfunction useIsMobile(query = \"(max-width: 768px)\") {\n  const read = () => typeof window !== \"undefined\" && window.matchMedia(query).matches;\n  const [m, setM] = useState(read);\n  useEffect(() => {\n    const mq = window.matchMedia(query);\n    const on = () => setM(mq.matches);\n    mq.addEventListener(\"change\", on);\n    return () => mq.removeEventListener(\"change\", on);\n  }, [query]);\n  return m;\n}\n\n\u002F\u002F Mobile: render exactly ONE pane based on state; wide: render them side-by-side.\nconst isMobile = useIsMobile();\nif (isMobile) {\n  if (detail && selected) return \u003CDetailOrThread onClose={() => setDetail(null)} \u002F>;\n  if (selected) return (\n    \u003CMessagePane>\n      \u003CCometChatMessageHeader {...target} hideBackButton={false} onBack={() => setSelected(null)} \u002F>\n      {\u002F* list + composer *\u002F}\n    \u003C\u002FMessagePane>\n  );\n  return \u003CCometChatConversations onItemClick={pick} \u002F>;   \u002F\u002F list only\n}\n\u002F\u002F wide → the two\u002Fthree-pane layout, header with hideBackButton\n```\nNative (RN\u002FFlutter): use the platform navigator (stack navigation) — one screen per route — not a web split view.\n\n## Layout wiring per placement\n- **Every placement satisfies the reflow-free-surface standard (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`)** — pin a content-INDEPENDENT height (full-screen → `100dvh`; sidebar\u002Fsplit → the panes take a viewport or flex\u002Fgrid-supplied height; popup\u002Fembedded → a fixed height e.g. `600px` or a sized grid\u002Fflex cell — **never `min-height`\u002F`auto`**), prepare the ancestor chain, and size the columns with `min-height:0`\u002F`overflow:hidden`. The kit fills its parent, so a content-driven container both collapses the chat to ~0px AND grows-into-place as content loads (the two named failure modes).\n- Keep `CometChatProvider` at a stable ancestor (not remounted per route\u002Ftoggle) so init+login survive navigation.\n- Manage the selected conversation\u002Fuser\u002Fgroup in host state and pass it to the message components. Fetch the exact selection props from the component's `.md` twin (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`).\n- Reuse the app's existing routing\u002Flayout; add wiring, never rewrite (`RULES.md`).\n- **Open an overlay\u002Fcompanion IN the pane its trigger lives in — not full-screen (AUDIT-014).** Search opened from the `CometChatConversations` search bar (`onSearchBarClicked` → `CometChatSearch`) renders **in the conversations list column, over the list** — the message pane stays visible; `onBack`\u002Fresult-click returns to the list. Do NOT take over the whole screen (it hides the conversation the user was reading). Header search (`onSearchOptionClicked`, scoped by `uid`\u002F`guid`) opens the same way. A full-screen replacement is correct ONLY on a **mobile single-pane** (§ responsive), where the search IS the list-level screen. Same principle for any pane-rooted affordance (thread\u002Fprofile open in the side panel, not full-screen on desktop).\n\n```tsx\n\u002F\u002F Wide: the LEFT column shows search when open, else the list — message pane stays.\nconst listColumn = searchOpen\n  ? \u003CCometChatSearch onBack={() => setSearchOpen(false)} onConversationClicked={pick} onMessageClicked={jump} \u002F>\n  : \u003CCometChatConversations showSearchBar onSearchBarClicked={() => setSearchOpen(true)} onItemClick={pick} \u002F>;\n\u002F\u002F \u003Caside className=\"list-column\">{listColumn}\u003C\u002Faside> \u003Cmain>{messagePane}\u003C\u002Fmain>\n\u002F\u002F Mobile (single-pane): if (searchOpen) render \u003CCometChatSearch\u002F> full-screen (it's the list screen).\n```\n\n## Common pitfalls (BAKED)\n- Remounting `CometChatProvider` on every route\u002Ftoggle (re-triggers init\u002Flogin). Rendering the message pane before a conversation is selected. Nesting multiple providers.\n- **Shipping a fixed side-by-side layout with no small-viewport collapse** — the #1 layout defect. On a phone the list + message panes squash and tapping a conversation does nothing visible. Always add the mobile single-pane branch above and wire the header's built-in `onBack` (AUDIT-011).\n- **Not wrapping the surface in `CometChatErrorBoundary`** — a render error in any kit component then blanks the whole page (white screen) instead of showing a localized fallback + retry. Both recipes above wrap the surface; keep it.\n- **A surface that grows into place as content loads (load-transition reflow)** — small while the list loads, then jumps to full size. The box is content-driven, not pinned: satisfy `layout.md` (pinned `100dvh`, prepared ancestor chain, `min-height:0` columns) and let the kit's own `loadingView`\u002F`emptyView` fill the pinned box — don't gate the surface behind your own placeholder→chat swap (AUDIT-023).\n- **Over-delivering the whole combined app on a plain \"add chat\"** — the default is the Core-surface recipe (list ↔ message pane); grow to the Combined-app recipe (selector tabs + side panel + incoming call) only when the user asks for the whole app.\n\n## Verify it works\nChat renders in the chosen layout inside a `CometChatErrorBoundary`, and on a narrow viewport it collapses to ONE pane at a time (list → message → back) — no squashed side-by-side panes on a phone. Default \"add chat\" ⇒ the Core-surface recipe (list ↔ message pane, sized, affordances wired-or-hidden); the whole combined app (tabs + side panel + incoming call) is the grow target for an explicit full-app ask.\n\n**Close (after it builds):** end with the shared 3-option selectable menu and WAIT for the pick — **(1) add another feature** (suggest a few not-yet-wired) · **(2) customize theming** · **(3) test it manually** (stop; let the user check). Same contract as the `cometchat-react-v7-core` close (`RULES.md` §19).\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7`. Uses only components defined in `cometchat-react-v7-core`\u002F`-components` (from live v7 docs). Status: **catalog-verified vs installed 7.1.0 (exports-only web-v7.json).** Fetch layout-specific props from the component's **`.md` twin** (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`).\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — install, `init→login→render`, provider. This skill ASSUMES it.\n- `cometchat-react-v7-components` — the component catalog this composes.\n\n## Use this skill when\nDeciding\u002F​wiring WHERE chat lives — and either (a) **growing the core surface into the whole combined chat app** (selector tabs ↔ messages ↔ details\u002Fthread\u002Fsearch side panel + incoming call) when the user asks for the full app, or (b) a scoped-down sidebar\u002Fsplit, popup\u002Ffloating widget, or embedded panel. Triggers: \"build a full chat app\", \"add users\u002Fgroups\u002Fcalls tabs and a side panel\", \"add chat as a sidebar\", \"full screen chat page\", \"chat popup widget\", \"embed chat in my dashboard\". Note: a plain unscoped \"add chat\" defaults to the production-ready CORE surface (list ↔ message pane) in `cometchat-react-v7-core` — grow to the combined app below only on request.\n\n## Prerequisites & install\nCovered by core. No new package.\n\n## Placement patterns (BAKED) — each composes core components\n- **Core surface (THE DEFAULT for an unscoped \"add chat\") — production-ready, but lean.** Inside `CometChatErrorBoundary` → ONE `CometChatProvider`, a **two-column** layout: a `CometChatConversations` LIST ↔ a MESSAGE pane (`CometChatMessageHeader` + `CometChatMessageList` + `CometChatMessageComposer`), sized per `..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`, with the **thread-replies panel** and the **in-chat scoped message search** wired by DEFAULT (opt-out only) and the global conversation search bar wired-or-hidden, collapsing to one pane on mobile. One small host state object coordinates {selected conversation, which side view (thread | in-chat-search | none)}. Complete and wired — NOT a bare demo — but NOT the whole app. See the \"Core-surface recipe\" below.\n- **Grow to the full combined app (on request) — the whole app the official sample ships.** When the user asks for the full app, grow the core surface into a **three-column** layout, all under `CometChatErrorBoundary` → ONE `CometChatProvider`: a SELECTOR column (the list for the active tab — `CometChatConversations` \u002F `CometChatUsers` \u002F `CometChatGroups` \u002F `CometChatCallLogs` — + a tab bar), a MESSAGE pane, and a mutually-exclusive SIDE panel (user\u002Fgroup details, a thread `CometChatThreadHeader` + list\u002Fcomposer, or a scoped `CometChatSearch`), plus `CometChatIncomingCall` mounted at root. One host state object coordinates {active tab, selected user\u002Fgroup, thread parent, which side panel}. It is the UNION of the core surface + these growths — see the \"Combined-app recipe (grow target)\" below. Least-code = reach for these drop-ins (HOW).\n- **Sidebar \u002F split:** conversations list in a fixed side panel; the message pane fills the rest. Selection state links list → message pane. (Scoped-down variant.)\n- **Popup \u002F floating widget:** a toggle button mounts the chat panel in an overlay; keep `CometChatProvider` mounted at app root so init\u002Flogin persist across open\u002Fclose. (Scoped-down variant.)\n- **Embedded panel:** drop the message components into an existing page region; reuse the host layout\u002Fcontainers. (Scoped-down variant.)\n\n> Default to the CORE surface for a plain \"add chat\"; grow to the full combined app when the user asks for the whole app; honor an explicit smaller scope (the narrower three).\n\n\n## Recipes (FETCH — `references\u002Frecipes.md`)\nThe two production recipes — full TSX + the 3-column CSS — live in `references\u002Frecipes.md` (progressive disclosure; load it when you build):\n- **Core-surface recipe** — THE DEFAULT for a plain \"add chat\": `CometChatErrorBoundary` → one `CometChatProvider` → two-column list ↔ message pane, thread panel + in-chat scoped search wired by default, mobile one-pane collapse.\n- **Combined-app recipe** — the GROW target (whole app, on request): three columns (selector tabs ↔ message pane ↔ mutually-exclusive details\u002Fthread\u002Fsearch side panel) + `CometChatIncomingCall`.\n\nBoth encode the same invariants — **keep them when you emit the code**:\n> **Selection has THREE obligations (AUDIT-079)** — a selection that only opens a pane is a dead-end: (1) render the pane; (2) REFLECT it in the list (pass `activeConversation`\u002F`activeUser`\u002F`activeGroup` so the row highlights); (3) every opened side panel is CLOSEABLE (wire `onBack`\u002F`onClose`).\n> **A list-header action (\"New chat\"\u002F\"Create group\") goes in the list's `headerView`** — which REPLACES the default header, so render the title AND the button together inside it — NOT a sibling above the list (AUDIT-083; pattern in `..\u002Fcometchat-react-v7-core\u002Freferences\u002Fcomponent-props.md`).\n\nBoth satisfy the reflow-free-surface standard (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`) and collapse to one pane on mobile (below). The recipes use the `useIsMobile` hook defined in the **Responsive \u002F mobile** section below.\n\n## Responsive \u002F mobile — one screen at a time (MANDATORY for any multi-pane layout)\nEvery pattern above that shows more than one pane (full-screen two-pane, sidebar\u002Fsplit, list+thread\u002Fdetail) MUST collapse to a SINGLE screen at a time on small viewports — a fixed side-by-side layout that squashes on a phone is a defect (`RULES.md` §14), not a style choice. The kit has **no responsive shell** (no `WithMessages`\u002F`CometChatUI`); you compose it from the same selection state, gated by a breakpoint.\n- **Mobile = a navigation stack:** conversations list → tap a conversation → the message pane REPLACES the list full-screen → tap the header → the profile\u002Fthread panel REPLACES the message pane. Wide viewport → the SAME state renders side-by-side.\n- **Reuse the built-in back button (don't hand-roll one):** `CometChatMessageHeader` ships `hideBackButton` (default `false`) + `onBack()`. On mobile wire `onBack` to clear the selection (pop to the list) and keep the button visible; on wide set `hideBackButton` (the list is always there).\n\n```tsx\n\u002F\u002F SSR-guarded breakpoint hook\nfunction useIsMobile(query = \"(max-width: 768px)\") {\n  const read = () => typeof window !== \"undefined\" && window.matchMedia(query).matches;\n  const [m, setM] = useState(read);\n  useEffect(() => {\n    const mq = window.matchMedia(query);\n    const on = () => setM(mq.matches);\n    mq.addEventListener(\"change\", on);\n    return () => mq.removeEventListener(\"change\", on);\n  }, [query]);\n  return m;\n}\n\n\u002F\u002F Mobile: render exactly ONE pane based on state; wide: render them side-by-side.\nconst isMobile = useIsMobile();\nif (isMobile) {\n  if (detail && selected) return \u003CDetailOrThread onClose={() => setDetail(null)} \u002F>;\n  if (selected) return (\n    \u003CMessagePane>\n      \u003CCometChatMessageHeader {...target} hideBackButton={false} onBack={() => setSelected(null)} \u002F>\n      {\u002F* list + composer *\u002F}\n    \u003C\u002FMessagePane>\n  );\n  return \u003CCometChatConversations onItemClick={pick} \u002F>;   \u002F\u002F list only\n}\n\u002F\u002F wide → the two\u002Fthree-pane layout, header with hideBackButton\n```\nNative (RN\u002FFlutter): use the platform navigator (stack navigation) — one screen per route — not a web split view.\n\n## Layout wiring per placement\n- **Every placement satisfies the reflow-free-surface standard (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Flayout.md`)** — pin a content-INDEPENDENT height (full-screen → `100dvh`; sidebar\u002Fsplit → the panes take a viewport or flex\u002Fgrid-supplied height; popup\u002Fembedded → a fixed height e.g. `600px` or a sized grid\u002Fflex cell — **never `min-height`\u002F`auto`**), prepare the ancestor chain, and size the columns with `min-height:0`\u002F`overflow:hidden`. The kit fills its parent, so a content-driven container both collapses the chat to ~0px AND grows-into-place as content loads (the two named failure modes).\n- Keep `CometChatProvider` at a stable ancestor (not remounted per route\u002Ftoggle) so init+login survive navigation.\n- Manage the selected conversation\u002Fuser\u002Fgroup in host state and pass it to the message components. Fetch the exact selection props from the component's `.md` twin (`..\u002Fcometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`).\n- Reuse the app's existing routing\u002Flayout; add wiring, never rewrite (`RULES.md`).\n- **Open an overlay\u002Fcompanion IN the pane its trigger lives in — not full-screen (AUDIT-014).** Search opened from the `CometChatConversations` search bar (`onSearchBarClicked` → `CometChatSearch`) renders **in the conversations list column, over the list** — the message pane stays visible; `onBack`\u002Fresult-click returns to the list. Do NOT take over the whole screen (it hides the conversation the user was reading). Header search (`onSearchOptionClicked`, scoped by `uid`\u002F`guid`) opens the same way. A full-screen replacement is correct ONLY on a **mobile single-pane** (§ responsive), where the search IS the list-level screen. Same principle for any pane-rooted affordance (thread\u002Fprofile open in the side panel, not full-screen on desktop).\n\n```tsx\n\u002F\u002F Wide: the LEFT column shows search when open, else the list — message pane stays.\nconst listColumn = searchOpen\n  ? \u003CCometChatSearch onBack={() => setSearchOpen(false)} onConversationClicked={pick} onMessageClicked={jump} \u002F>\n  : \u003CCometChatConversations showSearchBar onSearchBarClicked={() => setSearchOpen(true)} onItemClick={pick} \u002F>;\n\u002F\u002F \u003Caside className=\"list-column\">{listColumn}\u003C\u002Faside> \u003Cmain>{messagePane}\u003C\u002Fmain>\n\u002F\u002F Mobile (single-pane): if (searchOpen) render \u003CCometChatSearch\u002F> full-screen (it's the list screen).\n```\n\n## Common pitfalls (BAKED)\n- Remounting `CometChatProvider` on every route\u002Ftoggle (re-triggers init\u002Flogin). Rendering the message pane before a conversation is selected. Nesting multiple providers.\n- **Shipping a fixed side-by-side layout with no small-viewport collapse** — the #1 layout defect. On a phone the list + message panes squash and tapping a conversation does nothing visible. Always add the mobile single-pane branch above and wire the header's built-in `onBack` (AUDIT-011).\n- **Not wrapping the surface in `CometChatErrorBoundary`** — a render error in any kit component then blanks the whole page (white screen) instead of showing a localized fallback + retry. Both recipes above wrap the surface; keep it.\n- **A surface that grows into place as content loads (load-transition reflow)** — small while the list loads, then jumps to full size. The box is content-driven, not pinned: satisfy `layout.md` (pinned `100dvh`, prepared ancestor chain, `min-height:0` columns) and let the kit's own `loadingView`\u002F`emptyView` fill the pinned box — don't gate the surface behind your own placeholder→chat swap (AUDIT-023).\n- **Over-delivering the whole combined app on a plain \"add chat\"** — the default is the Core-surface recipe (list ↔ message pane); grow to the Combined-app recipe (selector tabs + side panel + incoming call) only when the user asks for the whole app.\n\n## Verify it works\nChat renders in the chosen layout inside a `CometChatErrorBoundary`, and on a narrow viewport it collapses to ONE pane at a time (list → message → back) — no squashed side-by-side panes on a phone. Default \"add chat\" ⇒ the Core-surface recipe (list ↔ message pane, sized, affordances wired-or-hidden); the whole combined app (tabs + side panel + incoming call) is the grow target for an explicit full-app ask.\n\n**Close (after it builds):** end with the shared 3-option selectable menu and WAIT for the pick — **(1) add another feature** (suggest a few not-yet-wired) · **(2) customize theming** · **(3) test it manually** (stop; let the user check). Same contract as the `cometchat-react-v7-core` close (`RULES.md` §19).\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"cometchat react placement layout uikit v7","CometChat","1.1.0","React >=18; @cometchat\u002Fchat-uikit-react ^7 (7.2.x, verified 7.2.4)","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-placement",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-placement",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-placement",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-placement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-placement\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Frecipes.md","REFERENCE","参考文档",25565,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-placement\u002Freferences\u002Frecipes.md",[86,95,103,111,119,127],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":94},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":94},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":94},"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":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":94},"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",[],[]]