
Genui Helper
- 77 installs
- 1.7k repo stars
- Updated August 4, 2026
- flutter/genui
Provide GenUI repository workflows for running tests and fixes, creating A2UI-compliant components, and following repo documentation standards.
About
A development helper for the genui repository covering its test-and-fix tooling, component creation conventions, and documentation standards. A developer uses it when working inside the genui repo to run the custom test_and_fix tool, create UiComponent-based components, or update docs.
- Runs tool/test_and_fix which applies dart fix, format, and flutter test
- Components extend UiComponent and must match the A2UI specification
Genui Helper by the numbers
- 77 all-time installs (skills.sh)
- Ranked #5,386 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/flutter/genui --skill genui-helperAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 77 |
|---|---|
| repo stars | ★ 1.7k |
| Last updated | August 4, 2026 |
| Repository | flutter/genui ↗ |
What it does
Provide GenUI repository workflows for running tests and fixes, creating A2UI-compliant components, and following repo documentation standards.
Files
GenUI Development Helper
This skill provides workflows and best practices specific to the genui repository.
Workflows
1. Running Tests and Fixes
The repository uses a custom tool to run tests, apply fixes, and format code before committing. It should typically only be run before committing, since it is inefficient and slow to run it on every change.
It will run dart fix --apply, dart format, and flutter test on all packages in the repository.
Command:
dart run tool/test_and_fix/bin/test_and_fix.dartWhen to use:
- Before committing changes, to ensure project health.
- Instead of running
flutter testmanually for each project in the repo.
2. Creating a New Component in the genui package
When creating a new UI component in genui:
1. Location: Place component files in packages/genui/lib/src/components/. 2. Inheritance: Components must extend UiComponent. 3. A2UI Compliance: Ensure the component matches the A2UI specification. 4. Documentation: Follow strict Dart documentation standards.
3. Updating Documentation
- Documentation source of truth is in
docs/. - Use
mkdocscontext if mentioned, but primarily edit the markdown files directly. - Ensure strict adherence to "Natural Writing" standards (no AI-isms).
Key Constants & Patterns
- Current A2UI Version: v0.9
- State Management: Uses
SurfaceControllerfromgenui.
References
- A2UI Specification
- Available in the submodule at @submodules/a2ui
- The specification documentation is available in @submodules/a2ui/specification/v0.9/docs
- The specification schemas are available in @submodules/a2ui/specification/v0.9/json
- Because it is a submodule, you may need to update the submodule to get the latest specification.
- To find out details of a specific dart compiler diagnostic message, use the following url format to look up the details:
- https://dart.dev/tools/diagnostics/<message_id>
- Example: https://dart.dev/tools/diagnostics/ambiguous_import
- To find out details of a specific analyzer lint message, use the following url format to look up the details:
- https://dart.dev/tools/linter-rules/<lint_rule_id>
- Example: https://dart.dev/tools/linter-rules/always_declare_return_types