Cometchat Ios Migration

Organization

cometchat

cometchat-ios-migration

Upgrade an existing CometChat iOS integration from UI Kit v4 to v5 — composite components removed, theming replaced, properties renamed. Triggers: 'upgrade cometchat ios to v5', 'migrate from v4 uikit ios', 'CometChatConversationsWithMessages not found'.

Overview

Publisher	cometchat
Repository	`cometchat-skills`
Skill name	`cometchat-ios-migration`
Stars	109
Forks	2
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by cometchat on GitHub. Read the source before you install it.

Installation

Install the Cometchat Ios Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cometchat/cometchat-skills.git /tmp/cometchat-skills
mkdir -p .claude/skills
cp -r /tmp/cometchat-skills/skills/cometchat-ios-migration .claude/skills/cometchat-ios-migration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cometchat Ios Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cometchat Ios Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cometchat Ios Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Companion skills (read first)

cometchat-ios-core describes the v5 target state. This skill is the RECONCILIATION path to it. Build from the official guide — fetch /ui-kit/ios/upgrading-from-v4 via cometchat-ios-core/references/docs-map.md — then apply the deltas below.

Use this skill when

An existing v4 integration must move to v5, or a build breaks with cannot find 'CometChatConversationsWithMessages' in scope after an upgrade.

The one change that dominates the migration

v4's composite components are gone. CometChatMessages, CometChatUsersWithMessages, CometChatGroupsWithMessages, CometChatConversationsWithMessages do not exist in v5, and neither do the configuration objects that fed them (MessageHeaderConfiguration, MessageListConfiguration, MessageComposerConfiguration).

That is not a rename — it is an inversion of ownership. v4 gave you one screen that did everything; v5 gives you three components and expects you to own the screen and the navigation. Every place the old code pushed a composite becomes a view controller you write, composed per cometchat-ios-core's golden path, with its five layout rules applied.

Budget for this honestly: it is the bulk of the work, and it is a design change in the host app, not a search-and-replace.

Then the mechanical deltas

Theming was replaced. v4's theme objects give way to CometChatTheme's static colours plus per-component style objects. Re-derive the brand from the theme rather than porting v4 style code — cometchat-ios-customization.
Setter vs property split. Several v4 setters are v5 properties: styles (avatarStyle, badgeStyle, receiptStyle, statusIndicatorStyle, typingIndicatorStyle), onSearchClick, onSelectedItemProceed, the call-button click handlers.
Renames to expect: set(usersRequestBuilder:) → set(userRequestBuilder:) · set(subtitleView:) → set(subtitle:) and set(trailView:) → set(trailingView:) on Users/Groups only (Conversations and GroupMembers keep the old spelling) · set(sessionID:) → set(sessionId:) · set(callSettingBuilder:) → set(callSettingsBuilder:) · set(onDeclineClick:) → set(onCancelClick:) · set(parentMessage:) → set(parentMessageId:) on the list and composer, though the thread header still takes set(parentMessage:).
Dependencies. v5 is SPM-only (CocoaPods is winding down) and pins exactly: kit 5.1.22 / SDK 4.1.7 / Calls 5.0.3, all added by hand.

Method

Upgrade the dependency first and let the compiler enumerate the work — the errors are the migration checklist. Fix composites first (they cascade), then styling, then the renames. Do it additively: the host app's navigation, auth and design system stay theirs.

Gotchas

Never mix majors. A half-migrated project with both v4 and v5 symbols will not build.
Check every symbol against catalogs/ios-v5.json before porting it — if it is absent, it is gone, and a v5 doc page mentioning it is not evidence it exists.

Verify it works

The project builds with no v4 symbols remaining; every screen that was a composite is now a composed screen that renders full-size, keyboard-avoids and navigates back; theming looks intentional rather than half-ported.

Frequently asked questions

What does the Cometchat Ios Migration AI skill do?

Why use Cometchat Ios Migration on TypingMind?

Because you install it once and use it with any model. Cometchat Ios Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cometchat Ios Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cometchat/cometchat-skills/tree/main/skills/cometchat-ios-migration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cometchat Ios Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cometchat Ios Migration?

As many as you like. As long as a model supports skills, you can use Cometchat Ios Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cometchat Ios Migration AI skill free?

Yes. It is published on GitHub by cometchat under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Using Git Worktrees

obra

CommunityPopular

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Companion skills (read first)

Use this skill when

The one change that dominates the migration

Then the mechanical deltas

Method

Gotchas

Verify it works

Frequently asked questions

Related AI Skills

Set up your own AI workspace now