integrate-genui-firebase

Utilisez cette compétence lorsque l'utilisateur demande d'intégrer le package genui et de démarrer une conversation simple avec Firebase AI Logic.

npx skills add https://github.com/flutter/genui --skill integrate-genui-firebase

Integrate GenUI with Firebase AI Logic

Goal

To successfully integrate the genui package into a Flutter app and set up a basic conversational agent using Firebase AI Logic. This skill assumes Firebase AI Logic is already set up and working in the project.

Instructions

When tasked with integrating genui and starting a simple conversation, follow these steps:

  1. Verify Firebase Setup: Ensure firebase_core and firebase_ai are available in pubspec.yaml. Verify that Firebase.initializeApp is called in the main() function:

    WidgetsFlutterBinding.ensureInitialized();
    await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);
    
  2. Add GenUI Package: Add genui to the pubspec.yaml dependencies.

  3. Import Required Libraries: Import genui and hide TextPart so it doesn't conflict with other packages, then import it again with an alias:

    import 'package:genui/genui.dart' hide TextPart;
    import 'package:genui/genui.dart' as genui;
    
  4. Configure Basic Logging: At the beginning of the main() function, configure GenUI logging:

    configureLogging(
      logCallback: (level, msg) => debugPrint('GenUI $level: $msg'),
    );
    
  5. Create Model and Chat Session: Initialize the generative model and start a chat session.

    final model = FirebaseAI.googleAI().generativeModel(
      model: 'gemini-3-flash-preview',
    );
    final _chatSession = model.startChat();
    
  6. Identify Target StatefulWidget: STOP AND ASK THE USER IF UNCLEAR: This integration requires a StatefulWidget to hold the references to GenUI controllers (SurfaceController, A2uiTransportAdapter, and Conversation). Identify which StatefulWidget to use in the application. If you are unsure which widget should hold this state, ask the user before proceeding.

  7. Wire up GenUI Controllers inside State: Inside your identified State class, instantiate SurfaceController, A2uiTransportAdapter, and Conversation:

    final catalog = BasicCatalogItems.asCatalog(); // Optionally inject custom CatalogItems
    final _controller = SurfaceController(catalogs: [catalog]);
    final _transport = A2uiTransportAdapter(onSend: _sendAndReceive);
    final _conversation = Conversation(
      controller: _controller,
      transport: _transport,
    );
    
  8. Implement the _sendAndReceive Method: Create a method to take messages from the transport adapter, send them to Firebase, and feed the AI's response back to the transport.

    Future<void> _sendAndReceive(ChatMessage msg) async {
      final buffer = StringBuffer();
    
      for (final part in msg.parts) {
        if (part.isUiInteractionPart) {
          buffer.write(part.asUiInteractionPart!.interaction);
        } else if (part is genui.TextPart) {
          buffer.write(part.text);
        }
      }
    
      if (buffer.isEmpty) return;
    
      final text = buffer.toString();
      final response = await _chatSession.sendMessage(Content.text(text));
    
      if (response.text?.isNotEmpty ?? false) {
        _transport.addChunk(response.text!);
      }
    }
    
  9. Listen to Conversation Events: Create stubbed-out methods in your State class for each event type, including DartDoc comments explaining their required behavior. Depending on the interface design, new surfaces and text coming from the agent will be handled in different ways. A conversational interface might add everything to a list that's display in a ListView, for example, while an interface featuring UI components in specific locations (such as headers, footers, etc.) might rely on specific surface IDs given to the agent in the system instruction to know which surfaces to display in which locations.

    /// Updates state to include the new [surfaceId] so a new `Surface` widget can be built.
    void _onSurfaceAdded(String surfaceId) {
      // TODO: Implement state update to add surfaceId
    }
    
    /// Updates state to remove the [surfaceId] so its `Surface` widget is no longer built.
    void _onSurfaceRemoved(String surfaceId) {
      // TODO: Implement state update to remove surfaceId
    }
    
    /// Handles displaying raw text content received from the AI to the user.
    void _onContentReceived(String text) {
      // TODO: Implement displaying the received text
    }
    
    /// Handles errors that occur during the conversation appropriately.
    void _onError(Object error) {
      // TODO: Implement error handling
    }
    

    Subscribe to _conversation.events to track when UI surfaces or chat messages arrive, dispatching them to the appropriate stubbed out methods:

    _conversation.events.listen((event) {
      switch (event) {
        case ConversationSurfaceAdded added:
          _onSurfaceAdded(added.surfaceId);
        case ConversationSurfaceRemoved removed:
          _onSurfaceRemoved(removed.surfaceId);
        case ConversationContentReceived content:
          _onContentReceived(content.text);
        case ConversationError error:
          _onError(error.error);
        default:
      }
    });
    
  10. Initialize System Prompt: Use PromptBuilder to give the AI basic instructions, then send it as a system message.

    final promptBuilder = PromptBuilder.chat(
      catalog: catalog,
      instructions: 'You are a helpful assistant. Respond to messages in a chatty way.',
    );
    _conversation.sendRequest(ChatMessage.system(promptBuilder.systemPrompt));
    
  11. Display Surfaces: In your Flutter build() method, use the Surface widget wherever you need to render GenUI widgets using the surfaceIds you collected in step 9.

    Surface(surfaceContext: _controller.contextFor(surfaceId));
    
  12. Ask User for Input Preferences: STOP AND ASK THE USER: Ask the user for clarification on what UI elements should be used for user input. Explain that a TextField and ElevatedButton are good defaults, but you should not assume they want those exact widgets unless they clarify.

Constraints

  • Do not make assumptions about user input UI elements; see step 12.
  • Make sure to properly clean up GenUI controllers (_transport.dispose(), _controller.dispose()) inside the widget's dispose() method.

Plus de skills de flutter

dart-modern-features
flutter
Pour trouver des candidats à la modernisation :
flutter-fix-layout-issues
flutter
Corrige les erreurs de mise en page Flutter (débordements, contraintes illimitées) à l'aide des outils Dart et Flutter MCP. À utiliser pour résoudre les messages « RenderFlex overflowed », « Vertical…
adding-release-notes
flutter
Ajoute des descriptions de changements destinés aux utilisateurs dans les notes de version de DevTools. À utiliser pour documenter les améliorations, correctifs ou nouvelles fonctionnalités dans le fichier NEXT_RELEASE_NOTES.md.
reviewing-devtools-prs
flutter
Workflow de revue de PR spécifique au dépôt DevTools, appliquant les directives de style DevTools et les modèles de revue courants. À utiliser lors de la revue de pull requests dans le…
dart-use-primary-constructors
flutter
Aider les utilisateurs à écrire des constructeurs principaux syntaxiquement et sémantiquement corrects en Dart, et migrer/utiliser la nouvelle syntaxe de constructeur, la syntaxe de point-virgule à corps vide,…
code-documentation
flutter
Guide pour rédiger une documentation de code efficace, incluant les docstrings, JSDoc, dartdoc et les commentaires d'implémentation. Utilisez cette compétence lors de l'écriture de nouveau code, de l'ajout…
api-review
flutter
Examine le code spécifié par rapport aux directives canoniques de conception d'API. Utilisez cette compétence lorsque l'utilisateur demande une revue d'API ou souhaite vérifier que le code respecte la conception d'API…
flutter-accessibility
flutter
Implémente les normes d'accessibilité WCAG 2 et EN 301 549 ainsi que les mises en page adaptatives dans les applications Flutter. Applique les annotations sémantiques, les tailles de cible tactile (48x48 dp minimum) et les ratios de contraste de texte (4,5:1 pour le petit texte, 3:1 pour le grand texte) sur les plateformes mobiles, web et de bureau. Fournit une logique décisionnelle pour l'initialisation de la sémantique web, l'encapsulation de widgets interactifs, le changement de mise en page basé sur la taille d'écran et la gestion des entrées clavier/souris. Inclut la gestion du parcours de focus via FocusTraversalGroup et...