flutter / genui

create-catalog-item takes a JSON Schema definition and generates the matching CatalogItem, data class, and widget class an app needs to add a new widget to genui's catalog. genui-helper is scoped to the genui repository itself: running its own tests, scaffolding new components inside it, and finding the project's own A2UI and Dart reference material. integrate-genui-firebase wires up a basic genui conversation against Firebase AI Logic, and is the only one of the three that needs an external account rather than just the Flutter SDK already installed.

This suits a Flutter developer already building on genui who wants an agent to generate catalog boilerplate or navigate the repository's own conventions — not someone looking to learn generative UI concepts from scratch, since none of the three skills teaches genui's actual ideas (A2UI, widget catalogs, data binding) on their own.

READ THE FULL ANALYSIS＋

genui itself is still experimental. The README calls the whole SDK "highly experimental" and says its API will change, sometimes drastically; that instability sits under all three skills equally, since two of them generate code against APIs the maintainers say are not yet stable.

Install is scoped to one sub-package. The skills live under packages/genui/skills/ in a monorepo that also ships genui_a2a, genai_primitives, and json_schema_builder as separate pub.dev packages, and the README's own install command only reaches this one folder — the other three packages have no skills of their own.