cometchat-flutter-v6-patterns

Ground truth: the CometChat side is cometchat-flutter-v6-core; this skill only adds the DELTA for a given toolchain. Framework mechanics (go_router, riverpod, --dart-define) are baked Flutter knowledge, not kit API. Kit symbols come from the catalog.

Companion skills (read first)

• cometchat-flutter-v6-core — install, credentials, the settings asset, init→login→render. This skill ASSUMES it.
• cometchat-flutter-v6-placement — WHERE the surface goes; this skill is HOW it hooks into your app's plumbing.

Use this skill when

Wiring the kit into a specific project shape, or debugging "where does init go" / "the theme resets on navigation" / "my secrets are in git".

Prerequisites & install

Covered by core. No new package.

Navigation (BAKED — the delta per router)

The kit uses plain Navigator.push/pop internally and in every recipe, which works under all of these — you do not have to convert its recipes.

• Plain Navigator — nothing to do. Core's recipes are already this.
• go_router — register chat screens as routes and push with context.push('/chat/:uid'). The kit's own internal pops still work because go_router sits on the same Navigator. Put the init/login gate above the router (wrap MaterialApp.router's builder, or gate in redirect) so no chat route can build before login resolves.
• auto_route — same principle: an AutoRouteGuard that waits for login is the idiomatic gate.
• Calling adds one requirement: navigatorKey: CallNavigationContext.navigatorKey on MaterialApp (→ -calls). With go_router, pass the same key into the router config rather than creating a second one.