[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFG1A4RGYEMAPPMJA25EY9":3,"skill-same:01M6MFG1A4RGYEMAPPMJA25EY9":109},{"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},"01M6MFG1A4RGYEMAPPMJA25EY9","cometchat-react-native-core",null,"Foundational rules for the CometChat React Native UI Kit v5 — install and the exact native peer deps, the provider chain, init → login → render ordering, the component map, and the production-ready core chat surface. Read this first for any React Native CometChat task. Triggers: add chat to my React Native app, CometChat React Native setup, Expo chat, RN chat UI kit, integrate CometChat RN, log out of chat RN, add a logout button, chat lifecycle React Native.","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-native-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],"react","cometchat","core","react native","cometchat react native core","native","app","ready","deps","initialization","chain","render","chat ui","init","kit","production-ready","map","log","component","login","read","2026-11-10 10:12:30",false,"---\nname: cometchat-react-native-core\ndescription: \"Foundational rules for the CometChat React Native UI Kit v5 — install and the exact native peer deps, the provider chain, init → login → render ordering, the component map, and the production-ready core chat surface. Read this first for any React Native CometChat task. Triggers: add chat to my React Native app, CometChat React Native setup, Expo chat, RN chat UI kit, integrate CometChat RN, log out of chat RN, add a logout button, chat lifecycle React Native.\"\nlicense: \"MIT\"\ncompatibility: \"Node.js >=18; React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0; @cometchat\u002Fchat-sdk-react-native ^4.0.28; optional @cometchat\u002Fcalls-sdk-react-native ^5.0.4\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"chat cometchat react-native expo core rules initialization provider native\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json` (216 public symbols) +\n> `features.rn-v5.json`. Official docs: \u003Chttps:\u002F\u002Fwww.cometchat.com\u002Fdocs\u002Fui-kit\u002Freact-native\u002Foverview> ·\n> scoped index `...\u002Fui-kit\u002Freact-native\u002Fllms-react-native-v5.md`. Verify every symbol against the catalog;\n> fetch signatures from docs (`references\u002Fdocs-map.md`); never trust memory.\n>\n> ⚠️ **React Native is NOT React.** Different package, different API, native views instead of DOM.\n> A React UI Kit snippet will not compile here. `references\u002Fdocs-map.md` ends with the verified\n> React → React Native name table — read it before porting anything.\n\n## Use this skill when\n- \"add chat to my React Native app\" · \"integrate CometChat in Expo\" · \"RN chat UI\"\n- any React Native CometChat task — it is the assumed base for every other `cometchat-react-native-*` skill\n\n## Prerequisites & install\n\n**One package per platform.** Never mix `@cometchat\u002Fchat-uikit-react` (web) into an RN app.\n\n```bash\nnpm install @cometchat\u002Fchat-uikit-react-native@5 @cometchat\u002Fchat-sdk-react-native@4\n```\n\nThen the **native peer deps — required, not optional.** Verified against `5.4.0` + the integration pages:\n\n```bash\nnpm install @react-native-clipboard\u002Fclipboard \\\n  react-native-gesture-handler react-native-svg react-native-video react-native-localize \\\n  react-native-safe-area-context @react-native-async-storage\u002Fasync-storage@^2.1.2 dayjs\n# Expo also needs: punycode\n```\n\n`cd ios && pod install` for bare RN. **A missing native module fails at MOUNT, not at build** — the\nerror names a NativeModule, not CometChat, so it reads as unrelated.\n\n⚠️ **React Native >= 0.87:** RN removed `InteractionManager` from core and the kit (through 5.5.0)\nstill calls it in the composer's iOS send path, so **sending a message throws on iOS** — it builds,\ntypechecks and bundles clean. Fix and shim: `cometchat-react-native-troubleshooting` -> *Sending a\nmessage throws on iOS*.\n\n\n## Setup & credentials (essentials — full detail: `references\u002Fsetup-credentials.md`)\n1. **Detect** the project: Expo (`app.json`\u002F`app.config.js`) or bare RN (`metro.config.js`). Reuse an existing `.cometchat\u002Fconfig.json` or env if present — skip re-setup.\n2. **version_conflict — STOP** if `@cometchat\u002Fchat-uikit-react-native` is already in `package.json` at a non-v5 major; reconcile first, never mix majors (`RULES.md`).\n3. **Credentials — OFFER the dashboard fetch FIRST** (never silently \"paste it yourself\" — AUDIT-039). 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 values; **(b) manual paste** from Dashboard → Credentials (dev-only Auth Key). **Then the SKILL writes the env (§4)** — the MCP only returns the values; env-writing and codegen are the SKILL's job. Full flow: `references\u002Fsetup-credentials.md`.\n4. **Write env**: bare RN → `.env` (read via `react-native-config`); Expo → `.env` (read via `Constants.expoConfig.extra` or `process.env`). Gitignore it; never echo the Auth Key. Prod → server-minted auth token, not the Auth Key. **Nothing in a mobile bundle is secret** (IPA\u002FAPK are readable) — see `references\u002Fsetup-credentials.md`.\n5. **Authorize** = `initFromSettings` then `login` both resolve; auth error is almost always the wrong Region.\n\n## Integration ordering (BAKED — invariant)\n\n**`init()` must resolve before `login()`. `login()` must resolve before you render any component.**\nBreaking it gives a blank screen, not an error.\n\nUse **`initFromSettings`**, not the classic `init` — it persists `integrationSource=\"ai-agent\"`\nso CometChat can attribute the integration. The classic init does not (AUDIT-084), and a machine\ngate enforces this.\n\n```tsx\nimport { CometChatUIKit } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\n\nconst settings: CometChat.CometChatSettings = {\n  appId: APP_ID,\n  region: REGION,\n  credentials: { authKey: AUTH_KEY }, \u002F\u002F dev only — production mints an auth token server-side\n  chatSDK: {\n    presenceSubscription: { type: \"ALL_USERS\" },\n    autoEstablishSocketConnection: true,\n  },\n};\n\nawait CometChatUIKit.initFromSettings(settings);\nawait CometChatUIKit.login({ uid: UID });   \u002F\u002F or ({ authToken }) in production\n```\n\nNote the shape: presence moves **into** `chatSDK.presenceSubscription.type` — it is not a\ntop-level field and not a builder call.\n\n⚠️ **Two shapes that differ from React and will not compile if ported:**\n- settings is a **plain object** — there is no `UIKitSettingsBuilder` export in RN\n- `login` takes an **object**: `login({ uid })`, not `login(uid)`\n\nUse an existing UID from your dashboard (the sample apps seed `cometchat-uid-1`). Never invent one.\n\n## The provider chain (BAKED — order is load-bearing)\n\nOutermost first. Verified against the integration + recipe pages:\n\n```tsx\n\u003CGestureHandlerRootView style={{ flex: 1 }}>\n  \u003CSafeAreaProvider>\n    \u003CCometChatI18nProvider>\n      \u003CSafeAreaView style={{ flex: 1 }}>\n        \u003CCometChatThemeProvider>\n          {\u002F* screens *\u002F}\n        \u003C\u002FCometChatThemeProvider>\n      \u003C\u002FSafeAreaView>\n    \u003C\u002FCometChatI18nProvider>\n  \u003C\u002FSafeAreaProvider>\n\u003C\u002FGestureHandlerRootView>\n```\n\n**`GestureHandlerRootView` is outermost and must carry `flex: 1`.** Omit it and swipe \u002F long-press\nsilently do nothing — no error, no warning. It is the single most common \"the UI renders but nothing\nresponds\" cause on RN.\n\n## Sizing — flex, never viewport units\n\nThere is no `100dvh` and no CSS. The rule: **every ancestor of a kit component is `flex: 1`**, and a\nscrolling column also needs `minHeight: 0`. A fixed pixel height breaks when the soft keyboard opens.\nThe composer must remain visible with the keyboard up — verify on a device, not only a simulator.\n\n## Component \u002F API map (BAKED closed list — from `catalogs\u002Frn-v5.json`)\n\n| Need | Component |\n|---|---|\n| conversation list | `CometChatConversations` |\n| message pane | `CometChatMessageHeader` · `CometChatMessageList` · `CometChatMessageComposer` |\n| compact composer | `CometChatCompactMessageComposer` |\n| threads | `CometChatThreadHeader` |\n| search | `CometChatSearch` |\n| users \u002F groups \u002F members | `CometChatUsers` · `CometChatGroups` · `CometChatGroupMembers` |\n| calls | `CometChatCallButtons` · `CometChatIncomingCall` · `CometChatOutgoingCall` · `CometChatOngoingCall` · `CometChatCallLogs` |\n| theming \u002F i18n | `CometChatThemeProvider` + `useTheme()` · `CometChatI18nProvider` |\n| extension chain | `ChatConfigurator` + `DataSourceDecorator` |\n\nAnything not in `catalogs\u002Frn-v5.json` **does not exist** — do not emit it. Notably absent in v5:\n`CometChatErrorBoundary`, `CometChatDetails`, `CometChatAddMembers`, `CometChatBannedMembers`,\n`CometChatTransferOwnership`, and every `*WithMessages` composite. See `references\u002Fdocs-map.md`\nfor the SDK-fallback path for each.\n\n## Callback names — RN uses `Press`, not `Click`\n\n| Component | Wire these |\n|---|---|\n| `CometChatConversations` | `onItemPress` · `onSearchBarClicked` · `onError` |\n| `CometChatMessageList` | `onThreadRepliesPress` · `onError` |\n| `CometChatMessageHeader` | `showBackButton` (default `false`) + `onBack` · `onError` |\n| `CometChatSearch` | `onBack` · `onConversationClicked` · `onMessageClicked` |\n\nReact's `onItemClick` \u002F `onThreadRepliesClick` do not exist here.\n\n> ⚠️ **On `CometChatGroupMembers`, `onError` takes NO argument** in kits up to **5.5.0** —\n> `onError?: () => void`, unlike every other list. Type the handler with a parameter there and it fails\n> with TS2322. Write `onError={() => ...}` and show the failure with the `ErrorView` slot, which needs no\n> error object. Fixed in the kit (uikit-react-native#1452); once that ships, the parameter is available\n> and this note goes away.\n\n## Golden path — the production-ready core surface\n\nThe default for an unscoped \"add chat\". **One screen per route on a stack navigator with a real back\nbutton** — never two panes side by side, and never a web-style side panel.\n\n```tsx\n\u002F\u002F ChatScreen.tsx — the message pane\nimport {\n  CometChatMessageHeader, CometChatMessageList, CometChatMessageComposer,\n} from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\nimport { View } from \"react-native\";\n\nexport const ChatScreen = ({ user, group, onBack }: {\n  user?: CometChat.User; group?: CometChat.Group; onBack: () => void;\n}) => (\n  \u003CView style={{ flex: 1 }}>\n    {\u002F* showBackButton defaults to FALSE on RN — without it onBack never fires *\u002F}\n    \u003CCometChatMessageHeader user={user} group={group} showBackButton onBack={onBack} \u002F>\n    \u003CCometChatMessageList user={user} group={group} \u002F>\n    \u003CCometChatMessageComposer user={user} group={group} \u002F>\n  \u003C\u002FView>\n);\n```\n\n```tsx\n\u002F\u002F ConversationsScreen.tsx — the list, wired to open the pane\nimport { CometChatConversations, CometChatUiKitConstants } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\n\nexport const ConversationsScreen = ({ onOpen }: {\n  onOpen: (user?: CometChat.User, group?: CometChat.Group) => void;\n}) => (\n  \u003CCometChatConversations\n    onItemPress={(conversation: CometChat.Conversation) => {\n      const isUser =\n        conversation.getConversationType() ===\n        CometChatUiKitConstants.ConversationTypeConstants.user;\n      isUser\n        ? onOpen(conversation.getConversationWith() as CometChat.User, undefined)\n        : onOpen(undefined, conversation.getConversationWith() as CometChat.Group);\n    }}\n  \u002F>\n);\n```\n\n### The core surface is FOUR things, not two\n\n`contracts.rn-v5.json` → `core-chat-surface` mandates all four by default, and the reviewer's G1\ngate fails an emit that ships fewer. A list ↔ message pane is **half the surface**:\n\n| Capability | Component | Wire |\n|---|---|---|\n| conversations | `CometChatConversations` | `onItemPress` |\n| messages | `CometChatMessageHeader` + `List` + `Composer` | `showBackButton` + `onBack` |\n| **threaded replies** | `CometChatThreadHeader` | `onThreadRepliesPress` → push a thread screen |\n| **search** | `CometChatSearch` | `showSearchBar={true}` **+** `onSearchBarClicked` → push a search screen |\n\nOn RN both are **pushed screens**, not side panels. Search is opt-out only, and must cover the\nglobal (list) case *and* the in-chat case scoped to the open conversation.\n\n```tsx\n\u002F\u002F message pane — thread entry point\n\u003CCometChatMessageList\n  user={user}\n  group={group}\n  onThreadRepliesPress={(message) => openThread(message)}\n\u002F>\n\n\u002F\u002F conversation list — search entry point.\n\u002F\u002F showSearchBar defaults to FALSE on RN (it is true on React), so the callback alone\n\u002F\u002F silently ships a surface with no search. Both props, always.\n\u003CCometChatConversations\n  onItemPress={open}\n  showSearchBar={true}\n  onSearchBarClicked={() => openSearch()}\n\u002F>\n```\n\nThe callbacks above are only the **entry points**. `openThread` and `openSearch` push screens, and\nthose screens are where the two mandated components actually render — emit both, or the surface\nhas tap targets that lead nowhere:\n\n```tsx\n\u002F\u002F ThreadScreen — what openThread(message) pushes to.\n\u002F\u002F parentMessageId is typed `string` on the list and `string | number` on the composer,\n\u002F\u002F so the list needs .toString().\nfunction ThreadScreen({ route, navigation }) {\n  const { parentMessage, user, group } = route.params;\n  return (\n    \u003CView style={{ flex: 1, minHeight: 0 }}>\n      \u003CCometChatThreadHeader parentMessage={parentMessage} \u002F>\n      \u003CCometChatMessageList\n        user={user}\n        group={group}\n        parentMessageId={parentMessage.getId().toString()}\n      \u002F>\n      \u003CCometChatMessageComposer\n        user={user}\n        group={group}\n        parentMessageId={parentMessage.getId()}\n      \u002F>\n    \u003C\u002FView>\n  );\n}\n```\n\n```tsx\n\u002F\u002F SearchScreen — what openSearch() pushes to.\n\u002F\u002F Omit uid\u002Fguid for the GLOBAL case (from the conversation list); pass one to scope the\n\u002F\u002F search to the open conversation. Both cases are mandated — one screen serves both.\nfunction SearchScreen({ route, navigation }) {\n  const { user, group } = route.params ?? {};\n  return (\n    \u003CCometChatSearch\n      onBack={() => navigation.goBack()}\n      uid={user?.getUid()}\n      guid={group?.getGuid()}\n      onConversationClicked={(conversation) => navigation.navigate(\"Messages\", { conversation })}\n      onMessageClicked={(message) => navigation.navigate(\"Messages\", { message })}\n      onError={(e) => console.error(e)}\n    \u002F>\n  );\n}\n```\n\n> **Search:** `CometChatSearch` is documented at `{DOCS_BASE}\u002Fui-kit\u002Freact-native\u002Fsearch` (fetch it\n> via `references\u002Fdocs-map.md`); wire `onConversationClicked` \u002F `onMessageClicked` and its `onBack`.\n> (Formerly tracked as gap RN-G1 — the page has since been published.)\n\n**Every affordance that is visible by default is wired or hidden.** A tap target that does nothing is\na defect, and so is an opened surface with no way back — if you open search or a thread, wire its\n`onBack` in the same edit.\n\n## Deep references (load only when the task needs them)\n- `references\u002Fdocs-map.md` — intent → the exact docs page; the SDK-fallback table; the React→RN name table. **Read before porting any React snippet.**\n- `references\u002Fcomponent-props.md` — baked props + **PascalCase view slots** per drop-in, and the defaults that differ from React (`showSearchBar` is `false` here). **Read before placing custom UI** — it goes in a slot, never as a sibling.\n- `references\u002Fanti-patterns.md` — the 13 failures that actually break an RN integration, each with why its error names the wrong thing.\n- `references\u002Flifecycle.md` — `initFromSettings` → login → render, and the promise-cached boot guard (a boolean flag does not work).\n- `references\u002Flayout.md` — the four sizing invariants the `core-chat-surface` contract gates on.\n- `references\u002Fdependencies.md` — the exact peer set + the native config that is not optional (Podfile modular headers, gesture-handler import order).\n- `references\u002Fsetup-credentials.md` — dev vs production auth, and why nothing in a mobile bundle is secret.\n\n## Common pitfalls\n1. **Missing `GestureHandlerRootView`** — gestures silently dead. Outermost, `flex: 1`.\n2. **Rendering before `login()` resolves** — blank screen, no error.\n3. **Porting React code** — `UIKitSettingsBuilder`, `login(uid)`, `onItemClick`, CSS, `document.*`: none exist here.\n4. **Fixed heights** — breaks on keyboard open. Use `flex: 1` + `minHeight: 0`.\n5. **Shipping the Auth Key** — dev only; production mints an auth token server-side.\n\n## Verify it works\n- Every emitted symbol appears in `catalogs\u002Frn-v5.json`.\n- Code compiles against the pinned kit: `npm run verify:fences:rn-v5`.\n- Oracles agree with the kit and docs: `npm run verify:sync:rn-v5`.\n- **`tsc --noEmit` in the APP is not clean, and that is not the app's bug.** The kit ships raw\n  `src\u002F*.tsx` as its `main`\u002F`module` with no built declarations, so TypeScript follows the import and\n  typechecks the kit itself (`NodeJS` namespace, implicit `any`, `isolatedModules` re-exports,\n  `User | null`, and on RN 0.87 a `RefObject\u003CTextInputType>` mismatch). Gate on the **Metro bundle**\n  instead — `npx react-native bundle --platform ios|android --dev false --entry-file index.js\n  --bundle-output \u002Fdev\u002Fnull` — and if you want a typecheck, filter the kit's own files out of the\n  output. Never \"fix\" node_modules, and never report the app as failing typecheck because of them.\n- **Getting the app to actually RUN on a shared machine.** React Native asks for Metro on port 8081\n  and takes whatever answers: another project's packager serves a foreign bundle, and the app dies\n  with `Invariant Violation: TurboModuleRegistry.getEnforcing('PlatformConstants')` — a version\n  mismatch that reads like a missing native module. iOS: point the app at your packager with\n  `xcrun simctl spawn \u003Cudid> defaults write \u003Cbundle-id> RCT_jsLocation \"localhost:\u003Cport>\"`\n  (`RCT_METRO_PORT` does not change the runtime URL). Android: `adb reverse tcp:8081 tcp:\u003Cport>`, and\n  when that silently does nothing — it does on some emulators — embed the bundle instead:\n  `npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output\n  android\u002Fapp\u002Fsrc\u002Fmain\u002Fassets\u002Findex.android.bundle --assets-dest android\u002Fapp\u002Fsrc\u002Fmain\u002Fres`, then\n  `run-android`. Remove that file before going back to Fast Refresh.\n- On a device: chat fills the screen, the composer survives the keyboard, back works, gestures respond.\n\n## Explain what you built (REQUIRED close)\nTell the user briefly: **(1) what I wired** (3–5 bullets, NAME the files); **(2) decisions & why**, flagging dev-only AS dev-only (the **Auth Key** is dev-only → server-minted auth token for production; the `\u003Cuid>` you used; Expo vs bare RN path); **(3) what I did NOT touch** (additive — navigation\u002Fauth\u002Fstyles intact). Then **offer these THREE options as a selectable choice and WAIT — do not auto-continue:**\n- **(1) Add another feature** — check what's already wired; ASK which Dashboard extensions are enabled; suggest 3–4 gaps (**calls · push · AI smart replies · polls · stickers · translation · notification feed**). Never suggest reactions or mentions — they are ON by default in v5. → `cometchat-react-native-features` \u002F `cometchat-react-native-calls` \u002F `cometchat-react-native-push`.\n- **(2) Customize theming** — ask for brand color \u002F light-dark → `cometchat-react-native-customization`.\n- **(3) Test it manually** — hand it back so they run it on a device.\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json` (216 public symbols) +\n> `features.rn-v5.json`. Official docs: \u003Chttps:\u002F\u002Fwww.cometchat.com\u002Fdocs\u002Fui-kit\u002Freact-native\u002Foverview> ·\n> scoped index `...\u002Fui-kit\u002Freact-native\u002Fllms-react-native-v5.md`. Verify every symbol against the catalog;\n> fetch signatures from docs (`references\u002Fdocs-map.md`); never trust memory.\n>\n> ⚠️ **React Native is NOT React.** Different package, different API, native views instead of DOM.\n> A React UI Kit snippet will not compile here. `references\u002Fdocs-map.md` ends with the verified\n> React → React Native name table — read it before porting anything.\n\n## Use this skill when\n- \"add chat to my React Native app\" · \"integrate CometChat in Expo\" · \"RN chat UI\"\n- any React Native CometChat task — it is the assumed base for every other `cometchat-react-native-*` skill\n\n## Prerequisites & install\n\n**One package per platform.** Never mix `@cometchat\u002Fchat-uikit-react` (web) into an RN app.\n\n```bash\nnpm install @cometchat\u002Fchat-uikit-react-native@5 @cometchat\u002Fchat-sdk-react-native@4\n```\n\nThen the **native peer deps — required, not optional.** Verified against `5.4.0` + the integration pages:\n\n```bash\nnpm install @react-native-clipboard\u002Fclipboard \\\n  react-native-gesture-handler react-native-svg react-native-video react-native-localize \\\n  react-native-safe-area-context @react-native-async-storage\u002Fasync-storage@^2.1.2 dayjs\n# Expo also needs: punycode\n```\n\n`cd ios && pod install` for bare RN. **A missing native module fails at MOUNT, not at build** — the\nerror names a NativeModule, not CometChat, so it reads as unrelated.\n\n⚠️ **React Native >= 0.87:** RN removed `InteractionManager` from core and the kit (through 5.5.0)\nstill calls it in the composer's iOS send path, so **sending a message throws on iOS** — it builds,\ntypechecks and bundles clean. Fix and shim: `cometchat-react-native-troubleshooting` -> *Sending a\nmessage throws on iOS*.\n\n\n## Setup & credentials (essentials — full detail: `references\u002Fsetup-credentials.md`)\n1. **Detect** the project: Expo (`app.json`\u002F`app.config.js`) or bare RN (`metro.config.js`). Reuse an existing `.cometchat\u002Fconfig.json` or env if present — skip re-setup.\n2. **version_conflict — STOP** if `@cometchat\u002Fchat-uikit-react-native` is already in `package.json` at a non-v5 major; reconcile first, never mix majors (`RULES.md`).\n3. **Credentials — OFFER the dashboard fetch FIRST** (never silently \"paste it yourself\" — AUDIT-039). 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 values; **(b) manual paste** from Dashboard → Credentials (dev-only Auth Key). **Then the SKILL writes the env (§4)** — the MCP only returns the values; env-writing and codegen are the SKILL's job. Full flow: `references\u002Fsetup-credentials.md`.\n4. **Write env**: bare RN → `.env` (read via `react-native-config`); Expo → `.env` (read via `Constants.expoConfig.extra` or `process.env`). Gitignore it; never echo the Auth Key. Prod → server-minted auth token, not the Auth Key. **Nothing in a mobile bundle is secret** (IPA\u002FAPK are readable) — see `references\u002Fsetup-credentials.md`.\n5. **Authorize** = `initFromSettings` then `login` both resolve; auth error is almost always the wrong Region.\n\n## Integration ordering (BAKED — invariant)\n\n**`init()` must resolve before `login()`. `login()` must resolve before you render any component.**\nBreaking it gives a blank screen, not an error.\n\nUse **`initFromSettings`**, not the classic `init` — it persists `integrationSource=\"ai-agent\"`\nso CometChat can attribute the integration. The classic init does not (AUDIT-084), and a machine\ngate enforces this.\n\n```tsx\nimport { CometChatUIKit } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\n\nconst settings: CometChat.CometChatSettings = {\n  appId: APP_ID,\n  region: REGION,\n  credentials: { authKey: AUTH_KEY }, \u002F\u002F dev only — production mints an auth token server-side\n  chatSDK: {\n    presenceSubscription: { type: \"ALL_USERS\" },\n    autoEstablishSocketConnection: true,\n  },\n};\n\nawait CometChatUIKit.initFromSettings(settings);\nawait CometChatUIKit.login({ uid: UID });   \u002F\u002F or ({ authToken }) in production\n```\n\nNote the shape: presence moves **into** `chatSDK.presenceSubscription.type` — it is not a\ntop-level field and not a builder call.\n\n⚠️ **Two shapes that differ from React and will not compile if ported:**\n- settings is a **plain object** — there is no `UIKitSettingsBuilder` export in RN\n- `login` takes an **object**: `login({ uid })`, not `login(uid)`\n\nUse an existing UID from your dashboard (the sample apps seed `cometchat-uid-1`). Never invent one.\n\n## The provider chain (BAKED — order is load-bearing)\n\nOutermost first. Verified against the integration + recipe pages:\n\n```tsx\n\u003CGestureHandlerRootView style={{ flex: 1 }}>\n  \u003CSafeAreaProvider>\n    \u003CCometChatI18nProvider>\n      \u003CSafeAreaView style={{ flex: 1 }}>\n        \u003CCometChatThemeProvider>\n          {\u002F* screens *\u002F}\n        \u003C\u002FCometChatThemeProvider>\n      \u003C\u002FSafeAreaView>\n    \u003C\u002FCometChatI18nProvider>\n  \u003C\u002FSafeAreaProvider>\n\u003C\u002FGestureHandlerRootView>\n```\n\n**`GestureHandlerRootView` is outermost and must carry `flex: 1`.** Omit it and swipe \u002F long-press\nsilently do nothing — no error, no warning. It is the single most common \"the UI renders but nothing\nresponds\" cause on RN.\n\n## Sizing — flex, never viewport units\n\nThere is no `100dvh` and no CSS. The rule: **every ancestor of a kit component is `flex: 1`**, and a\nscrolling column also needs `minHeight: 0`. A fixed pixel height breaks when the soft keyboard opens.\nThe composer must remain visible with the keyboard up — verify on a device, not only a simulator.\n\n## Component \u002F API map (BAKED closed list — from `catalogs\u002Frn-v5.json`)\n\n| Need | Component |\n|---|---|\n| conversation list | `CometChatConversations` |\n| message pane | `CometChatMessageHeader` · `CometChatMessageList` · `CometChatMessageComposer` |\n| compact composer | `CometChatCompactMessageComposer` |\n| threads | `CometChatThreadHeader` |\n| search | `CometChatSearch` |\n| users \u002F groups \u002F members | `CometChatUsers` · `CometChatGroups` · `CometChatGroupMembers` |\n| calls | `CometChatCallButtons` · `CometChatIncomingCall` · `CometChatOutgoingCall` · `CometChatOngoingCall` · `CometChatCallLogs` |\n| theming \u002F i18n | `CometChatThemeProvider` + `useTheme()` · `CometChatI18nProvider` |\n| extension chain | `ChatConfigurator` + `DataSourceDecorator` |\n\nAnything not in `catalogs\u002Frn-v5.json` **does not exist** — do not emit it. Notably absent in v5:\n`CometChatErrorBoundary`, `CometChatDetails`, `CometChatAddMembers`, `CometChatBannedMembers`,\n`CometChatTransferOwnership`, and every `*WithMessages` composite. See `references\u002Fdocs-map.md`\nfor the SDK-fallback path for each.\n\n## Callback names — RN uses `Press`, not `Click`\n\n| Component | Wire these |\n|---|---|\n| `CometChatConversations` | `onItemPress` · `onSearchBarClicked` · `onError` |\n| `CometChatMessageList` | `onThreadRepliesPress` · `onError` |\n| `CometChatMessageHeader` | `showBackButton` (default `false`) + `onBack` · `onError` |\n| `CometChatSearch` | `onBack` · `onConversationClicked` · `onMessageClicked` |\n\nReact's `onItemClick` \u002F `onThreadRepliesClick` do not exist here.\n\n> ⚠️ **On `CometChatGroupMembers`, `onError` takes NO argument** in kits up to **5.5.0** —\n> `onError?: () => void`, unlike every other list. Type the handler with a parameter there and it fails\n> with TS2322. Write `onError={() => ...}` and show the failure with the `ErrorView` slot, which needs no\n> error object. Fixed in the kit (uikit-react-native#1452); once that ships, the parameter is available\n> and this note goes away.\n\n## Golden path — the production-ready core surface\n\nThe default for an unscoped \"add chat\". **One screen per route on a stack navigator with a real back\nbutton** — never two panes side by side, and never a web-style side panel.\n\n```tsx\n\u002F\u002F ChatScreen.tsx — the message pane\nimport {\n  CometChatMessageHeader, CometChatMessageList, CometChatMessageComposer,\n} from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\nimport { View } from \"react-native\";\n\nexport const ChatScreen = ({ user, group, onBack }: {\n  user?: CometChat.User; group?: CometChat.Group; onBack: () => void;\n}) => (\n  \u003CView style={{ flex: 1 }}>\n    {\u002F* showBackButton defaults to FALSE on RN — without it onBack never fires *\u002F}\n    \u003CCometChatMessageHeader user={user} group={group} showBackButton onBack={onBack} \u002F>\n    \u003CCometChatMessageList user={user} group={group} \u002F>\n    \u003CCometChatMessageComposer user={user} group={group} \u002F>\n  \u003C\u002FView>\n);\n```\n\n```tsx\n\u002F\u002F ConversationsScreen.tsx — the list, wired to open the pane\nimport { CometChatConversations, CometChatUiKitConstants } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { CometChat } from \"@cometchat\u002Fchat-sdk-react-native\";\n\nexport const ConversationsScreen = ({ onOpen }: {\n  onOpen: (user?: CometChat.User, group?: CometChat.Group) => void;\n}) => (\n  \u003CCometChatConversations\n    onItemPress={(conversation: CometChat.Conversation) => {\n      const isUser =\n        conversation.getConversationType() ===\n        CometChatUiKitConstants.ConversationTypeConstants.user;\n      isUser\n        ? onOpen(conversation.getConversationWith() as CometChat.User, undefined)\n        : onOpen(undefined, conversation.getConversationWith() as CometChat.Group);\n    }}\n  \u002F>\n);\n```\n\n### The core surface is FOUR things, not two\n\n`contracts.rn-v5.json` → `core-chat-surface` mandates all four by default, and the reviewer's G1\ngate fails an emit that ships fewer. A list ↔ message pane is **half the surface**:\n\n| Capability | Component | Wire |\n|---|---|---|\n| conversations | `CometChatConversations` | `onItemPress` |\n| messages | `CometChatMessageHeader` + `List` + `Composer` | `showBackButton` + `onBack` |\n| **threaded replies** | `CometChatThreadHeader` | `onThreadRepliesPress` → push a thread screen |\n| **search** | `CometChatSearch` | `showSearchBar={true}` **+** `onSearchBarClicked` → push a search screen |\n\nOn RN both are **pushed screens**, not side panels. Search is opt-out only, and must cover the\nglobal (list) case *and* the in-chat case scoped to the open conversation.\n\n```tsx\n\u002F\u002F message pane — thread entry point\n\u003CCometChatMessageList\n  user={user}\n  group={group}\n  onThreadRepliesPress={(message) => openThread(message)}\n\u002F>\n\n\u002F\u002F conversation list — search entry point.\n\u002F\u002F showSearchBar defaults to FALSE on RN (it is true on React), so the callback alone\n\u002F\u002F silently ships a surface with no search. Both props, always.\n\u003CCometChatConversations\n  onItemPress={open}\n  showSearchBar={true}\n  onSearchBarClicked={() => openSearch()}\n\u002F>\n```\n\nThe callbacks above are only the **entry points**. `openThread` and `openSearch` push screens, and\nthose screens are where the two mandated components actually render — emit both, or the surface\nhas tap targets that lead nowhere:\n\n```tsx\n\u002F\u002F ThreadScreen — what openThread(message) pushes to.\n\u002F\u002F parentMessageId is typed `string` on the list and `string | number` on the composer,\n\u002F\u002F so the list needs .toString().\nfunction ThreadScreen({ route, navigation }) {\n  const { parentMessage, user, group } = route.params;\n  return (\n    \u003CView style={{ flex: 1, minHeight: 0 }}>\n      \u003CCometChatThreadHeader parentMessage={parentMessage} \u002F>\n      \u003CCometChatMessageList\n        user={user}\n        group={group}\n        parentMessageId={parentMessage.getId().toString()}\n      \u002F>\n      \u003CCometChatMessageComposer\n        user={user}\n        group={group}\n        parentMessageId={parentMessage.getId()}\n      \u002F>\n    \u003C\u002FView>\n  );\n}\n```\n\n```tsx\n\u002F\u002F SearchScreen — what openSearch() pushes to.\n\u002F\u002F Omit uid\u002Fguid for the GLOBAL case (from the conversation list); pass one to scope the\n\u002F\u002F search to the open conversation. Both cases are mandated — one screen serves both.\nfunction SearchScreen({ route, navigation }) {\n  const { user, group } = route.params ?? {};\n  return (\n    \u003CCometChatSearch\n      onBack={() => navigation.goBack()}\n      uid={user?.getUid()}\n      guid={group?.getGuid()}\n      onConversationClicked={(conversation) => navigation.navigate(\"Messages\", { conversation })}\n      onMessageClicked={(message) => navigation.navigate(\"Messages\", { message })}\n      onError={(e) => console.error(e)}\n    \u002F>\n  );\n}\n```\n\n> **Search:** `CometChatSearch` is documented at `{DOCS_BASE}\u002Fui-kit\u002Freact-native\u002Fsearch` (fetch it\n> via `references\u002Fdocs-map.md`); wire `onConversationClicked` \u002F `onMessageClicked` and its `onBack`.\n> (Formerly tracked as gap RN-G1 — the page has since been published.)\n\n**Every affordance that is visible by default is wired or hidden.** A tap target that does nothing is\na defect, and so is an opened surface with no way back — if you open search or a thread, wire its\n`onBack` in the same edit.\n\n## Deep references (load only when the task needs them)\n- `references\u002Fdocs-map.md` — intent → the exact docs page; the SDK-fallback table; the React→RN name table. **Read before porting any React snippet.**\n- `references\u002Fcomponent-props.md` — baked props + **PascalCase view slots** per drop-in, and the defaults that differ from React (`showSearchBar` is `false` here). **Read before placing custom UI** — it goes in a slot, never as a sibling.\n- `references\u002Fanti-patterns.md` — the 13 failures that actually break an RN integration, each with why its error names the wrong thing.\n- `references\u002Flifecycle.md` — `initFromSettings` → login → render, and the promise-cached boot guard (a boolean flag does not work).\n- `references\u002Flayout.md` — the four sizing invariants the `core-chat-surface` contract gates on.\n- `references\u002Fdependencies.md` — the exact peer set + the native config that is not optional (Podfile modular headers, gesture-handler import order).\n- `references\u002Fsetup-credentials.md` — dev vs production auth, and why nothing in a mobile bundle is secret.\n\n## Common pitfalls\n1. **Missing `GestureHandlerRootView`** — gestures silently dead. Outermost, `flex: 1`.\n2. **Rendering before `login()` resolves** — blank screen, no error.\n3. **Porting React code** — `UIKitSettingsBuilder`, `login(uid)`, `onItemClick`, CSS, `document.*`: none exist here.\n4. **Fixed heights** — breaks on keyboard open. Use `flex: 1` + `minHeight: 0`.\n5. **Shipping the Auth Key** — dev only; production mints an auth token server-side.\n\n## Verify it works\n- Every emitted symbol appears in `catalogs\u002Frn-v5.json`.\n- Code compiles against the pinned kit: `npm run verify:fences:rn-v5`.\n- Oracles agree with the kit and docs: `npm run verify:sync:rn-v5`.\n- **`tsc --noEmit` in the APP is not clean, and that is not the app's bug.** The kit ships raw\n  `src\u002F*.tsx` as its `main`\u002F`module` with no built declarations, so TypeScript follows the import and\n  typechecks the kit itself (`NodeJS` namespace, implicit `any`, `isolatedModules` re-exports,\n  `User | null`, and on RN 0.87 a `RefObject\u003CTextInputType>` mismatch). Gate on the **Metro bundle**\n  instead — `npx react-native bundle --platform ios|android --dev false --entry-file index.js\n  --bundle-output \u002Fdev\u002Fnull` — and if you want a typecheck, filter the kit's own files out of the\n  output. Never \"fix\" node_modules, and never report the app as failing typecheck because of them.\n- **Getting the app to actually RUN on a shared machine.** React Native asks for Metro on port 8081\n  and takes whatever answers: another project's packager serves a foreign bundle, and the app dies\n  with `Invariant Violation: TurboModuleRegistry.getEnforcing('PlatformConstants')` — a version\n  mismatch that reads like a missing native module. iOS: point the app at your packager with\n  `xcrun simctl spawn \u003Cudid> defaults write \u003Cbundle-id> RCT_jsLocation \"localhost:\u003Cport>\"`\n  (`RCT_METRO_PORT` does not change the runtime URL). Android: `adb reverse tcp:8081 tcp:\u003Cport>`, and\n  when that silently does nothing — it does on some emulators — embed the bundle instead:\n  `npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output\n  android\u002Fapp\u002Fsrc\u002Fmain\u002Fassets\u002Findex.android.bundle --assets-dest android\u002Fapp\u002Fsrc\u002Fmain\u002Fres`, then\n  `run-android`. Remove that file before going back to Fast Refresh.\n- On a device: chat fills the screen, the composer survives the keyboard, back works, gestures respond.\n\n## Explain what you built (REQUIRED close)\nTell the user briefly: **(1) what I wired** (3–5 bullets, NAME the files); **(2) decisions & why**, flagging dev-only AS dev-only (the **Auth Key** is dev-only → server-minted auth token for production; the `\u003Cuid>` you used; Expo vs bare RN path); **(3) what I did NOT touch** (additive — navigation\u002Fauth\u002Fstyles intact). Then **offer these THREE options as a selectable choice and WAIT — do not auto-continue:**\n- **(1) Add another feature** — check what's already wired; ASK which Dashboard extensions are enabled; suggest 3–4 gaps (**calls · push · AI smart replies · polls · stickers · translation · notification feed**). Never suggest reactions or mentions — they are ON by default in v5. → `cometchat-react-native-features` \u002F `cometchat-react-native-calls` \u002F `cometchat-react-native-push`.\n- **(2) Customize theming** — ask for brand color \u002F light-dark → `cometchat-react-native-customization`.\n- **(3) Test it manually** — hand it back so they run it on a device.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"chat cometchat react-native expo core rules initialization provider native","CometChat","1.0.0","Node.js >=18; React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0; @cometchat\u002Fchat-sdk-react-native ^4.0.28; optional @cometchat\u002Fcalls-sdk-react-native ^5.0.4","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-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-native-core",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-core",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-core","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002FSKILL.md",true,[79,85,89,93,97,101,105],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fanti-patterns.md","REFERENCE","参考文档",3946,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Fanti-patterns.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcomponent-props.md",5929,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Fcomponent-props.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdependencies.md",3531,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Fdependencies.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fdocs-map.md",9305,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Fdocs-map.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Flayout.md",2641,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Flayout.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Flifecycle.md",2283,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Flifecycle.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsetup-credentials.md",3320,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-core\u002Freferences\u002Fsetup-credentials.md",[110,119,127,135,143,151],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":118},"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":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":118},"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":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":118},"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":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":118},"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":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":118},"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":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":118},"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",[],[]]