@cometchat/skills 4.0.0 → 4.2.0

package/skills/cometchat-ios-calls/references/voip-cert-setup.md

@@ -0,0 +1,166 @@
+# VoIP cert setup — the manual Apple Developer steps
+
+The skill cannot automate these. They require browser access to https://developer.apple.com and physical possession of the developer team's signing identity. This reference is the printed instruction sheet the dispatcher hands the user.
+
+Print this verbatim during scaffold; pause execution until the user confirms each step.
+
+---
+
+## What you're creating
+
+A **VoIP Services certificate** is a separate certificate from your standard APNs (push notifications) certificate. It's specifically for PushKit VoIP delivery — the high-priority, terminated-app-wakeup channel iOS provides for calling apps.
+
+Without this certificate, your push server cannot deliver VoIP pushes. The OS won't ring the user's lock screen. CallKit never fires.
+
+---
+
+## Prerequisites
+
+- Apple Developer Program membership (paid — free accounts can't create VoIP certs)
+- Admin or App Manager role in the developer team
+- The bundle ID of your app already registered in https://developer.apple.com/account/resources/identifiers/list
+- Mac with Keychain Access (the cert must be generated from a CSR signed by your dev keychain)
+
+---
+
+## Step-by-step
+
+### 1. Generate a Certificate Signing Request
+
+On your Mac:
+
+1. Open **Keychain Access** (`/Applications/Utilities/Keychain Access.app`)
+2. Menu: **Keychain Access → Certificate Assistant → Request a Certificate from a Certificate Authority...**
+3. Fill in:
+   - **User Email Address:** your Apple ID email
+   - **Common Name:** something like "YourApp VoIP CSR"
+   - **CA Email Address:** leave blank
+   - **Request is:** Saved to disk + Let me specify key pair information (check both)
+4. Click Continue → save the `.certSigningRequest` file (e.g. to Desktop)
+5. On the key-pair-info screen: 2048 bits, RSA → Continue → save
+
+### 2. Create the cert in Apple Developer portal
+
+1. Open https://developer.apple.com/account/resources/certificates/list
+2. Click the "+" button to add a new certificate
+3. Under "Services", select **VoIP Services Certificate** → Continue
+4. Pick the App ID (bundle ID) of your app from the dropdown → Continue
+5. Upload the `.certSigningRequest` file you just created → Continue
+6. Apple generates the cert. Click **Download** → saves a `.cer` file (e.g. `voip_services.cer`)
+
+### 3. Install the cert in Keychain
+
+1. Double-click the `.cer` file → Keychain Access opens with the cert added
+2. Find it in the "My Certificates" category — should expand to show a private key alongside
+
+### 4. Export as .p12
+
+1. Right-click the cert → **Export "VoIP Services: ..."**
+2. File Format: **Personal Information Exchange (.p12)**
+3. Save → enter a passphrase (you'll need this on the push server)
+4. Output: a `.p12` file (e.g. `voip_services.p12`)
+
+### 5. (Optional) Convert .p12 to .pem for some push libs
+
+Some Node.js libraries (e.g. `node-apn` older versions) need `.pem`:
+
+```bash
+openssl pkcs12 -in voip_services.p12 -out voip_cert.pem -nodes -clcerts
+```
+
+The `.pem` contains both cert and key.
+
+### 6. Upload to your push server
+
+Where this goes depends on your stack:
+
+- **Node.js (`node-apn` v3+):** point at the `.p12` file via `cert: { path, passphrase }`
+- **Server-side using `apn` lib:** load the cert + key
+- **Self-managed APNs:** use the .p12 directly via `curl` to APNs HTTP/2 endpoint
+- **Third-party services (OneSignal, Firebase APNs forwarding):** they have UIs to upload the .p12 + passphrase
+
+---
+
+## Critical detail: the topic
+
+When sending a VoIP push, the APNs `topic` header MUST be your bundle ID **with `.voip` suffix**:
+
+```
+apns-topic: com.yourcompany.yourapp.voip
+```
+
+NOT just `com.yourcompany.yourapp` — that's the standard APNs topic for non-VoIP pushes. The two are separate channels.
+
+If you set the wrong topic, APNs returns `BadDeviceToken` or `TopicMismatch` and your call doesn't ring.
+
+In `node-apn`:
+
+```ts
+const note = new apn.Notification();
+note.topic = `${process.env.IOS_BUNDLE_ID}.voip`;
+note.pushType = "voip";
+```
+
+`pushType: "voip"` is required by APNs HTTP/2 protocol since iOS 13.
+
+---
+
+## Cert expiration
+
+VoIP certs expire after **1 year**. Calendar this — Apple will email a warning ~30 days before expiry, but it's easy to miss in inbox noise. When the cert expires:
+
+- iOS devices keep working briefly (cached subscriptions)
+- New incoming-call pushes silently fail
+- Users complain "I'm not getting calls anymore"
+
+Renew by repeating steps 1-6. The new cert can replace the old in your push server with no client-side change required (devices use the same VoIP push token).
+
+---
+
+## Bypassing the cert: APNs Auth Tokens (.p8)
+
+Apple now supports **token-based auth** for APNs (since iOS 10) — a `.p8` key + key ID + team ID instead of a per-app cert. Pros:
+
+- Single key works for all your apps (vs one cert per bundle)
+- Doesn't expire (you rotate manually when you want)
+- Easier rotation
+
+Cons:
+
+- Some older push libraries don't support it
+- Setup process is different
+
+To use:
+
+1. Apple Developer portal → Keys → "+" → APNs (Authentication Key)
+2. Download the `.p8` (one-time download — Apple won't let you download it again)
+3. Note the Key ID + Team ID
+4. Configure your push lib with `{ token: { key: ".p8 contents", keyId, teamId } }`
+
+The skill prefers token-auth for new push servers; uses cert auth if the project already has one.
+
+---
+
+## When stuck
+
+| Error | Fix |
+|---|---|
+| `BadDeviceToken` from APNs | Topic mismatch — `.voip` suffix missing, or production token used with sandbox cert |
+| `TopicDisallowed` | The cert is for a different bundle ID |
+| `Unregistered` | Token expired or app uninstalled — drop from your DB |
+| `BadCertificate` | Cert expired or tampered — re-export or re-generate |
+| `BadCertificateEnvironment` | Production cert + sandbox token, or vice versa |
+| `Forbidden` | Cert revoked or topic doesn't match |
+
+---
+
+## Sandbox vs production
+
+Apple has two APNs environments:
+
+- **Sandbox** (Xcode debug builds, dev provisioning profile) — uses sandbox APNs (api.sandbox.push.apple.com)
+- **Production** (TestFlight + App Store, distribution profile) — uses production APNs (api.push.apple.com)
+
+VoIP cert covers both — the same cert works for sandbox and production tokens. But the SERVER must hit the right endpoint depending on which environment the device token was registered against.
+
+The skill writes the push server with environment switching (`production: process.env.NODE_ENV === "production"` for `node-apn`).

package/skills/cometchat-ios-components/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-components
 description: "Complete catalog of CometChat iOS UI Kit v5 components with correct usage patterns from official documentation."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; CometChatSDK ^4; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-core/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-core
 description: "Shared rules for CometChat iOS UI Kit v5. Always loaded alongside placement skills. Read this first."
 license: "MIT"
 compatibility: "iOS 13+; Swift 5.0+; CometChatUIKitSwift ^5; CometChatSDK ^4"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-customization/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-customization
 description: "Customize CometChat iOS UI Kit beyond theming — custom views, message templates, text formatters, and event handling."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-features/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-features
 description: "Feature catalog for CometChat iOS UI Kit — calls, reactions, polls, stickers, AI features, and extensions."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-placement/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-placement
 description: "WHERE to put CometChat in your iOS app — navigation patterns, tab bars, modals, and embedded views."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-production/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-production
 description: "Production-ready CometChat iOS setup — server-side auth tokens, security best practices, and deployment checklist."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-push/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-push
 description: "Set up push notifications for CometChat iOS apps — APNs configuration, token registration, and notification handling."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-testing/SKILL.md

@@ -0,0 +1,371 @@
+---
+name: cometchat-ios-testing
+description: Testing patterns for CometChat iOS UI Kit v5 in Swift / SwiftUI / UIKit projects. Covers XCTest setup, mocking CometChatSDK + CometChatUIKitSwift via protocols, snapshot testing with iOSSnapshotTestCase, async/await test helpers, UI testing for full chat flows on simulators, and CI on Xcode Cloud / GitHub Actions.
+license: "MIT"
+compatibility: "Xcode 15+, Swift 5.9+, iOS 13+ deployment target; XCTest (built-in); SnapshotTesting >= 1.15 (Pointfree); CometChatUIKitSwift ~> 5.1"
+allowed-tools: "shell, file-read, file-search, file-list, ask-user"
+metadata:
+  author: "CometChat"
+  version: "4.0.0"
+  tags: "cometchat ios testing xctest swift uikit swiftui mocking snapshot async-await ui-tests xcode-cloud github-actions"
+---
+
+## Purpose
+
+Testing patterns for iOS CometChat integrations. XCTest (built-in) for unit + integration; SnapshotTesting (Pointfree) for visual regression; XCUITest for full-flow UI tests on the simulator.
+
+**Read these other skills first:**
+- `cometchat-ios-core` — init, login, Secrets pattern
+- `cometchat-ios-components` — what each VC does (tests assert against this)
+- `cometchat-ios-calls/references/callkit-and-pushkit.md` — CallKit testing strategy (different from chat)
+
+**Ground truth:**
+- XCTest — https://developer.apple.com/documentation/xctest
+- SnapshotTesting — https://github.com/pointfreeco/swift-snapshot-testing
+
+---
+
+## 1. Test target structure
+
+A typical iOS project has three targets:
+
+| Target | When |
+|---|---|
+| `YourApp` | Production code |
+| `YourAppTests` | Unit + integration tests (XCTest) |
+| `YourAppUITests` | UI tests (XCUITest, runs on simulator) |
+
+The skill writes to `YourAppTests` for most assertions; `YourAppUITests` for full flows.
+
+---
+
+## 2. Mocking the SDK via protocols
+
+The CometChat SDKs are class-based with static methods (`CometChat.init`, `CometChat.login`). Hard to mock directly. **Wrap them in protocols you own:**
+
+```swift
+// Protocols/CometChatService.swift
+import CometChatSDK
+
+protocol CometChatServiceProtocol {
+  func initialize(appId: String, region: String) async throws
+  func login(uid: String, authKey: String) async throws -> User
+  func logout() async throws
+  func getLoggedInUser() -> User?
+  func sendMessage(_ message: TextMessage) async throws -> TextMessage
+}
+
+// Production implementation
+final class CometChatService: CometChatServiceProtocol {
+  func initialize(appId: String, region: String) async throws {
+    try await withCheckedThrowingContinuation { (cont: CheckedContinuation<Void, Error>) in
+      let settings = AppSettings.AppSettingsBuilder()
+        .subscribePresenceForAllUsers()
+        .setRegion(region: region)
+        .build()
+      CometChat.init(appId: appId, appSettings: settings) { isInitialized, error in
+        if let error = error { cont.resume(throwing: error) } else { cont.resume() }
+      }
+    }
+  }
+
+  func login(uid: String, authKey: String) async throws -> User {
+    try await withCheckedThrowingContinuation { (cont: CheckedContinuation<User, Error>) in
+      CometChat.login(UID: uid, apiKey: authKey, onSuccess: { cont.resume(returning: $0) },
+                      onError: { cont.resume(throwing: $0) })
+    }
+  }
+
+  // ... etc
+}
+```
+
+Inject the protocol via DI:
+
+```swift
+final class ChatViewController: UIViewController {
+  private let service: CometChatServiceProtocol
+
+  init(service: CometChatServiceProtocol = CometChatService()) {
+    self.service = service
+    super.init(nibName: nil, bundle: nil)
+  }
+  required init?(coder: NSCoder) { fatalError() }
+}
+```
+
+Test with a mock:
+
+```swift
+// Tests/CometChatServiceMock.swift
+final class CometChatServiceMock: CometChatServiceProtocol {
+  var initializeCallCount = 0
+  var initializeError: Error?
+  var loginUser: User?
+  var loginError: Error?
+
+  func initialize(appId: String, region: String) async throws {
+    initializeCallCount += 1
+    if let error = initializeError { throw error }
+  }
+
+  func login(uid: String, authKey: String) async throws -> User {
+    if let error = loginError { throw error }
+    return loginUser ?? User(uid: uid, name: "Test User")
+  }
+
+  func logout() async throws {}
+  func getLoggedInUser() -> User? { loginUser }
+  func sendMessage(_ message: TextMessage) async throws -> TextMessage { message }
+}
+```
+
+---
+
+## 3. XCTest patterns
+
+### Async/await tests
+
+```swift
+import XCTest
+@testable import YourApp
+
+final class ChatViewControllerTests: XCTestCase {
+  func testInitializeRunsBeforeLogin() async throws {
+    let mock = CometChatServiceMock()
+    let vc = ChatViewController(service: mock)
+
+    await vc.bootstrapCometChat()
+
+    XCTAssertEqual(mock.initializeCallCount, 1)
+    XCTAssertNotNil(vc.currentUser)
+  }
+
+  func testLoginFailureSurfacesError() async throws {
+    let mock = CometChatServiceMock()
+    mock.loginError = NSError(domain: "Test", code: 401, userInfo: [NSLocalizedDescriptionKey: "Unauthorized"])
+
+    let vc = ChatViewController(service: mock)
+    await vc.bootstrapCometChat()
+
+    XCTAssertEqual(vc.errorMessage, "Unauthorized")
+    XCTAssertEqual(vc.errorLabel?.textColor, .red)            // skill rule: error UI must be visible
+  }
+}
+```
+
+### Expectation-based tests (legacy / non-async code)
+
+```swift
+func testMessageSendFiresCallback() {
+  let expectation = expectation(description: "message sent")
+
+  let mock = CometChatServiceMock()
+  let vc = ChatViewController(service: mock)
+  vc.send(message: "Hello") { _ in
+    expectation.fulfill()
+  }
+
+  wait(for: [expectation], timeout: 1.0)
+}
+```
+
+For SDK callback-based code, prefer wrapping in protocol + async/await per Section 2; this pattern is for legacy code only.
+
+---
+
+## 4. SwiftUI view tests
+
+```swift
+import SwiftUI
+import XCTest
+@testable import YourApp
+
+@MainActor
+final class ProfileViewTests: XCTestCase {
+  func testCallButtonInvokesService() throws {
+    let mock = CallServiceMock()
+    let view = ProfileView(user: testUser(), callService: mock)
+
+    let host = UIHostingController(rootView: view)
+    host.loadViewIfNeeded()
+
+    // Hard to interact with SwiftUI views from XCTest directly — use ViewInspector or UI tests
+    // For most behavioral tests, prefer XCUITest (Section 6)
+  }
+}
+```
+
+Pure SwiftUI testing is hard; pragmatic choice is to keep most tests at the service / view-model layer and put view assertions in UI tests.
+
+### ViewInspector (third-party)
+
+For SwiftUI views you do want to inspect from XCTest, install `ViewInspector`:
+
+```swift
+import ViewInspector
+
+func testProfileShowsUserName() throws {
+  let user = testUser()
+  let view = ProfileView(user: user)
+  let text = try view.inspect().find(text: user.name)
+  XCTAssertNotNil(text)
+}
+```
+
+Adds a runtime dep. Not strictly necessary if you have UI tests.
+
+---
+
+## 5. Snapshot testing
+
+```bash
+# Package.swift dependency
+.package(url: "https://github.com/pointfreeco/swift-snapshot-testing.git", from: "1.15.0")
+```
+
+```swift
+import SnapshotTesting
+import XCTest
+@testable import YourApp
+
+final class ChatViewSnapshotTests: XCTestCase {
+  func testEmptyChatView() {
+    let view = ChatView(messages: [])
+    let host = UIHostingController(rootView: view)
+    assertSnapshot(matching: host, as: .image(on: .iPhone13))
+  }
+
+  func testChatViewWithMessages() {
+    let messages = [
+      TextMessage(text: "Hi", senderUid: "alice"),
+      TextMessage(text: "Hey", senderUid: "bob"),
+    ]
+    let view = ChatView(messages: messages)
+    let host = UIHostingController(rootView: view)
+    assertSnapshot(matching: host, as: .image(on: .iPhone13))
+  }
+}
+```
+
+First run creates the reference image; subsequent runs diff against it. Commit the `__Snapshots__` directory.
+
+**Gotcha:** snapshot tests are sensitive to font rendering — if CI uses a different macOS version than dev, snapshots won't match. Pin runners to a known version.
+
+---
+
+## 6. UI tests (XCUITest)
+
+```swift
+import XCTest
+
+final class ChatUITests: XCTestCase {
+  override func setUp() {
+    continueAfterFailure = false
+    let app = XCUIApplication()
+    app.launchEnvironment["UI_TEST_MODE"] = "1"
+    app.launchEnvironment["TEST_UID"] = "cometchat-uid-1"
+    app.launch()
+  }
+
+  func testLoginAndSeeConversations() {
+    let app = XCUIApplication()
+    XCTAssertTrue(app.staticTexts["Welcome"].waitForExistence(timeout: 10))
+    app.buttons["Messages"].tap()
+    XCTAssertTrue(app.staticTexts["Conversations"].waitForExistence(timeout: 10))
+  }
+
+  func testSendMessage() {
+    let app = XCUIApplication()
+    app.buttons["Messages"].tap()
+    app.buttons["cometchat-uid-2"].tap()
+
+    let composer = app.textFields["Type a message"]
+    composer.tap()
+    composer.typeText("Hello from UI test")
+    app.buttons["Send"].tap()
+
+    XCTAssertTrue(app.staticTexts["Hello from UI test"].waitForExistence(timeout: 5))
+  }
+}
+```
+
+**`UI_TEST_MODE` flag:** in production code, check this env var and skip animations / use shorter timeouts:
+
+```swift
+if ProcessInfo.processInfo.environment["UI_TEST_MODE"] == "1" {
+  UIView.setAnimationsEnabled(false)
+}
+```
+
+**Test users:** UI tests need real login. Use the dev `cometchat-uid-1` through `cometchat-uid-5`; never use production credentials.
+
+---
+
+## 7. CI configuration
+
+### GitHub Actions
+
+```yaml
+name: tests
+on: [push, pull_request]
+
+jobs:
+  unit:
+    runs-on: macos-13                              # pin macOS version for snapshot stability
+    steps:
+      - uses: actions/checkout@v4
+      - run: |
+          xcodebuild test \
+            -scheme YourApp \
+            -destination "platform=iOS Simulator,name=iPhone 15,OS=17.0" \
+            -only-testing:YourAppTests \
+            COMETCHAT_TEST_APP_ID="${{ secrets.TEST_COMETCHAT_APP_ID }}" \
+            COMETCHAT_TEST_REGION="${{ secrets.TEST_COMETCHAT_REGION }}" \
+            COMETCHAT_TEST_AUTH_KEY="${{ secrets.TEST_COMETCHAT_AUTH_KEY }}"
+
+  ui:
+    runs-on: macos-13
+    needs: unit
+    steps:
+      - uses: actions/checkout@v4
+      - run: |
+          xcodebuild test \
+            -scheme YourApp \
+            -destination "platform=iOS Simulator,name=iPhone 15,OS=17.0" \
+            -only-testing:YourAppUITests \
+            COMETCHAT_TEST_APP_ID="${{ secrets.TEST_COMETCHAT_APP_ID }}"
+```
+
+### Xcode Cloud
+
+Configure in App Store Connect → Xcode Cloud. Use the same env var convention; Xcode Cloud injects them into `xcodebuild` automatically.
+
+---
+
+## 8. Anti-patterns
+
+1. **Mocking CometChat directly** (without the protocol wrapper). The static methods aren't swappable; you'd need OCMock and method swizzling. The protocol wrapper is cleaner.
+2. **Using real WebSocket connections** in unit tests. They're flaky on CI. Mock the service layer.
+3. **Snapshot tests on a Mac with system font preference different from CI.** Pin macOS + Xcode versions.
+4. **Hardcoding `cometchat-uid-1` strings** across many tests. Centralize via a `TestUsers` enum so renames are one-edit.
+5. **Skipping `continueAfterFailure = false`** in UI tests. Default UI tests continue running after a failure, hiding root causes in cascade failures.
+6. **Storing test credentials in `Secrets.swift`.** Use env vars passed via `xcodebuild` and read via `ProcessInfo.processInfo.environment["..."]` in test bundles only.
+
+## 9. Verification checklist
+
+- [ ] `CometChatServiceProtocol` (or similar) wrapping the SDK; production VCs use it via DI
+- [ ] Mock implementation in `Tests/Mocks/`
+- [ ] At least one test for "init resolves before VC is functional"
+- [ ] At least one test for "error UI shows on init/login failure"
+- [ ] Snapshot tests for at least the empty + populated states of chat surfaces
+- [ ] At least one UI test for login + see conversations
+- [ ] Test target uses dedicated CometChat test App ID via env vars (not Secrets.swift)
+- [ ] CI pinned to macOS + Xcode versions
+- [ ] No `continueAfterFailure = true` in UI tests
+
+## 10. Pointers
+
+- `cometchat-ios-calls/references/callkit-and-pushkit.md` — calls + CallKit testing
+- `cometchat-ios-core` — init, login, Secrets patterns the tests assert against
+- `cometchat-ios-troubleshooting` — when tests pass but production breaks

package/skills/cometchat-ios-theming/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-theming
 description: "Customize the look and feel of CometChat iOS UI Kit — colors, fonts, styles, and dark mode support."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"

package/skills/cometchat-ios-troubleshooting/SKILL.md

@@ -3,7 +3,7 @@ name: cometchat-ios-troubleshooting
 description: "Diagnose and fix common CometChat iOS integration issues — build errors, runtime errors, and debugging techniques."
 license: "MIT"
 compatibility: "CometChatUIKitSwift ^5; iOS 13+"
-allowed-tools: "executeBash, readFile, fileSearch, listDirectory"
+allowed-tools: "shell, file-read, file-search, file-list"
 metadata:
   author: "CometChat"
   version: "3.0.0"