AGENT SKILL

cometchat-android-v6-kotlin-customization

Make the CometChat Android v6 UI match your app in the Kotlin XML Views cohort — theming via CometChatTheme.DayNight attributes, per-component styles, message-bubble styling, ViewHolder view slots, state views, long-press and composer menu options, text formatters, custom message rendering with BubbleFactory, localization and sounds. Triggers: 'change cometchat colors android', 'brand the android chat ui', 'dark mode cometchat android xml', 'custom row in conversations', 'replace the empty state', 'add a message menu option', 'custom message type android'.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
cometchat-android-v6-kotlin-customization
license
MIT
metadata
{ "tags": "cometchat android customization theming styles v6 kotlin views dark-mode bubblefactory", "author": "CometChat", "version": "1.0.0" }
description
Make the CometChat Android v6 UI match your app in the Kotlin XML Views cohort — theming via CometChatTheme.DayNight attributes, per-component styles, message-bubble styling, ViewHolder view slots, state views, long-press and composer menu options, text formatters, custom message rendering with BubbleFactory, localization and sounds. Triggers: 'change cometchat colors android', 'brand the android chat ui', 'dark mode cometchat android xml', 'custom row in conversations', 'replace the empty state', 'add a message menu option', 'custom message type android'.
compatibility
Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 (XML Views cohort) — 6.1.x, verified 6.1.1; com.cometchat:chat-sdk-android ^5

03 SKILL.md 正文

Ground truth: catalog android-v6.json + the live Theming/Customization pages. Slot and style setters below were verified against the INSTALLED 6.0.5 source. Fetch exact token names from color-resources; never invent a token or a setter.

⚠️ Kotlin XML Views cohort — theming is XML theme attributes, slots are ViewHolder listeners. The Compose cohort (CometChatTheme {} + style data classes) is a separate skill.

Companion skills (read first)

  • cometchat-android-v6-core — install, credentials, init/login, the fetch map. Assumed here, never repeated.
  • cometchat-android-v6-kotlin-components — what exists; this skill changes how it looks/behaves.

Use this skill when

"match the chat to our brand", "use our fonts", "support dark mode", "restyle the conversation rows or bubbles", "replace the empty/loading/error view", "add an option to the message long-press menu", "render a custom message type", "highlight #hashtags", "translate the UI", "change notification sounds". Theming lives HERE — there is no separate theming skill.

Cloning a named app, or mixing kit components with your own UI? Measure the target's colors, type, spacing and radii into ONE token source, theme the kit from it, and style every custom component from the same tokens so kit and custom parts look like one design; host a kit component in your own dialog/panel when only its placement differs. Flow: cometchat-onboarding → references/clone-mode.md (Design sync, build levels L0–L6).

Customization mechanism map (pick the smallest one that does the job)

Intent Mechanism Docs page (fetch for exact names)
brand color, global look, light/dark Theme — extend CometChatTheme.DayNight theme-introduction
exact token names Color resources (cometchat* attrs) color-resources
fonts / text styles Typography (CometChatTextAppearance*) component-styling (NOT theme-introduction — it documents colours only)
restyle ONE component setStyle(@StyleRes) / setStyle(CometChat<X>Style) component-styling
bubble look per message type Message-bubble styling message-bubble-styling
replace a REGION of a row/bubble View slots (ViewHolder listeners / view providers) customization-view-slots
replace empty / error / loading setEmptyView / setErrorView / setLoadingView customization-state-views
long-press or composer actions setOptions / setAddOptions, CometChatMessageOption, CometChatMessageComposerAction customization-menu-options
custom message TYPE rendering BubbleFactory + setBubbleFactories see below — not the docs' message-template page
custom text patterns CometChatTextFormatter / CometChatMentionsFormatter / CometChatRichTextFormatter customization-text-formatters
change what a list fetches request builders + setViewModel(...) customization-viewmodel-data
translate the UI / locale CometChatLocalize localize
in-app sounds CometChatSoundManager sound-manager

Theming — the top mechanism (BAKED; the rest of the table is a FETCH)

Extend the kit theme, then apply it in the manifest:

<!-- app/src/main/res/values/themes.xml -->
<style name="AppTheme" parent="CometChatTheme.DayNight">
    <item name="cometchatPrimaryColor">#F76808</item>
</style>
<!-- AndroidManifest.xml: <application android:theme="@style/AppTheme" ...> -->

Programmatic equivalent: CometChatTheme.setPrimaryColor(Color.parseColor("#F76808")).

Brownfield — an app with its own design system NEVER re-parents its application theme. CometChatTheme.DayNight parents Theme.MaterialComponents.DayNight.NoActionBar; re-parenting a Material3 host breaks its own screens (Material3-only attrs stop resolving), while skipping the kit theme crashes kit inflation (unresolved ?attr/cometchat*). Keep the host theme and SCOPE the derived style to where kit views live: manifest android:theme on the chat Activities + ContextThemeWrapper for fragment/tab-embedded views — recipe: kotlin-placement Placement 2. App-wide re-parenting (above) is the greenfield path.

Dark mode — follow the system by default. Add res/values-night/themes.xml overriding the same attributes (cometchatPrimaryColor, cometchatBackgroundColor1, cometchatTextColorPrimary, ...); Android applies it automatically. A theme can also be scoped to one Activity (theme-introduction §"Apply a Theme to a Specific Activity"). Override only the tokens you actually brand so future kit versions stay consistent.

What's swappable — slots, verified against 6.0.5 and 6.1.1

Lists (CometChatConversations, and the same shape on CometChatUsers/CometChatGroups/CometChatGroupMembers): setItemView · setLeadingView · setTitleView · setSubtitleView · setTrailingView — each takes a ConversationsViewHolderListener (a createView/bindView pair), not a View. Plus setEmptyView/setErrorView/setLoadingView (plain View), setOptions/setAddOptions for the long-press menu, setOverflowMenu, and setConversationsRequestBuilder(...) to scope the data.

Message list — per-region providers, each a BubbleViewProvider: setLeadingViewProvider · setHeaderViewProvider · setContentViewProvider · setReplyViewProvider · setBottomViewProvider · setStatusInfoViewProvider · setThreadViewProvider · setFooterViewProvider. Warning: these compile but render nothing in 6.0.5 and 6.1.1: MessageAdapter stores the providers and never reads them (source: "stored but not used in the new architecture"; shipped AAR bytecode has no read of the field). The docs message-list page still teaches setLeadingViewProvider. Per-message slots that DO render: a BubbleFactory's createLeadingView/createHeaderView/... for its own category+type (below).

Avatar and sender name on every message (BAKED — verified vs 6.1.1 source + compiled)

What to check and why: cometchat-onboarding/references/clone-mode.md -> Message chrome. This is the Views how-to. Kit default: avatar only on INCOMING messages in a GROUP (MessageAdapter.showAvatar = false, showLeftBubbleGroupAvatar = true, showLeftBubbleUserAvatar = false); sender name only on incoming group messages. Your own messages and every 1:1 chat get neither. Do this whenever the target shows avatars/names (Slack, Discord, Teams); don't ask. Two calls cover own and others' messages in 1:1 and group chats:

import com.cometchat.uikit.core.constants.UIKitConstants
import com.cometchat.uikit.kotlin.presentation.messagelist.ui.CometChatMessageList

fun CometChatMessageList.showSenderOnEveryMessage() {
    setMessageAlignment(UIKitConstants.MessageListAlignment.LEFT_ALIGNED) // own messages render as "left", so the name shows
    showAvatar(true) // global override: avatar on every left row, 1:1 included (default: groups only)
}
  • LEFT_ALIGNED makes isHideName return false for every row, so the name shows in 1:1 too; showAvatar(true) (same as setHideAvatar(false)) sets the adapter's global avatar flag. Action and call rows stay centered with no avatar.
  • All rows now use the INCOMING bubble style. Style the name with senderNameTextColor / senderNameTextAppearance on the bubble style (message-bubble-styling).
  • Your own avatar/name design is not reachable on Views 6.0.5 or 6.1.1: the leading/header providers above are dead, and a BubbleFactory slot replaces every slot of that message type (content, time, receipts, reactions), so it isn't a per-message avatar hook for standard types. Say so (L4).
  • Once per run (avatar only on the first of consecutive messages) isn't reachable: no hook sees the previous message (L4).

Custom message types — BubbleFactory (NOT message templates)

class ContactBubbleFactory : BubbleFactory() {
    override fun getCategory(): String = CometChatConstants.CATEGORY_CUSTOM
    override fun getType(): String = "contact"
    override fun createContentView(context: Context): View = ContactCardView(context)
    override fun bindContentView(
        view: View, message: BaseMessage,
        alignment: UIKitConstants.MessageBubbleAlignment,
        holder: RecyclerView.ViewHolder?, position: Int
    ) { (view as ContactCardView).bind(message) }
}
messageList.setBubbleFactories(listOf(ContactBubbleFactory()))

createContentView() runs before the message is known (only the factory key is available); the message arrives in bindContentView(). Optional: createBubbleView/bindBubbleView (replace the whole bubble), createLeadingView, getBubbleStyle.

⚠️ The old v5 template API is absent from the shipped 6.0.5 and 6.1.1 artifacts — CometChatMessageTemplate, setTemplates, setType, setCategory, setBubbleView, setMessageReceipt do not compile (logged internally). The docs message-template page was corrected upstream (verified 2026-09-09): it is now "Message Bubble Factory" and teaches BubbleFactory. Use BubbleFactory.

The rule

Custom UI goes INSIDE the component — a slot, a state view, a menu option, a formatter, a bubble factory — never a hand-built row stacked over a kit list, never a forked component. If no slot exists for what's needed, fetch the component's .md twin before inventing UI; if there genuinely is no hook, say so rather than re-implementing the component.

Common pitfalls

Hardcoding hex per screen instead of theming once · inventing a token name (fetch color-resources) · styling only light mode (no values-night) · passing a View where a ViewHolderListener/BubbleViewProvider is required · stacking custom views on top of kit components · re-implementing a list to change one row · emitting CometChatMessageTemplate from the docs page · filtering data client-side instead of scoping the request builder.

Verify it works

Compile: ./gradlew :app:assembleDebug # in YOUR app (native-fence.mjs is a pack-repo gate, not installed by the CLI). On device: the brand color appears on kit surfaces; toggle system dark mode → the UI follows with readable contrast; a slotted view renders INSIDE its component; state views appear on empty/error/loading; a custom message type renders through its factory; a changed menu option shows on long-press.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

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.

★ 1.6k