cometchat-flutter-v6-features

Ground truth: the feature-existence oracle is features.flutter-v6.json (pack root). A feature the user asks for MUST be an id there — if it is not listed, it does not exist; do not invent it. Exact dashboard steps come from the feature's docs_topic (dashboard paths rot — FETCH them). Widget names come from catalogs/flutter-v6.json.

Companion skills (read first)

• cometchat-flutter-v6-core — install, credentials, init→login→render. This skill ASSUMES it.
• cometchat-flutter-v6-components — the widget catalog features render through.

Use this skill when

The user wants to turn ON a capability: "add polls", "enable stickers", "turn on translation", "add smart replies", "add moderation", "enable an extension".

Prerequisites & install

Core done. Most features add NO package; voice-video-calls adds one (→ -calls), push adds Firebase (→ -push).

THE v6 RULE THAT CHANGES EVERYTHING

v6 deleted the entire v5 extension architecture. There is no UIKitSettings.extensions, no CometChatUIKitChatExtensions, no DataSource, no ChatConfigurator, no *ExtensionDecorator, no CometChatUIKit.getDataSource(). A dashboard-enabled extension surfaces automatically through MessageTemplateUtils — composer action sheet, message bubbles — with zero client registration code.

So for most extensions the correct answer is: flip the Dashboard toggle and write NO code. Emitting v5-style registration into a v6 app is a defect, not a harmless no-op. If the user already has such code, that is a migration problem (→ -migration).