Update GEMINI instructions for catalog items, add implementation descriptions.#31
Merged
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request adds two new implementation documents, one for the travel app example and one for the flutter_genui package. The documentation provides a good overview of the architecture and implementation details. My feedback includes a suggestion to update a link to point to the more detailed implementation file and a recommendation to standardize the list formatting in the markdown for better readability and consistency.
polina-c
reviewed
Aug 1, 2025
| @@ -3,26 +3,28 @@ | |||
| A CatalogItem is an object which represents a widget that can be instantiated by an LLM. It centralizes the builder function for the widget along with the data schema and name. | |||
Collaborator
There was a problem hiding this comment.
may I ask you to add README.md to the folder .gemini with summary what it is for and link to documentation?
Collaborator
Author
There was a problem hiding this comment.
Sure, no problem.
Update GEMINI instructions for catalog items Add README.md for .gemini directory.
This was referenced Oct 25, 2025
sethgw
added a commit
to layups-ai/genui
that referenced
this pull request
Jul 8, 2026
- Bump protocol version to v1.0 in message envelopes and capabilities - Rename createSurface 'theme' to 'surfaceProperties'; support inline 'components' and 'dataModel' for single-message UI instantiation - Add CallFunctionMessage/ActionResponseMessage (server-to-client) and A2uiFunctionResponse (client-to-server) with actionId correlation - Add callableFrom execution boundaries with INVALID_FUNCTION_CALL rejection for remote calls to clientOnly/unregistered functions - Serialize catalog functions as a map keyed by name with static returnType/callableFrom metadata; move surfaceProperties under $defs - Remove wire-level returnType from FunctionCall payloads - Serialize explicit null in updateDataModel for key deletion - Add @index system function (with offset) scoped to template loops - Enforce UAX flutter#31 identifier rules for catalog entity names - Add optional catalog 'instructions' (replaces external rules text) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Just added a hint to use extension types for the data in catalog items, and added some files that outline the implementation of the travel app and the SDK package.