[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFMBTEK6RXAHDFZN31H0VS":3,"skill-same:01M6MFMBTEK6RXAHDFZN31H0VS":79},{"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},"01M6MFMBTEK6RXAHDFZN31H0VS","cometchat-react-v7-troubleshooting",null,"Diagnose a broken CometChat React v7 integration — blank panes, a collapsed\u002F0-height surface, empty lists, no messages, the kit's error state, events that never fire, or a version_conflict. Triggers: 'cometchat react not working', 'chat is blank', 'conversations empty', 'messages not showing react', 'something went wrong cometchat', 'cometchat react errors', 'why is my chat broken'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-troubleshooting\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","cometchat react v7 troubleshooting","troubleshooting","react","conflict","verified","my","conversations","kit","errors","error","events","screen","next","never","router","broken","why","astro","messages","diagnostics","2026-11-10 10:12:30",false,"---\nname: cometchat-react-v7-troubleshooting\ndescription: \"Diagnose a broken CometChat React v7 integration — blank panes, a collapsed\u002F0-height surface, empty lists, no messages, the kit's error state, events that never fire, or a version_conflict. Triggers: 'cometchat react not working', 'chat is blank', 'conversations empty', 'messages not showing react', 'something went wrong cometchat', 'cometchat react errors', 'why is my chat broken'.\"\nlicense: \"MIT\"\ncompatibility: \"@cometchat\u002Fchat-uikit-react ^7 (7.1.x–7.2.x verified); React 18–19; Vite \u002F Next.js \u002F CRA \u002F React Router \u002F Astro\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat react v7 troubleshooting debug diagnostics blank-screen version-conflict\"\n---\n\n> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7`. Symbols\u002Fsignatures are verified against `cometchat-react-v7-core` + its catalog and FETCHED via `references\u002Fdocs-map.md`; the rules referenced (init order, layout sizing, credentials) are `RULES.md`. This diagnostics catalog is cross-checked against the live `{DOCS_BASE}\u002Fui-kit\u002Freact\u002Ftroubleshooting.md` page (base + paths in `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`), and adds the host-side\u002Fruntime symptoms it doesn't cover.\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — the correct init→login→render order, credentials, and the reflow-free layout the fixes below restore.\n\n## Use this skill when\nA React CometChat integration compiles but misbehaves at runtime: blank, empty, unresponsive, or throwing.\n\n## Start here — React fails on the ORDER and the BOX\nTwo causes explain most \"it's blank\":\n1. **A kit component rendered before `init()` + `login()` resolved.** The surface must be gated on the resolved logged-in user. Rendering it eagerly (or during SSR) yields an empty\u002Ferroring pane.\n2. **The container has no height.** The kit fills its parent; a parent at `height:auto`\u002F`0` collapses it to a sliver. This is a host CSS defect, not a kit bug (`RULES.md` → Layout \u002F sizing).\n\n## Symptom → cause → fix\n| Symptom | Likely cause | Fix |\n| --- | --- | --- |\n| Blank\u002Fwhite, no errors | Surface rendered before init+login resolved | Gate render on the resolved user; keep `CometChatErrorBoundary` for a visible fallback |\n| Blank during SSR \u002F `window is not defined` | A kit component imported or rendered on the server (Next.js, Astro, Remix) | Render the surface client-only — `\"use client\"` + `dynamic(..., { ssr:false })` (Next), `client:only` (Astro); see core `references\u002Fssr.md` |\n| Surface ~0px \u002F cramped top-left | Ancestor chain has no height | `html,body,#root{height:100%}` + a pinned surface (`100dvh` full-app) + panes `min-height:0`; see core `references\u002Flayout.md` |\n| \"OOPS! Looks like something went wrong\" | The kit's error state — a call threw (often a custom `ConversationsRequestBuilder` with no `.setLimit(n)`, or a bad Region) | Add `.setLimit(30)`; confirm Region matches the dashboard app |\n| Conversations empty | New\u002Fseeded app has no conversations yet, or scope excludes them | Send a first message; check `conversationsRequestBuilder` scope (`user`\u002F`group`) matches intent |\n| `login()` fails \"user not found\" | UID does not exist in the app | Use a real UID (Dashboard → Users; fresh apps seed `cometchat-uid-1`) — never a guessed `superhero*` |\n| Nothing updates live | Missing\u002Fduplicated listeners, or StrictMode double-mount | Add listeners with a stable ID, remove on unmount; guard the init\u002Flogin in-flight (`cometchat-react-v7-patterns`) |\n| Roster rows appear TWICE + ~30 \"duplicate key\" errors (dev only) | React **StrictMode** double-invokes effects; the roster drop-ins `CometChatUsers`\u002F`CometChatGroups`\u002F`CometChatGroupMembers` double-append (kit de-dupe gap; `CometChatConversations` is unaffected) | A dev-only StrictMode artifact — gone in `vite build`\u002Fprod. Do **NOT** remove StrictMode to \"fix\" it; verify the roster in a production build. Kit issue — report upstream |\n| Localized keys shown raw (e.g. `group_info`) | Wrong\u002Fstale i18n key or provider missing | Use the kit component \u002F correct key; ensure `CometChatProvider` wraps the tree |\n| Works in dev, blank in prod | Wrong env prefix → Auth Key\u002FApp ID missing in the bundle | Fix the bundler prefix; grep the build (`cometchat-react-v7-production`) |\n| `version_conflict` on detect | Project on UI Kit v6 while skills target v7 | STOP and reconcile — migrate v6→v7 (`cometchat-react-v7-migration`), or stay on v6 by installing the older **v4 skills pack** (it targets the v6 UI Kit) |\n\n## When the table does not cover it\nOpen the browser console + network tab: a `401` is auth (bad token\u002FAuth Key\u002FRegion), a `402` is a plan-gated feature (e.g. Search — enable it in the dashboard), a `4xx` \"no conversation yet\" is benign. Then fetch the feature's page via `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`. Never diagnose from `node_modules`\u002F`.d.ts` or memory.\n\n## Verify it works\nInit+login resolve before the surface renders · the surface has real dimensions (not a sliver) · conversations render or show the kit's empty state (not the error state) · a message sends and arrives live · no raw localization keys · production build carries no Auth Key.\n\n## What NOT to do\nDo not silence the error boundary to hide a thrown call; do not hard-code a UID to dodge \"user not found\"; do not read kit internals to work around a missing prop — fetch the documented prop instead.\n","> **Ground truth:** `@cometchat\u002Fchat-uikit-react@7`. Symbols\u002Fsignatures are verified against `cometchat-react-v7-core` + its catalog and FETCHED via `references\u002Fdocs-map.md`; the rules referenced (init order, layout sizing, credentials) are `RULES.md`. This diagnostics catalog is cross-checked against the live `{DOCS_BASE}\u002Fui-kit\u002Freact\u002Ftroubleshooting.md` page (base + paths in `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`), and adds the host-side\u002Fruntime symptoms it doesn't cover.\n\n## Companion skills (read first)\n- `cometchat-react-v7-core` — the correct init→login→render order, credentials, and the reflow-free layout the fixes below restore.\n\n## Use this skill when\nA React CometChat integration compiles but misbehaves at runtime: blank, empty, unresponsive, or throwing.\n\n## Start here — React fails on the ORDER and the BOX\nTwo causes explain most \"it's blank\":\n1. **A kit component rendered before `init()` + `login()` resolved.** The surface must be gated on the resolved logged-in user. Rendering it eagerly (or during SSR) yields an empty\u002Ferroring pane.\n2. **The container has no height.** The kit fills its parent; a parent at `height:auto`\u002F`0` collapses it to a sliver. This is a host CSS defect, not a kit bug (`RULES.md` → Layout \u002F sizing).\n\n## Symptom → cause → fix\n| Symptom | Likely cause | Fix |\n| --- | --- | --- |\n| Blank\u002Fwhite, no errors | Surface rendered before init+login resolved | Gate render on the resolved user; keep `CometChatErrorBoundary` for a visible fallback |\n| Blank during SSR \u002F `window is not defined` | A kit component imported or rendered on the server (Next.js, Astro, Remix) | Render the surface client-only — `\"use client\"` + `dynamic(..., { ssr:false })` (Next), `client:only` (Astro); see core `references\u002Fssr.md` |\n| Surface ~0px \u002F cramped top-left | Ancestor chain has no height | `html,body,#root{height:100%}` + a pinned surface (`100dvh` full-app) + panes `min-height:0`; see core `references\u002Flayout.md` |\n| \"OOPS! Looks like something went wrong\" | The kit's error state — a call threw (often a custom `ConversationsRequestBuilder` with no `.setLimit(n)`, or a bad Region) | Add `.setLimit(30)`; confirm Region matches the dashboard app |\n| Conversations empty | New\u002Fseeded app has no conversations yet, or scope excludes them | Send a first message; check `conversationsRequestBuilder` scope (`user`\u002F`group`) matches intent |\n| `login()` fails \"user not found\" | UID does not exist in the app | Use a real UID (Dashboard → Users; fresh apps seed `cometchat-uid-1`) — never a guessed `superhero*` |\n| Nothing updates live | Missing\u002Fduplicated listeners, or StrictMode double-mount | Add listeners with a stable ID, remove on unmount; guard the init\u002Flogin in-flight (`cometchat-react-v7-patterns`) |\n| Roster rows appear TWICE + ~30 \"duplicate key\" errors (dev only) | React **StrictMode** double-invokes effects; the roster drop-ins `CometChatUsers`\u002F`CometChatGroups`\u002F`CometChatGroupMembers` double-append (kit de-dupe gap; `CometChatConversations` is unaffected) | A dev-only StrictMode artifact — gone in `vite build`\u002Fprod. Do **NOT** remove StrictMode to \"fix\" it; verify the roster in a production build. Kit issue — report upstream |\n| Localized keys shown raw (e.g. `group_info`) | Wrong\u002Fstale i18n key or provider missing | Use the kit component \u002F correct key; ensure `CometChatProvider` wraps the tree |\n| Works in dev, blank in prod | Wrong env prefix → Auth Key\u002FApp ID missing in the bundle | Fix the bundler prefix; grep the build (`cometchat-react-v7-production`) |\n| `version_conflict` on detect | Project on UI Kit v6 while skills target v7 | STOP and reconcile — migrate v6→v7 (`cometchat-react-v7-migration`), or stay on v6 by installing the older **v4 skills pack** (it targets the v6 UI Kit) |\n\n## When the table does not cover it\nOpen the browser console + network tab: a `401` is auth (bad token\u002FAuth Key\u002FRegion), a `402` is a plan-gated feature (e.g. Search — enable it in the dashboard), a `4xx` \"no conversation yet\" is benign. Then fetch the feature's page via `cometchat-react-v7-core\u002Freferences\u002Fdocs-map.md`. Never diagnose from `node_modules`\u002F`.d.ts` or memory.\n\n## Verify it works\nInit+login resolve before the surface renders · the surface has real dimensions (not a sliver) · conversations render or show the kit's empty state (not the error state) · a message sends and arrives live · no raw localization keys · production build carries no Auth Key.\n\n## What NOT to do\nDo not silence the error boundary to hide a thrown call; do not hard-code a UID to dodge \"user not found\"; do not read kit internals to work around a missing prop — fetch the documented prop instead.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":54},{"tags":51,"author":52,"version":53},"cometchat react v7 troubleshooting debug diagnostics blank-screen version-conflict","CometChat","1.0.0","@cometchat\u002Fchat-uikit-react ^7 (7.1.x–7.2.x verified); React 18–19; Vite \u002F Next.js \u002F CRA \u002F React Router \u002F Astro","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-troubleshooting",490,"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 02:12:02",{"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-troubleshooting",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-troubleshooting",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-react-v7-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-react-v7-troubleshooting\u002FSKILL.md",true,[],[80,89,96,103,128,152],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":84,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":88},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":88},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\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":84,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":45},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[110,111,38,34,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"search","deja search","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":45},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[135,136,137,123,138,139,140,37,141,142,143,144,145,146,113,147,148,149,150,151],"deja reflect","reflect","review","with","record","github","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":167,"publishedAt":45},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[158,161,164],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[154,168,169,170,171,172,173,148,174,114,175,176,177,178,119,179,180,181,182,183],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]