[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFG7W1DHYQNWNEJB6HB6YG":3,"skill-same:01M6MFG7W1DHYQNWNEJB6HB6YG":88},{"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":26,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6MFG7W1DHYQNWNEJB6HB6YG","cometchat-react-native-customization",null,"Theme, restyle and extend the CometChat React Native UI Kit v5 — theme modes and color tokens, per-component style objects, view slots, and the DataSource decorator chain for custom message types. Triggers: change CometChat colors React Native, dark mode RN chat, custom message bubble RN, brand the RN chat UI, custom message type React Native, restyle the message bubble, change the chat font, add a custom bubble RN.","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-customization\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"react","cometchat","customization","react native","cometchat react native customization","native","types","chain","mode","chat ui","objects","kit","change","component","message","react-native","styling","ui","font","add","extend","2026-11-10 10:12:30",false,"---\nname: cometchat-react-native-customization\ndescription: \"Theme, restyle and extend the CometChat React Native UI Kit v5 — theme modes and color tokens, per-component style objects, view slots, and the DataSource decorator chain for custom message types. Triggers: change CometChat colors React Native, dark mode RN chat, custom message bubble RN, brand the RN chat UI, custom message type React Native, restyle the message bubble, change the chat font, add a custom bubble RN.\"\nlicense: \"MIT\"\ncompatibility: \"React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"chat cometchat react-native customization theming styling datasource decorator\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json`.\n> Docs: `\u002Fui-kit\u002Freact-native\u002Ftheme` · `colors` · `component-styling` · `message-bubble-styling`.\n> Fetch token names and style keys from docs — never invent them.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- \"change the chat colors\" · \"brand the chat UI\" · \"dark mode\" · \"restyle the bubbles\"\n- \"custom message type\" · \"render my own bubble\" · \"add an option to the message menu\"\n\n**Cloning a named app, or mixing kit components with your own UI?** Measure the target's colors, type, spacing and radii into ONE token source, theme the kit from it, and style every custom component from the same tokens so kit and custom parts look like one design; host a kit component in your own dialog\u002Fpanel when only its placement differs. Flow: `cometchat-onboarding` → `references\u002Fclone-mode.md` (Design sync, build levels L0–L6).\n\n**Avatar + sender name on every message (own and others', 1:1 and group):** the kit default shows them only on others' messages in groups. Fix it yourself whenever the target shows them: `references\u002Fmessage-chrome.md` (`alignment=\"leftAligned\"`, then per-message `LeadingView` \u002F `HeaderView` via a decorator).\n\n## Prerequisites & install\nNone beyond `core`. Theming needs `CometChatThemeProvider` already in the chain (see `core`).\n\n## Customization mechanism — three layers, cheapest first\n\n**There is no CSS.** No stylesheets, no `className`, no `--cometchat-*` variables. If you are\nholding a React snippet with CSS custom properties, it does not apply here.\n\n### Layer 1 — theme mode + color tokens (whole app)\nThe provider takes a `theme` prop shaped `{ mode, light, dark }`. `mode` is `\"light\"` · `\"dark\"` ·\n`\"auto\"` — **`\"auto\"` is what makes the kit follow the device (OS) light\u002Fdark setting** (it reads\n`useColorScheme()`); the provider default is already `\"auto\"`.\n\n```tsx\n\u002F\u002F Fixed dark for the whole app.\n\u003CCometChatThemeProvider theme={{ mode: \"dark\" }}>{\u002F* ... *\u002F}\u003C\u002FCometChatThemeProvider>\n```\n\n```tsx\n\u002F\u002F Follow the OS, branded in BOTH schemes. mode:\"auto\" is the switch;\n\u002F\u002F set BOTH light and dark or dark falls back to defaults.\n\u003CCometChatThemeProvider\n  theme={{\n    mode: \"auto\",\n    light: { color: { primary: \"#F76808\" } },\n    dark: { color: { primary: \"#F8935B\" } },\n  }}\n>\n  {\u002F* ... *\u002F}\n\u003C\u002FCometChatThemeProvider>\n```\n\n`primary` drives buttons, outgoing bubbles and active states — it is usually the only token a brand\nchange needs. Other common tokens: `textPrimary`, `background1`, `neutral50`, `extendedPrimary500`.\n**Fetch the full list** from `\u002Fui-kit\u002Freact-native\u002Fcolors.md` rather than guessing a token name.\n\nTo follow the OS, use **`mode: \"auto\"`** and set both `light` and `dark`. Without the provider,\nsystem theme changes are not reflected at all.\n\n### Layer 2 — per-component style objects\nEvery component takes a `style` prop holding named sub-style objects — plain RN style objects,\nnot CSS:\n\n```tsx\n\u003CCometChatConversations style={{ containerStyle: { backgroundColor: \"#F7F7F7\" } }} \u002F>\n```\n\nThe same style keys can be set globally through the theme instead, which is preferable when the\nchange should apply everywhere:\n\n```tsx\n\u003CCometChatThemeProvider theme={{ light: { conversationStyles: { \u002F* ... *\u002F } } }}>\n```\n\nStyle-key names differ per component. Fetch them from that component's page\n(`\u002Fui-kit\u002Freact-native\u002Fcomponent-styling.md` and the component's own page) — do not pattern-match\nfrom another component.\n\n### Layer 3 — read the active theme in your own views\n`useTheme()` returns the **resolved** theme (already light-or-dark per `mode`), so custom views match\nthe kit without re-deriving the palette:\n\n```tsx\nimport { useTheme } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { Text } from \"react-native\";\n\nconst Label = () => {\n  const theme = useTheme();\n  return \u003CText style={{ color: theme.color.textPrimary }}>Chats\u003C\u002FText>;\n};\n```\n\n## Custom message types — the DataSource decorator chain\n\n⚠️ **RN does NOT have the React plugin API.** `CometChatMessagePlugin` and `CometChatPluginRegistry`\ndo not exist in this kit; emitting them will not compile. RN uses a decorator chain.\n\nExtend `DataSourceDecorator`, override what you need, and register it with `ChatConfigurator.enable`:\n\n```tsx\nimport {\n  ChatConfigurator, DataSourceDecorator, CometChatMessageTemplate,\n} from \"@cometchat\u002Fchat-uikit-react-native\";\n\nconst ORDER_TYPE = \"order\";\n\nclass OrderDataSource extends DataSourceDecorator {\n  \u002F\u002F 0. IDENTITY — REQUIRED. The base DataSourceDecorator.getId() THROWS\n  \u002F\u002F (\"Method not implemented.\") and ChatConfigurator.enable() calls getId() to\n  \u002F\u002F dedupe the registry — so a subclass without this override crashes at\n  \u002F\u002F ChatConfigurator.enable(...), NOT at render. Return a stable, unique id.\n  getId(): string {\n    return \"order_message_datasource\";\n  }\n\n  \u002F\u002F 1. RENDER — how the bubble draws.\n  getAllMessageTemplates(theme?: any, params?: any): CometChatMessageTemplate[] {\n    const templates = super.getAllMessageTemplates(theme, params);\n    \u002F\u002F append or replace a template here\n    return templates;\n  }\n\n  \u002F\u002F 2. FETCH — WITHOUT THESE TWO THE MESSAGE IS NEVER RETRIEVED.\n  \u002F\u002F CometChatMessageList builds its request from them:\n  \u002F\u002F   requestBuilder.setTypes(ChatConfigurator.dataSource.getAllMessageTypes())\n  \u002F\u002F   requestBuilder.setCategories(ChatConfigurator.dataSource.getAllMessageCategories())\n  \u002F\u002F A type absent from those filters is excluded server-side. The bubble appears\n  \u002F\u002F optimistically when sent, then vanishes on reload — with no error anywhere.\n  getAllMessageTypes(): string[] {\n    return [...super.getAllMessageTypes(), ORDER_TYPE];\n  }\n\n  getAllMessageCategories(): string[] {\n    const categories = super.getAllMessageCategories();\n    return categories.includes(CometChat.CATEGORY_CUSTOM)\n      ? categories\n      : [...categories, CometChat.CATEGORY_CUSTOM];\n  }\n}\n\n\u002F\u002F AFTER login(), not merely after init(). CometChatUIKit.login() calls enableExtensions(),\n\u002F\u002F whose first statement is ChatConfigurator.init() — \"re-initialize data source\". Anything\n\u002F\u002F registered earlier is DISCARDED, so a decorator wired at module scope, or straight after\n\u002F\u002F init(), silently disappears.\nawait CometChatUIKit.login({ uid: UID });\nChatConfigurator.enable((source) => new OrderDataSource(source));\n```\n\n**`getId()` is REQUIRED on every `DataSourceDecorator` subclass.** It is the ONE base method that\ndoes not delegate to the wrapped source — the base throws `Error(\"Method not implemented.\")`, and\n`ChatConfigurator.enable()` calls `getId()` to dedupe the registry. Omit it and registration crashes\nat `ChatConfigurator.enable(...)` with `Method not implemented.` — NOT at render, so it reads as\nunrelated. Every built-in decorator (Polls, Stickers, Translation, LinkPreview, Collaborative*)\noverrides it; yours must too, returning a stable unique string.\n\nA custom message type is **two halves, and only one of them is obvious.** Render is\n`getAllMessageTemplates` \u002F `getMessageTemplate`. Fetch is `getAllMessageTypes` \u002F\n`getAllMessageCategories`. Ship the render half alone and everything looks right until the first\nreload, when every message of your type is gone — no error, no warning.\n\n`DataSourceDecorator` exposes ~50 overridable methods; the ones you usually want are **`getId`**\n(mandatory — see above), `getAllMessageTemplates`, `getMessageTemplate`, **`getAllMessageTypes`**,\n**`getAllMessageCategories`**, `getMessageOptions` (the long-press menu) and\n`getAuxiliaryOptions` (composer actions). Always call `super.\u003Cmethod>(...)` and modify the result —\nreplacing it wholesale drops every built-in message type.\n\n> **DOCS GAP (RN-G10):** `DataSourceDecorator` \u002F `MessageDataSource` \u002F `ExtensionsDataSource` and\n> `ChatConfigurator.enable` are **not documented** on any RN page — the docs show only mutating\n> existing templates via `getAllMessageTemplates()`. Built from the kit source; flag this to the\n> developer rather than presenting it as documented.\n>\n> **Partially closed (2026-08-20).** `ui-kit\u002Freact-native\u002Fmessage-list` now documents the\n> half that actually breaks builds: a custom type must be registered for **fetch**\n> (`getAllMessageTypes` \u002F `getAllMessageCategories`), not only for render, and the decorator must\n> be registered **after `login()`** because `enableExtensions()` re-runs `ChatConfigurator.init()`.\n> Still missing: a dedicated RN custom-message-types page covering `DataSourceDecorator` \u002F\n> `MessageDataSource` \u002F `ExtensionsDataSource` end to end. Owner: docs.\n\n## Customizing an existing bubble without a decorator\nTo restyle rather than replace, prefer the theme's bubble style keys —\n`textBubbleStyles`, `imageBubbleStyles`, `fileBubbleStyles`, `pollBubbleStyles` and siblings.\nFetch exact keys from `\u002Fui-kit\u002Freact-native\u002Fmessage-bubble-styling.md`.\n\n## Common pitfalls\n1. **Reaching for CSS** — no stylesheets, no `className`, no `--cometchat-*`. Theme object + RN styles.\n2. **Emitting the React plugin API** — does not exist; use `ChatConfigurator` + `DataSourceDecorator`.\n3. **Omitting `getId()` on a decorator** — the base throws; `ChatConfigurator.enable()` calls it → crash at registration with `Method not implemented.`\n4. **Not calling `super`** in a decorator override — silently drops all built-in templates.\n5. **Setting only `light`** when the app follows the OS — dark mode then falls back to defaults.\n6. **Guessing token or style-key names** — fetch them; a wrong key fails silently rather than erroring.\n\n## Verify it works\n- Every symbol appears in `catalogs\u002Frn-v5.json`.\n- `npm run verify:fences:rn-v5` compiles the examples against the pinned kit.\n- On device: toggle OS dark mode and confirm the surface follows; confirm a custom template renders\n  and built-in types still render alongside it.\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react-native@5` + catalog `rn-v5.json`.\n> Docs: `\u002Fui-kit\u002Freact-native\u002Ftheme` · `colors` · `component-styling` · `message-bubble-styling`.\n> Fetch token names and style keys from docs — never invent them.\n\n## Companion skills (read first)\n- `cometchat-react-native-core` — install, provider chain, init→login→render. Assumed, not repeated here.\n\n## Use this skill when\n- \"change the chat colors\" · \"brand the chat UI\" · \"dark mode\" · \"restyle the bubbles\"\n- \"custom message type\" · \"render my own bubble\" · \"add an option to the message menu\"\n\n**Cloning a named app, or mixing kit components with your own UI?** Measure the target's colors, type, spacing and radii into ONE token source, theme the kit from it, and style every custom component from the same tokens so kit and custom parts look like one design; host a kit component in your own dialog\u002Fpanel when only its placement differs. Flow: `cometchat-onboarding` → `references\u002Fclone-mode.md` (Design sync, build levels L0–L6).\n\n**Avatar + sender name on every message (own and others', 1:1 and group):** the kit default shows them only on others' messages in groups. Fix it yourself whenever the target shows them: `references\u002Fmessage-chrome.md` (`alignment=\"leftAligned\"`, then per-message `LeadingView` \u002F `HeaderView` via a decorator).\n\n## Prerequisites & install\nNone beyond `core`. Theming needs `CometChatThemeProvider` already in the chain (see `core`).\n\n## Customization mechanism — three layers, cheapest first\n\n**There is no CSS.** No stylesheets, no `className`, no `--cometchat-*` variables. If you are\nholding a React snippet with CSS custom properties, it does not apply here.\n\n### Layer 1 — theme mode + color tokens (whole app)\nThe provider takes a `theme` prop shaped `{ mode, light, dark }`. `mode` is `\"light\"` · `\"dark\"` ·\n`\"auto\"` — **`\"auto\"` is what makes the kit follow the device (OS) light\u002Fdark setting** (it reads\n`useColorScheme()`); the provider default is already `\"auto\"`.\n\n```tsx\n\u002F\u002F Fixed dark for the whole app.\n\u003CCometChatThemeProvider theme={{ mode: \"dark\" }}>{\u002F* ... *\u002F}\u003C\u002FCometChatThemeProvider>\n```\n\n```tsx\n\u002F\u002F Follow the OS, branded in BOTH schemes. mode:\"auto\" is the switch;\n\u002F\u002F set BOTH light and dark or dark falls back to defaults.\n\u003CCometChatThemeProvider\n  theme={{\n    mode: \"auto\",\n    light: { color: { primary: \"#F76808\" } },\n    dark: { color: { primary: \"#F8935B\" } },\n  }}\n>\n  {\u002F* ... *\u002F}\n\u003C\u002FCometChatThemeProvider>\n```\n\n`primary` drives buttons, outgoing bubbles and active states — it is usually the only token a brand\nchange needs. Other common tokens: `textPrimary`, `background1`, `neutral50`, `extendedPrimary500`.\n**Fetch the full list** from `\u002Fui-kit\u002Freact-native\u002Fcolors.md` rather than guessing a token name.\n\nTo follow the OS, use **`mode: \"auto\"`** and set both `light` and `dark`. Without the provider,\nsystem theme changes are not reflected at all.\n\n### Layer 2 — per-component style objects\nEvery component takes a `style` prop holding named sub-style objects — plain RN style objects,\nnot CSS:\n\n```tsx\n\u003CCometChatConversations style={{ containerStyle: { backgroundColor: \"#F7F7F7\" } }} \u002F>\n```\n\nThe same style keys can be set globally through the theme instead, which is preferable when the\nchange should apply everywhere:\n\n```tsx\n\u003CCometChatThemeProvider theme={{ light: { conversationStyles: { \u002F* ... *\u002F } } }}>\n```\n\nStyle-key names differ per component. Fetch them from that component's page\n(`\u002Fui-kit\u002Freact-native\u002Fcomponent-styling.md` and the component's own page) — do not pattern-match\nfrom another component.\n\n### Layer 3 — read the active theme in your own views\n`useTheme()` returns the **resolved** theme (already light-or-dark per `mode`), so custom views match\nthe kit without re-deriving the palette:\n\n```tsx\nimport { useTheme } from \"@cometchat\u002Fchat-uikit-react-native\";\nimport { Text } from \"react-native\";\n\nconst Label = () => {\n  const theme = useTheme();\n  return \u003CText style={{ color: theme.color.textPrimary }}>Chats\u003C\u002FText>;\n};\n```\n\n## Custom message types — the DataSource decorator chain\n\n⚠️ **RN does NOT have the React plugin API.** `CometChatMessagePlugin` and `CometChatPluginRegistry`\ndo not exist in this kit; emitting them will not compile. RN uses a decorator chain.\n\nExtend `DataSourceDecorator`, override what you need, and register it with `ChatConfigurator.enable`:\n\n```tsx\nimport {\n  ChatConfigurator, DataSourceDecorator, CometChatMessageTemplate,\n} from \"@cometchat\u002Fchat-uikit-react-native\";\n\nconst ORDER_TYPE = \"order\";\n\nclass OrderDataSource extends DataSourceDecorator {\n  \u002F\u002F 0. IDENTITY — REQUIRED. The base DataSourceDecorator.getId() THROWS\n  \u002F\u002F (\"Method not implemented.\") and ChatConfigurator.enable() calls getId() to\n  \u002F\u002F dedupe the registry — so a subclass without this override crashes at\n  \u002F\u002F ChatConfigurator.enable(...), NOT at render. Return a stable, unique id.\n  getId(): string {\n    return \"order_message_datasource\";\n  }\n\n  \u002F\u002F 1. RENDER — how the bubble draws.\n  getAllMessageTemplates(theme?: any, params?: any): CometChatMessageTemplate[] {\n    const templates = super.getAllMessageTemplates(theme, params);\n    \u002F\u002F append or replace a template here\n    return templates;\n  }\n\n  \u002F\u002F 2. FETCH — WITHOUT THESE TWO THE MESSAGE IS NEVER RETRIEVED.\n  \u002F\u002F CometChatMessageList builds its request from them:\n  \u002F\u002F   requestBuilder.setTypes(ChatConfigurator.dataSource.getAllMessageTypes())\n  \u002F\u002F   requestBuilder.setCategories(ChatConfigurator.dataSource.getAllMessageCategories())\n  \u002F\u002F A type absent from those filters is excluded server-side. The bubble appears\n  \u002F\u002F optimistically when sent, then vanishes on reload — with no error anywhere.\n  getAllMessageTypes(): string[] {\n    return [...super.getAllMessageTypes(), ORDER_TYPE];\n  }\n\n  getAllMessageCategories(): string[] {\n    const categories = super.getAllMessageCategories();\n    return categories.includes(CometChat.CATEGORY_CUSTOM)\n      ? categories\n      : [...categories, CometChat.CATEGORY_CUSTOM];\n  }\n}\n\n\u002F\u002F AFTER login(), not merely after init(). CometChatUIKit.login() calls enableExtensions(),\n\u002F\u002F whose first statement is ChatConfigurator.init() — \"re-initialize data source\". Anything\n\u002F\u002F registered earlier is DISCARDED, so a decorator wired at module scope, or straight after\n\u002F\u002F init(), silently disappears.\nawait CometChatUIKit.login({ uid: UID });\nChatConfigurator.enable((source) => new OrderDataSource(source));\n```\n\n**`getId()` is REQUIRED on every `DataSourceDecorator` subclass.** It is the ONE base method that\ndoes not delegate to the wrapped source — the base throws `Error(\"Method not implemented.\")`, and\n`ChatConfigurator.enable()` calls `getId()` to dedupe the registry. Omit it and registration crashes\nat `ChatConfigurator.enable(...)` with `Method not implemented.` — NOT at render, so it reads as\nunrelated. Every built-in decorator (Polls, Stickers, Translation, LinkPreview, Collaborative*)\noverrides it; yours must too, returning a stable unique string.\n\nA custom message type is **two halves, and only one of them is obvious.** Render is\n`getAllMessageTemplates` \u002F `getMessageTemplate`. Fetch is `getAllMessageTypes` \u002F\n`getAllMessageCategories`. Ship the render half alone and everything looks right until the first\nreload, when every message of your type is gone — no error, no warning.\n\n`DataSourceDecorator` exposes ~50 overridable methods; the ones you usually want are **`getId`**\n(mandatory — see above), `getAllMessageTemplates`, `getMessageTemplate`, **`getAllMessageTypes`**,\n**`getAllMessageCategories`**, `getMessageOptions` (the long-press menu) and\n`getAuxiliaryOptions` (composer actions). Always call `super.\u003Cmethod>(...)` and modify the result —\nreplacing it wholesale drops every built-in message type.\n\n> **DOCS GAP (RN-G10):** `DataSourceDecorator` \u002F `MessageDataSource` \u002F `ExtensionsDataSource` and\n> `ChatConfigurator.enable` are **not documented** on any RN page — the docs show only mutating\n> existing templates via `getAllMessageTemplates()`. Built from the kit source; flag this to the\n> developer rather than presenting it as documented.\n>\n> **Partially closed (2026-08-20).** `ui-kit\u002Freact-native\u002Fmessage-list` now documents the\n> half that actually breaks builds: a custom type must be registered for **fetch**\n> (`getAllMessageTypes` \u002F `getAllMessageCategories`), not only for render, and the decorator must\n> be registered **after `login()`** because `enableExtensions()` re-runs `ChatConfigurator.init()`.\n> Still missing: a dedicated RN custom-message-types page covering `DataSourceDecorator` \u002F\n> `MessageDataSource` \u002F `ExtensionsDataSource` end to end. Owner: docs.\n\n## Customizing an existing bubble without a decorator\nTo restyle rather than replace, prefer the theme's bubble style keys —\n`textBubbleStyles`, `imageBubbleStyles`, `fileBubbleStyles`, `pollBubbleStyles` and siblings.\nFetch exact keys from `\u002Fui-kit\u002Freact-native\u002Fmessage-bubble-styling.md`.\n\n## Common pitfalls\n1. **Reaching for CSS** — no stylesheets, no `className`, no `--cometchat-*`. Theme object + RN styles.\n2. **Emitting the React plugin API** — does not exist; use `ChatConfigurator` + `DataSourceDecorator`.\n3. **Omitting `getId()` on a decorator** — the base throws; `ChatConfigurator.enable()` calls it → crash at registration with `Method not implemented.`\n4. **Not calling `super`** in a decorator override — silently drops all built-in templates.\n5. **Setting only `light`** when the app follows the OS — dark mode then falls back to defaults.\n6. **Guessing token or style-key names** — fetch them; a wrong key fails silently rather than erroring.\n\n## Verify it works\n- Every symbol appears in `catalogs\u002Frn-v5.json`.\n- `npm run verify:fences:rn-v5` compiles the examples against the pinned kit.\n- On device: toggle OS dark mode and confirm the surface follows; confirm a custom template renders\n  and built-in types still render alongside it.\n",{"name":5,"license":15,"metadata":53,"description":7,"compatibility":57},{"tags":54,"author":55,"version":56},"chat cometchat react-native customization theming styling datasource decorator","CometChat","1.0.0","React Native >=0.77; @cometchat\u002Fchat-uikit-react-native ^5.4.0","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-customization",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-customization",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-customization",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-native-customization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-customization\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fmessage-chrome.md","REFERENCE","参考文档",4550,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-native-customization\u002Freferences\u002Fmessage-chrome.md",[89,98,106,114,122,130],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":97},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":97},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":97},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":97},"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":97},"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",[],[]]