Cometchat Android V6 Compose Components logo

Cometchat Android V6 Compose Components

Organization
cometchat
cometchat-android-v6-compose-components

The closed catalog of CometChat Android v6 UI Kit components for the Jetpack Compose cohort — what exists, the composable import for each, the param shape (onX lambdas, hideX booleans, @Composable slots), and how to pass custom UI into a slot instead of stacking on top. Triggers: 'cometchat compose components', 'is there a X composable', 'cometchat jetpack compose list', 'custom row compose cometchat', 'swap the message bubble compose'.

Overview

Publishercometchat
Repositorycometchat-skills
Skill namecometchat-android-v6-compose-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 Android V6 Compose 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-android-v6-compose-components .claude/skills/cometchat-android-v6-compose-components
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cometchat Android V6 Compose 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 Android V6 Compose 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 Android V6 Compose 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.

Ground truth: catalog android-v6.json (287 symbols, from the INSTALLED 6.0.5 source, cross-checked against the published AAR). Param shapes below were read from the Compose source. Fetch anything else from docs (corereferences/docs-map.md); never trust memory.

⚠️ This is the Jetpack Compose cohort. Artifact chatuikit-compose-android, namespace com.cometchat.uikit.compose.presentation.*, components are composables configured by named params. The Views cohort (chatuikit-kotlin-android, setX(...) setters) is a separate skill — never install both.

Companion skills (read first)

  • cometchat-android-v6-core — install, credentials, initFromSettings → login → render, the fetch map. Assumed here, never repeated.
  • cometchat-android-v6-compose-placement — where these go · cometchat-android-v6-compose-customization — theming and slots.

Use this skill when

"which composables does the kit have?", "is there a <X> composable?", "what params does the conversations list take?", "can I replace a row / bubble region in Compose?".

Prerequisites & install

⚠️ Required on Compose too: configurations.all { exclude(group = "org.jetbrains", module = "annotations-java5") } plus android.useAndroidX=true + android.enableJetifier=true in gradle.properties. The collision arrives via chatuikit-core-android, which BOTH cohorts pull, so a Compose-only app fails its FIRST build without them (~40 Duplicate class errors). Full block: cometchat-android-v6-core §Prerequisites & install. implementation("com.cometchat:chatuikit-compose-android:6.0.5") + buildFeatures { compose = true } + the Kotlin Compose plugin. Same init/login gate as core.

Component catalog (closed list)

The component NAMES are identical to the Views cohort — only the wiring differs. Import pattern: com.cometchat.uikit.compose.presentation.<area>.ui.<Component>. Not listed ⇒ not in the catalog ⇒ does not exist.

⚠️ Three exceptions to that path (verified vs 6.0.6): the calling trio DOES carry .ui in Compose — …compose.presentation.callbuttons.ui.CometChatCallButtons — which is the OPPOSITE of the Views cohort, so do not carry the Views exception across. And the presentation.shared.* family drops .ui entirely: …presentation.shared.searchbox.CometChatSearchBox, …presentation.shared.baseelements.avatar.CometChatAvatar, …presentation.shared.toolbar.CometChatToolbar. CometChatScopeChange ships in Views only — there is no Compose composable for it.

Conversations & listsCometChatConversations · CometChatUsers · CometChatGroups · CometChatGroupMembers (+ row composables CometChatConversationListItem, CometChatUsersListItem, CometChatGroupMemberListItem, CometChatGroupsItem). MessagingCometChatMessageHeader · CometChatMessageList · CometChatMessageComposer · CometChatMessageBubble · CometChatThreadHeader · CometChatThreadScreen · CometChatMessageInformation · CometChatMessageOption · CometChatMessageComposerAction · CometChatReactionList · CometChatMessageReaction · CometChatFlagMessageDialog · CometChatTypingIndicator · CometChatReceipt/CometChatReceipts. Bubbles by typeCometChatTextBubble · CometChatImageBubble/CometChatImagesBubble · CometChatVideoBubble/CometChatVideosBubble · CometChatAudioBubble/CometChatAudiosBubble · CometChatVoiceNoteBubble · CometChatFileBubble/CometChatFilesBubble · CometChatPollBubble · CometChatStickerBubble · CometChatCardBubble · CometChatCollaborativeBubble · CometChatActionBubble · CometChatCallActionBubble · CometChatMeetCallBubble · CometChatDeleteBubble · CometChatAIAssistantBubble. CallingCometChatCallButtons · CometChatIncomingCall · CometChatOutgoingCall · CometChatOngoingCall · CometChatCallLogs · CometChatCallLogsListItem. Search, AI & notificationsCometChatSearch · CometChatSearchBox · CometChatAIAssistantChatHistory · CometChatAIConversationStarterView · CometChatAISmartRepliesView · CometChatAIConversationSummaryView · CometChatNotificationFeed. Composer add-ons & mediaCometChatStickerKeyboard · CometChatEmojiKeyboard · CometChatCreatePoll · CometChatAttachmentTray/CometChatAttachmentTile · CometChatMediaRecorder/CometChatInlineMediaRecorder/CometChatInlineAudioRecorder · CometChatAudioVisualizer/CometChatInlineAudioWaveform · CometChatRichTextToolbar · CometChatSuggestionList · CometChatImagePreview · CometChatImageViewerScreen · CometChatVideoViewerScreen. Building blocksCometChatAvatar · CometChatBadgeCount · CometChatStatusIndicator · CometChatDate · CometChatToolbar · CometChatDialog/CometChatConfirmDialog · CometChatPopupMenu · CometChatSnackBar · state views CometChatLoadingState/CometChatEmptyState/CometChatErrorState · shimmer CometChatShimmerBox/CometChatShimmerContainer. Non-visualCometChatUIKit · theming CometChatTheme/CometChatColorScheme/CometChatTypography · CometChatLocalize · CometChatSoundManager · events CometChatEvents + the *Event family · formatters CometChatTextFormatter/CometChatMentionsFormatter/CometChatRichTextFormatter.

⚠️ Emitting ANY calling component requires the calls artifact and "uiKit": { "enableCalling": true } in assets/cometchat-settings.json — otherwise it crashes on device while compiling fine (the compile gate cannot catch it). Full artifact/flag/result matrix: docs call-logs page. → cometchat-android-v6-calls.

Param shape — how a Compose component is configured

Three conventions, consistent across the cohort (verified vs 6.0.5):

  • onX lambdas for events — onItemClick: ((Conversation) -> Unit)?, onSearchClick: (() -> Unit)?, onBackPress: (() -> Unit)?, onItemLongClick, onError: ((CometChatException) -> Unit)?, onLoad, onEmpty, onSelection.
  • hideX booleans for affordances — hideSearchBox, hideToolbar, hideBackIcon, hideUserStatus, hideReceipts, hideDeleteOption, hideLoadingState, hideEmptyState, hideErrorState. (Views uses visibility setters; Compose hides.)
  • @Composable slots for custom UI — e.g. itemView, leadingView, subtitleView, trailingView, each (@Composable (Conversation, TypingIndicator?) -> Unit)?. Plus modifier: Modifier, style: CometChat<X>Style = …default(), and request-builder params (conversationsRequestBuilder).
kotlin
import com.cometchat.uikit.compose.presentation.conversations.ui.CometChatConversations

CometChatConversations(
    modifier = Modifier.fillMaxSize(),
    title = "Chats",
    onItemClick = { conversation -> /* navigate */ },
    onSearchClick = { /* open search route */ },
)

Size it to fill. The kit fills the box you give it — a wrap_content-equivalent (unbounded height, or a Column without weight) renders a sliver (core/references/layout.md).

Key param differences from the Views cohort

ConcernViewsCompose
thread scopesetParentMessageId(Long)parentMessageId: Long = -1 param on list AND composer
thread headersetParentMessage(BaseMessage)parentMessage: BaseMessage (required param)
search scopesetSearchIn(List<SearchScope>)searchScopes: List<SearchScope>
search targetsetUid / setGuiduid: String? / guid: String?
affordancesvisibility settershideX: Boolean
slotsViewHolder listeners@Composable lambdas
Everything else (user, group, onThreadRepliesClick: ((BaseMessage) -> Unit)?) matches by name.

Custom UI goes IN a slot, not on top

Pass a @Composable to the component's slot param (itemView, leadingView, subtitleView, trailingView), use options/addOptions for the long-press menu, and setBubbleFactories-equivalent factories for custom message TYPES. Never stack your own composable over a kit component, and never re-implement a list the kit ships. Detail: cometchat-android-v6-compose-customization.

⚠️ A slot with a DEFAULT implementation REPLACES it — CometChatMessageHeader auxiliaryView vs trailingView (verified vs installed 6.0.5 source + on device). The header's auxiliaryView substitutes the built-in DefaultAuxiliaryView, which is what HOSTS the voice/video call buttons — so putting a custom icon there silently removes them. Extra header icons belong in trailingView, a separate slot that keeps the auxiliary area (and its call buttons) intact. Use auxiliaryView only when you intend to REPLACE the call-button area (and re-render CometChatCallButtons yourself if you still want calling).

Group member permissions — the kit enforces them, don't re-implement

CometChatGroupMembers gates its own long-press menu (verified vs 6.0.5). Rely on it:

Logged-in userMenu opens onCannot act on
Owner (uid == group.owner)anyone but themselves
Admin (group.scope)participants, moderatorsother admins, owner
Moderatorparticipants onlymoderators, admins, owner
Participantnobodyeveryone

A moderator also cannot assign the admin role (disabled in the scope sheet). Scope strings: CometChatConstants.SCOPE_ADMIN / SCOPE_MODERATOR / SCOPE_PARTICIPANT. Never hand-roll these checks or hide the component behind your own role logic — you will drift from the kit.

⚠️ Reversed parameter order between the two ownership APIs: CometChat.updateGroupMemberScope(UID, GUID, scope, listener) but CometChat.transferGroupOwnership(GUID, UID, listener).

Components that do NOT exist in v6

No combined shell — CometChatConversationsWithMessages, CometChatUsersWithMessages, CometChatGroupsWithMessages, CometChatUI are v4-era. ⚠️ CometChatMessageTemplate is absent from the shipped 6.0.5 artifact (logged internally) — use bubble factories.

Common pitfalls

Mixing cohorts (Views artifact in a Compose app) · using a setX(...) setter on a composable · unbounded height (sliver) · showSearchBar-style thinking (Compose uses hideSearchBox) · overlaying instead of slotting · a custom header icon in CometChatMessageHeader auxiliaryView (replaces the call-button host — use trailingView) · emitting CometChatMessageTemplate · guessing a param instead of fetching the page's Compose tab.

Verify it works

Every composable you emitted is in the list above (Tier-1) and it compiles — ./gradlew :app:assembleDebug # in YOUR app (native-fence.mjs is a pack-repo gate, not installed by the CLI). On device: full-size render with the kit's own loading/empty state, slotted composables INSIDE the component.

Frequently asked questions

What does the Cometchat Android V6 Compose Components AI skill do?

The closed catalog of CometChat Android v6 UI Kit components for the Jetpack Compose cohort — what exists, the composable import for each, the param shape (onX lambdas, hideX booleans, @Composable slots), and how to pass custom UI into a slot instead of stacking on top. Triggers: 'cometchat compose components', 'is there a X composable', 'cometchat jetpack compose list', 'custom row compose cometchat', 'swap the message bubble compose'.

Why use Cometchat Android V6 Compose Components on TypingMind?

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

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

Which AI models can use Cometchat Android V6 Compose 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 Android V6 Compose Components?

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

Is the Cometchat Android V6 Compose 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 👇