Cometchat Ios Components logo

Cometchat Ios Components

Organization
cometchat
cometchat-ios-components

The CometChat iOS UI Kit component catalogue — what each component is for, its real API shape, and where custom UI goes. Use when picking or customising an individual component. Triggers: 'which cometchat component', 'customise the conversation row', 'add a custom view to the message list', 'ios component list'.

Overview

Publishercometchat
Repositorycometchat-skills
Skill namecometchat-ios-components
Stars
109
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
  • 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 Components AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. 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.
2

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-components .claude/skills/cometchat-ios-components
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cometchat Ios Components 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 Components 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 Components 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 owns install, credentials, init → login → render and the golden-path chat surface. This skill ADDS the per-component catalogue; it never restates core's setup. Fetch exact API via cometchat-ios-core/references/docs-map.md.

Use this skill when

Choosing a component, or customising one: "what shows the member list?", "put a badge on the conversation row", "swap the message bubble".

The catalogue (catalog-verified — nothing else exists)

ComponentFor
CometChatConversationsRecent-chats list · the usual entry point
CometChatMessageHeader · CometChatMessageList · CometChatCompactMessageComposerThe chat screen — you compose these three yourself
CometChatUsers · CometChatGroups · CometChatGroupMembersPickers and rosters
CometChatSearchGlobal search over conversations and messages
CometChatThreadedMessageHeaderThread parent header
CometChatCallButtons · CometChatIncomingCall · CometChatOngoingCall · CometChatCallLogsCalling → cometchat-ios-calls
CometChatAvatar · CometChatBadge · CometChatStatusIndicator · CometChatDate · CometChatReceiptBase building blocks
CometChatMessageInformation · CometChatAIAssistanceChatHistoryPer-message detail · AI history
CometChatScopeChangeChange a member's role. set(group:groupMember:), options: [(String, CometChat.MemberScope)] (property). PRESENT it as a sheet — its Cancel calls dismiss(), so pushing it strands the user. CometChatGroupMembers already presents it on row tap.

There is NO composite component. CometChatMessages, CometChat{Users,Groups,Conversations}WithMessages, CometChatAddMembers, CometChatMessageHeaderOption are v4 or non-existent — never emit them. If a symbol is not in catalogs/ios-v5.json, it does not exist in v5, whatever a page says.

Three API shapes — get this right or nothing compiles

  1. Setters return Self and are chainable: set(user:), set(onItemClick:), set(subtitle:).
  2. Properties are assigned: list.avatarStyle = …, conversations.onSearchClick = { … }, groups.onSelectedItemProceed = { … }.
  3. Named setterssetXxx(xxx:) with the label repeated: CometChatMessageInformation uses setSubtitle(subtitle:), setBubbleView(bubbleView:), setListItemView(listItemView:), setOnError(onError:). Writing them in shape-1 form (set(subtitle:)) does not compile on that component. Which is which is per component, and the kit is not consistentCometChatConversations has set(subtitleView:)/set(trailView:) while CometChatUsers and CometChatGroups have set(subtitle:)/set(trailingView:), and CometChatGroupMembers uses the Conversations spelling. Never generalise a name across components — fetch the component's .md twin.

Where custom UI goes — IN the component's slot, never beside it

Every list component exposes: set(listItemView:) (whole row) · set(leadingView:) · set(titleView:) · subtitle · trailing · set(options:) (swipe/overflow actions). Use these instead of building your own row above the list. Empty/error/loading are assignable views inherited from CometChatListBase: emptyStateView, errorStateView, loadingView, plus emptyStateTitleText / emptyStateSubTitleText to retitle the built-in one. CometChatSearch is the exception — it does NOT inherit CometChatListBase, so it has none of that chrome; it uses set(emptyView:) / set(errorView:) / set(loadingView:) instead.

Gotchas

  • set(controller:) on any component that presents something (header, list, composer) or its built-in affordances render and do nothing.
  • CometChatAvatar — use setAvatar(avatarUrl:with:). set(image:) and init(image:) compile but render NOTHING. There is no set(user:). Measured on 5.1.19: an avatar given a UIImage through either set(image:) or init(image:) draws an empty circle — the image never appears, with no warning and no error, because the kit paints its own content over it. setAvatar(avatarUrl:with:) is the working path, and its with: name renders initials when no URL loads. There is also no no-arg init: CometChatAvatar() does not compile — construct with CometChatAvatar(image: nil) or CometChatAvatar(frame:) and then call setAvatar.
  • Search slots are per result TYPE: set(listItemViewForMessage:) plus …ForImage/Video/Audio/Document/Link/Conversation. There are no *ForMessage granular (title/subtitle/leading/trailing) slots — those exist for conversations only, as properties.

Verify it works

The component renders at full size, its custom slot appears in the right place (inside the row, not above the list), and every rendered control does something when tapped.

Frequently asked questions

What does the Cometchat Ios Components AI skill do?

The CometChat iOS UI Kit component catalogue — what each component is for, its real API shape, and where custom UI goes. Use when picking or customising an individual component. Triggers: 'which cometchat component', 'customise the conversation row', 'add a custom view to the message list', 'ios component list'.

Why use Cometchat Ios Components on TypingMind?

Because you install it once and use it with any model. Cometchat Ios Components 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 Components in TypingMind?

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

Which AI models can use Cometchat Ios Components?

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 Components?

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

Is the Cometchat Ios Components 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇