mcpbeat Sign in

Integrate Genui Firebase Agent Skill

Use this skill when the user asks to integrate the genui package and get a simple conversation going with Firebase AI Logic.

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1734
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/flutter/genui --skill integrate-genui-firebase

The instruction itself

4 sections, as written by the author

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:

  • 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);
  • Add GenUI Package:

Add genui to the pubspec.yaml dependencies.

  • 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;
  • Configure Basic Logging:

At the beginning of the main() function, configure GenUI logging:

   configureLogging(
     logCallback: (level, msg) => debugPrint('GenUI $level: $msg'),
   );
  • 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();
  • 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.

  • 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,
   );
  • 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!);
     }
   }
  • 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.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Skill Creator
by vercel-labs
vendor ×10

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

12k tokens scripts
Skill Creator
by JayZeeDesign
×9

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

10k tokens scripts
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Dispatching Parallel Agents
by ZhanlinCui
×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

2k tokens
Skill Development
by anthropics
vendor ×4

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

9k tokens
Find Skills
by sanity-io
vendor ×4

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

1k tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take flutter/integrate-genui-firebase from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.