[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFB9BF01DPGXG1RC2SKZY8":3,"skill-same:01M6MFB9BF01DPGXG1RC2SKZY8":80},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MFB9BF01DPGXG1RC2SKZY8","cometchat-flutter-v6-testing",null,"Test a Flutter app that uses the CometChat UI Kit — what is worth testing versus what belongs to the kit, mocking the SDK boundary, widget tests around chat screens, and integration\u002FCI setup. Triggers: 'test my cometchat integration', 'mock cometchat in flutter tests', 'widget test chat screen', 'cometchat test setup'.","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-flutter-v6-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"flutter","cometchat flutter v6 testing","testing","cometchat","flutter testing widget","ci setup","chat","mock","uikit","tests","mocking","triggers","ui","test setup","flutter app","my","verified","screen","kit","ci","flutter testing","app","2026-11-10 10:12:30",false,"---\nname: cometchat-flutter-v6-testing\ndescription: \"Test a Flutter app that uses the CometChat UI Kit — what is worth testing versus what belongs to the kit, mocking the SDK boundary, widget tests around chat screens, and integration\u002FCI setup. Triggers: 'test my cometchat integration', 'mock cometchat in flutter tests', 'widget test chat screen', 'cometchat test setup'.\"\nlicense: \"MIT\"\ncompatibility: \"Flutter >=3.38.9; cometchat_chat_uikit ^6.2.0 (6.2.x; catalog compiler-verified vs 6.1.0, source-checked vs 6.2.0); flutter_test \u002F integration_test\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat flutter testing widget-test mocks integration ci v6\"\n---\n\n> **Ground truth:** kit symbols are catalog-verified against 6.1.0. Test tooling (`flutter_test`, `integration_test`, `mocktail`) is standard Flutter, not CometChat API.\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, `init→login→render`. This skill ASSUMES it.\n- `cometchat-flutter-v6-patterns` — how init\u002Flogin is gated, which is what your tests have to work around.\n\n## Use this skill when\nThe user ASKS for tests. **Building a feature does not imply writing tests** (`RULES.md`) — do not volunteer a test suite as part of \"add chat\".\n\n## Prerequisites & install\n```bash\nflutter pub add --dev mocktail integration_test\n```\n`flutter_test` ships with Flutter.\n\n## Test the RIGHT boundary (the thing most people get wrong)\nDo **not** test the UI Kit. `CometChatConversations` rendering a list, `CometChatMessageList` appending a message, receipts, typing — all CometChat's own tested surface. Asserting on the kit's internals produces slow tests that break on every kit upgrade and prove nothing about YOUR app.\n\nTest what is **yours**:\n| Worth testing | Why |\n|---|---|\n| The init\u002Flogin **gate** | Your logic. Does a chat route stay unreachable until login resolves? |\n| **Navigation wiring** | `onItemTap` pushes the right screen with the right `user`\u002F`group`. |\n| **Target plumbing** | The thread screen receives `parentMessageId` **and** the same user\u002Fgroup — the silent-never-sends trap. |\n| **Config selection** | Prod flavour has no Auth Key; the right App ID per flavour. |\n| **Your own slots** | Custom `listItemView` \u002F `subtitleView` widgets render as expected. |\n| **Error paths** | `onError` surfaces something to the user instead of a blank screen. |\n\n## Widget tests — the practical constraint\nA CometChat widget expects an initialized, logged-in SDK. In a unit\u002Fwidget test there is none, so:\n- **Test your screens' STRUCTURE and wiring**, not the kit's rendered output. Pump your screen and assert your own widgets, callbacks, and navigation.\n- **Keep chat screens behind a thin seam you can substitute** — a factory\u002Fbuilder your test can swap for a stub. This is the single change that makes a CometChat app testable.\n- **Do not try to \"mock the UI Kit widgets\"** — they are concrete widgets, not injectable interfaces. Swap at YOUR seam instead.\n\n```dart\n\u002F\u002F A seam: your screen depends on a builder, so tests substitute a stub for the kit widget.\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\ntypedef ConversationsBuilder = Widget Function(void Function(Conversation) onTap);\n\nclass ChatsScreen extends StatelessWidget {\n  final ConversationsBuilder builder;\n  final void Function(Conversation) onOpen;\n  const ChatsScreen({super.key, required this.builder, required this.onOpen});\n\n  @override\n  Widget build(BuildContext context) => Scaffold(body: SafeArea(child: builder(onOpen)));\n}\n\n\u002F\u002F production wiring\nWidget realConversations(void Function(Conversation) onTap) =>\n    CometChatConversations(onItemTap: onTap);\n```\nIn the test, pass a builder returning a plain `ListView` and assert that tapping a row calls `onOpen` with the right conversation — that is YOUR logic, tested fast and without a network.\n\n## Integration tests (`integration_test`)\nThe only place a real end-to-end chat flow can be asserted, because it needs a real init\u002Flogin.\n- Use a **dedicated test CometChat app** and seeded users (`cometchat-uid-1...`), never production data.\n- Credentials come from the test flavour's settings asset, generated in CI — do not commit them.\n- Keep the suite small: sign in → open a conversation → send a message → assert it appears. Broad E2E over the kit's own surface is slow and re-tests CometChat.\n- Some things **cannot** be automated here and should be stated rather than faked: **push delivery** and **real calls** need physical devices.\n\n## CI\nRun `flutter analyze` + unit\u002Fwidget tests on every PR — they need no credentials. Gate integration tests behind a job that has the test-app secrets, and let them be non-blocking if the environment is flaky; a red build from a missing fixture teaches people to ignore CI.\n\n## Common pitfalls (BAKED)\n- **Writing tests nobody asked for** (`RULES.md`).\n- **Testing the UI Kit** instead of your wiring.\n- **Trying to mock kit widgets directly** — introduce a seam instead.\n- **Widget-testing a screen that calls `init`\u002F`login`** → hangs or throws; gate it behind the seam.\n- **Integration tests against production** — use a test app.\n- **Committing test credentials.**\n- **Claiming push\u002Fcalls are covered** when they need real devices.\n\n## Verify it works\nUnit\u002Fwidget tests run with no network and no credentials; integration tests pass against the test app; `flutter analyze` is clean; nothing in the suite asserts on CometChat's internal rendering.\n","> **Ground truth:** kit symbols are catalog-verified against 6.1.0. Test tooling (`flutter_test`, `integration_test`, `mocktail`) is standard Flutter, not CometChat API.\n\n## Companion skills (read first)\n- `cometchat-flutter-v6-core` — install, credentials, `init→login→render`. This skill ASSUMES it.\n- `cometchat-flutter-v6-patterns` — how init\u002Flogin is gated, which is what your tests have to work around.\n\n## Use this skill when\nThe user ASKS for tests. **Building a feature does not imply writing tests** (`RULES.md`) — do not volunteer a test suite as part of \"add chat\".\n\n## Prerequisites & install\n```bash\nflutter pub add --dev mocktail integration_test\n```\n`flutter_test` ships with Flutter.\n\n## Test the RIGHT boundary (the thing most people get wrong)\nDo **not** test the UI Kit. `CometChatConversations` rendering a list, `CometChatMessageList` appending a message, receipts, typing — all CometChat's own tested surface. Asserting on the kit's internals produces slow tests that break on every kit upgrade and prove nothing about YOUR app.\n\nTest what is **yours**:\n| Worth testing | Why |\n|---|---|\n| The init\u002Flogin **gate** | Your logic. Does a chat route stay unreachable until login resolves? |\n| **Navigation wiring** | `onItemTap` pushes the right screen with the right `user`\u002F`group`. |\n| **Target plumbing** | The thread screen receives `parentMessageId` **and** the same user\u002Fgroup — the silent-never-sends trap. |\n| **Config selection** | Prod flavour has no Auth Key; the right App ID per flavour. |\n| **Your own slots** | Custom `listItemView` \u002F `subtitleView` widgets render as expected. |\n| **Error paths** | `onError` surfaces something to the user instead of a blank screen. |\n\n## Widget tests — the practical constraint\nA CometChat widget expects an initialized, logged-in SDK. In a unit\u002Fwidget test there is none, so:\n- **Test your screens' STRUCTURE and wiring**, not the kit's rendered output. Pump your screen and assert your own widgets, callbacks, and navigation.\n- **Keep chat screens behind a thin seam you can substitute** — a factory\u002Fbuilder your test can swap for a stub. This is the single change that makes a CometChat app testable.\n- **Do not try to \"mock the UI Kit widgets\"** — they are concrete widgets, not injectable interfaces. Swap at YOUR seam instead.\n\n```dart\n\u002F\u002F A seam: your screen depends on a builder, so tests substitute a stub for the kit widget.\nimport 'package:cometchat_chat_uikit\u002Fcometchat_chat_uikit.dart';\nimport 'package:flutter\u002Fmaterial.dart';\n\ntypedef ConversationsBuilder = Widget Function(void Function(Conversation) onTap);\n\nclass ChatsScreen extends StatelessWidget {\n  final ConversationsBuilder builder;\n  final void Function(Conversation) onOpen;\n  const ChatsScreen({super.key, required this.builder, required this.onOpen});\n\n  @override\n  Widget build(BuildContext context) => Scaffold(body: SafeArea(child: builder(onOpen)));\n}\n\n\u002F\u002F production wiring\nWidget realConversations(void Function(Conversation) onTap) =>\n    CometChatConversations(onItemTap: onTap);\n```\nIn the test, pass a builder returning a plain `ListView` and assert that tapping a row calls `onOpen` with the right conversation — that is YOUR logic, tested fast and without a network.\n\n## Integration tests (`integration_test`)\nThe only place a real end-to-end chat flow can be asserted, because it needs a real init\u002Flogin.\n- Use a **dedicated test CometChat app** and seeded users (`cometchat-uid-1...`), never production data.\n- Credentials come from the test flavour's settings asset, generated in CI — do not commit them.\n- Keep the suite small: sign in → open a conversation → send a message → assert it appears. Broad E2E over the kit's own surface is slow and re-tests CometChat.\n- Some things **cannot** be automated here and should be stated rather than faked: **push delivery** and **real calls** need physical devices.\n\n## CI\nRun `flutter analyze` + unit\u002Fwidget tests on every PR — they need no credentials. Gate integration tests behind a job that has the test-app secrets, and let them be non-blocking if the environment is flaky; a red build from a missing fixture teaches people to ignore CI.\n\n## Common pitfalls (BAKED)\n- **Writing tests nobody asked for** (`RULES.md`).\n- **Testing the UI Kit** instead of your wiring.\n- **Trying to mock kit widgets directly** — introduce a seam instead.\n- **Widget-testing a screen that calls `init`\u002F`login`** → hangs or throws; gate it behind the seam.\n- **Integration tests against production** — use a test app.\n- **Committing test credentials.**\n- **Claiming push\u002Fcalls are covered** when they need real devices.\n\n## Verify it works\nUnit\u002Fwidget tests run with no network and no credentials; integration tests pass against the test app; `flutter analyze` is clean; nothing in the suite asserts on CometChat's internal rendering.\n",{"name":5,"license":15,"metadata":51,"description":7,"compatibility":55},{"tags":52,"author":53,"version":54},"cometchat flutter testing widget-test mocks integration ci v6","CometChat","1.0.0","Flutter >=3.38.9; cometchat_chat_uikit ^6.2.0 (6.2.x; catalog compiler-verified vs 6.1.0, source-checked vs 6.2.0); flutter_test \u002F integration_test","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-testing",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-testing",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-testing",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-flutter-v6-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-flutter-v6-testing\u002FSKILL.md",true,[],[81,90,98,106,114,122],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"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":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":89},"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":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":89},"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":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":89},"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":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":89},"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",[],[]]