[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFCZ80KPQ9Z3R7MNQ29S4Z":3,"skill-same:01M6MFCZ80KPQ9Z3R7MNQ29S4Z":75},{"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":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MFCZ80KPQ9Z3R7MNQ29S4Z","cometchat-ios-production",null,"Ship a CometChat iOS (Swift) integration safely — server-minted auth tokens instead of the Auth Key, keeping secrets out of the app binary, and a pre-launch checklist. Triggers: 'is my cometchat ios production ready', 'auth token instead of auth key swift', 'secure cometchat ios', 'going live checklist ios', 'harden cometchat swift before launch'.","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-ios-production\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"ios","Production","cometchat ios production","cometchat","auth tokens","pre-launch","swift","spm","appstore","ship","security","live","my","token","secure","secrets","server","xcode","only","auth","ready","app","2026-11-10 10:12:30",false,"---\nname: cometchat-ios-production\ndescription: \"Ship a CometChat iOS (Swift) integration safely — server-minted auth tokens instead of the Auth Key, keeping secrets out of the app binary, and a pre-launch checklist. Triggers: 'is my cometchat ios production ready', 'auth token instead of auth key swift', 'secure cometchat ios', 'going live checklist ios', 'harden cometchat swift before launch'.\"\nlicense: \"MIT\"\ncompatibility: \"CometChatUIKitSwift 5.2.3+ (Up to Next Major; resolves CometChatSDK 4.1.10+); Xcode 16+; iOS 15.1+; SPM only\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat ios swift production security auth-token hardening appstore\"\n---\n\n> **Ground truth:** `CometChatUIKitSwift` 5.2.3 + `CometChatSDK` 4.1.10 (symbols verified vs `catalogs\u002Fios-v5.json`). The login\u002Fauth-token API is FETCHED via `cometchat-ios-core\u002Freferences\u002Fdocs-map.md`; the REST auth-token endpoint is `{DOCS_BASE}\u002Frest-api\u002Fauth-tokens`. **The iOS UI Kit docs have no single production-hardening page** — this checklist is the pack's own guidance from `RULES.md` §4 + `cometchat-ios-core\u002Freferences\u002Fsetup-credentials.md`, labelled as such. Tracked DOCS GAP.\n\n## Companion skills (read first)\n- `cometchat-ios-core` — `references\u002Fsetup-credentials.md` (the `Secrets.xcconfig` → Info.plist → `Bundle.main` flow) and `references\u002Fswiftui.md` (the init→login launch hook) this hardens.\n- `cometchat-security` — the enterprise auth model this client-side hardening plugs into: wiring your IdP \u002F SSO into the token flow (your IdP → your server → mint the CometChat auth token; CometChat is **not** an IdP), token expiry\u002Frefresh + re-login, RBAC roles + group (SBAC) scopes, and Auth Key vs auth token vs REST API Key. Load it for a security review or any SSO question.\n\n## Use this skill when\nMoving off the development setup: TestFlight\u002FApp Store submission, a security review, or \"is this safe to ship.\"\n\n## The one thing that matters\n**Never embed the Auth Key in the app binary.**\n\nThe Auth Key can mint a session for **any user in your app**. Anything baked into the app — an `xcconfig` value promoted into `Info.plist`, a string constant — is recoverable from the shipped `.ipa` (`strings`, class-dump). Treat it as public.\n\n| | Development | Production |\n| --- | --- | --- |\n| Login | `CometChatUIKit.login(uid:...)` | `CometChatUIKit.login(authToken:...)` |\n| Auth Key | in `Secrets.xcconfig` | **not in the build** |\n| Token source | n\u002Fa | your backend, per authenticated user |\n| REST API Key | never in the app | server only |\n\n## The production login flow\n1. Your app authenticates the user (your own auth \u002F sign-in with Apple \u002F your backend).\n2. Your **server** mints a CometChat auth token for that user's UID via the REST API using the **REST API Key** (`{DOCS_BASE}\u002Frest-api\u002Fauth-tokens`).\n3. The server returns the token to the app over an authenticated HTTPS request.\n4. The app calls `login(authToken:)`.\n\n```swift\n\u002F\u002F UID comes from the SERVER session, never from the client\nlet authToken = try await fetchCometChatToken()   \u002F\u002F your authenticated endpoint\nCometChatUIKit.login(authToken: authToken) { result in \u002F* handle success\u002Ffailure *\u002F }\n```\n`init` must resolve first (`initFromSettings`), then login — calling login before init resolves fails silently (`cometchat-ios-core`).\n\n## Keep secrets out of the build\nDevelopment reads the Auth Key from a gitignored `Secrets.xcconfig` promoted into `Info.plist`. For production, ship **App ID + Region only** (not secrets — they identify the app) and log in with a token; leave the Auth-Key value empty in the release configuration.\n```bash\n# after an archive\u002Fbuild, confirm the key is not in the app binary\nstrings \"$APP_BUNDLE\u002FYourApp\" | grep -q \"\u003Cyour-auth-key>\" && echo \"LEAK\" || echo \"clean\"\n```\nAlso verify `Secrets.xcconfig` is in `.gitignore` (only a committed placeholder), and that it is not bundled as a resource.\n\n## Also before launch\n- **Users are created server-side** as part of signup — not from the app with the Auth Key.\n- **Log out properly**: `CometChatUIKit.logout()`, then clear derived state and unregister VoIP\u002FAPNs push tokens (`cometchat-ios-push`).\n- **Pin exact versions** — the kit is a prebuilt binary compiled against one Chat SDK version; a drifting `CometChatSDK` breaks it (`cometchat-ios-core` Install).\n- **App Transport Security**: keep HTTPS; do not add broad `NSAllowsArbitraryLoads` exceptions.\n- **Calls need permissions**: `NSCameraUsageDescription` + `NSMicrophoneUsageDescription` with real strings, or App Review rejects; VoIP push needs the entitlement.\n- **Region must match** the dashboard app.\n- **Enable dashboard extensions\u002FAI on the PRODUCTION app**, not just dev.\n\n## Pre-launch checklist\n- [ ] Auth Key not in the app binary (`strings`-verified)\n- [ ] `login(authToken:)` in production; UID from the server session\n- [ ] REST API Key server-side only\n- [ ] `Secrets.xcconfig` gitignored; only a placeholder committed\n- [ ] Exact kit\u002FSDK\u002FCalls versions pinned\n- [ ] Camera\u002Fmic usage strings + VoIP entitlement present (if calling)\n- [ ] Logout clears session, state and push tokens\n- [ ] Dashboard extensions\u002FAI enabled for the production app\n- [ ] Tested against the production app's credentials\n\n## Common pitfalls\n1. **Auth Key recoverable from the `.ipa`** — the critical one.\n2. **Token endpoint trusting a client-supplied UID** — impersonation.\n3. **Login before init resolves** — silent no-render (order invariant).\n4. **Missing usage-description strings** — App Review rejection for calling apps.\n5. **Dashboard configured on the dev app only** — features silently missing in production.\n\n## Verify it works\nArchived build's binary contains no Auth Key (`strings`) · login works via token · a tampered UID is rejected by the server · logout fully clears · calls request permission and connect · features enabled on the production app.\n","> **Ground truth:** `CometChatUIKitSwift` 5.2.3 + `CometChatSDK` 4.1.10 (symbols verified vs `catalogs\u002Fios-v5.json`). The login\u002Fauth-token API is FETCHED via `cometchat-ios-core\u002Freferences\u002Fdocs-map.md`; the REST auth-token endpoint is `{DOCS_BASE}\u002Frest-api\u002Fauth-tokens`. **The iOS UI Kit docs have no single production-hardening page** — this checklist is the pack's own guidance from `RULES.md` §4 + `cometchat-ios-core\u002Freferences\u002Fsetup-credentials.md`, labelled as such. Tracked DOCS GAP.\n\n## Companion skills (read first)\n- `cometchat-ios-core` — `references\u002Fsetup-credentials.md` (the `Secrets.xcconfig` → Info.plist → `Bundle.main` flow) and `references\u002Fswiftui.md` (the init→login launch hook) this hardens.\n- `cometchat-security` — the enterprise auth model this client-side hardening plugs into: wiring your IdP \u002F SSO into the token flow (your IdP → your server → mint the CometChat auth token; CometChat is **not** an IdP), token expiry\u002Frefresh + re-login, RBAC roles + group (SBAC) scopes, and Auth Key vs auth token vs REST API Key. Load it for a security review or any SSO question.\n\n## Use this skill when\nMoving off the development setup: TestFlight\u002FApp Store submission, a security review, or \"is this safe to ship.\"\n\n## The one thing that matters\n**Never embed the Auth Key in the app binary.**\n\nThe Auth Key can mint a session for **any user in your app**. Anything baked into the app — an `xcconfig` value promoted into `Info.plist`, a string constant — is recoverable from the shipped `.ipa` (`strings`, class-dump). Treat it as public.\n\n| | Development | Production |\n| --- | --- | --- |\n| Login | `CometChatUIKit.login(uid:...)` | `CometChatUIKit.login(authToken:...)` |\n| Auth Key | in `Secrets.xcconfig` | **not in the build** |\n| Token source | n\u002Fa | your backend, per authenticated user |\n| REST API Key | never in the app | server only |\n\n## The production login flow\n1. Your app authenticates the user (your own auth \u002F sign-in with Apple \u002F your backend).\n2. Your **server** mints a CometChat auth token for that user's UID via the REST API using the **REST API Key** (`{DOCS_BASE}\u002Frest-api\u002Fauth-tokens`).\n3. The server returns the token to the app over an authenticated HTTPS request.\n4. The app calls `login(authToken:)`.\n\n```swift\n\u002F\u002F UID comes from the SERVER session, never from the client\nlet authToken = try await fetchCometChatToken()   \u002F\u002F your authenticated endpoint\nCometChatUIKit.login(authToken: authToken) { result in \u002F* handle success\u002Ffailure *\u002F }\n```\n`init` must resolve first (`initFromSettings`), then login — calling login before init resolves fails silently (`cometchat-ios-core`).\n\n## Keep secrets out of the build\nDevelopment reads the Auth Key from a gitignored `Secrets.xcconfig` promoted into `Info.plist`. For production, ship **App ID + Region only** (not secrets — they identify the app) and log in with a token; leave the Auth-Key value empty in the release configuration.\n```bash\n# after an archive\u002Fbuild, confirm the key is not in the app binary\nstrings \"$APP_BUNDLE\u002FYourApp\" | grep -q \"\u003Cyour-auth-key>\" && echo \"LEAK\" || echo \"clean\"\n```\nAlso verify `Secrets.xcconfig` is in `.gitignore` (only a committed placeholder), and that it is not bundled as a resource.\n\n## Also before launch\n- **Users are created server-side** as part of signup — not from the app with the Auth Key.\n- **Log out properly**: `CometChatUIKit.logout()`, then clear derived state and unregister VoIP\u002FAPNs push tokens (`cometchat-ios-push`).\n- **Pin exact versions** — the kit is a prebuilt binary compiled against one Chat SDK version; a drifting `CometChatSDK` breaks it (`cometchat-ios-core` Install).\n- **App Transport Security**: keep HTTPS; do not add broad `NSAllowsArbitraryLoads` exceptions.\n- **Calls need permissions**: `NSCameraUsageDescription` + `NSMicrophoneUsageDescription` with real strings, or App Review rejects; VoIP push needs the entitlement.\n- **Region must match** the dashboard app.\n- **Enable dashboard extensions\u002FAI on the PRODUCTION app**, not just dev.\n\n## Pre-launch checklist\n- [ ] Auth Key not in the app binary (`strings`-verified)\n- [ ] `login(authToken:)` in production; UID from the server session\n- [ ] REST API Key server-side only\n- [ ] `Secrets.xcconfig` gitignored; only a placeholder committed\n- [ ] Exact kit\u002FSDK\u002FCalls versions pinned\n- [ ] Camera\u002Fmic usage strings + VoIP entitlement present (if calling)\n- [ ] Logout clears session, state and push tokens\n- [ ] Dashboard extensions\u002FAI enabled for the production app\n- [ ] Tested against the production app's credentials\n\n## Common pitfalls\n1. **Auth Key recoverable from the `.ipa`** — the critical one.\n2. **Token endpoint trusting a client-supplied UID** — impersonation.\n3. **Login before init resolves** — silent no-render (order invariant).\n4. **Missing usage-description strings** — App Review rejection for calling apps.\n5. **Dashboard configured on the dev app only** — features silently missing in production.\n\n## Verify it works\nArchived build's binary contains no Auth Key (`strings`) · login works via token · a tampered UID is rejected by the server · logout fully clears · calls request permission and connect · features enabled on the production app.\n",{"name":5,"license":15,"metadata":46,"description":7,"compatibility":50},{"tags":47,"author":48,"version":49},"cometchat ios swift production security auth-token hardening appstore","CometChat","1.0.0","CometChatUIKitSwift 5.2.3+ (Up to Next Major; resolves CometChatSDK 4.1.10+); Xcode 16+; iOS 15.1+; SPM only","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-ios-production",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-ios-production",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-ios-production",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-ios-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-ios-production\u002FSKILL.md",true,[],[76,85,93,101,109,117],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"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",[],[]]