Teaches coding agents how to build TUIs with TamboUI correctly: API-level selection, render-thread discipline, display-width safety, CSS-aware element authoring, and JFR conventions.
94
93%
Does it follow best practices?
Impact
97%
2.77xAverage score across 3 eval scenarios
Passed
No known issues
TamboUI's library modules (tamboui-core, tamboui-widgets, tamboui-toolkit, tamboui-tui, the backends, etc.) target Java 8 source compatibility so they can run on any modern JVM, including embedded scenarios. Demos and tooling are free to use newer Java. Why: dropping Java 8 here would lock out users on long-LTS deployments without their consent — and the cost of staying on Java 8 in the library is small.
Optionaljava.util.function, java.time, Collectors, etc.)Collections.unmodifiable*, Arrays.asList, builder patternsvar (Java 10), text blocks (Java 15), record (Java 16), sealed classes (Java 17), pattern matching for instanceof and switchList.of, Map.of, Set.of (Java 9) — use Collections.unmodifiableList(Arrays.asList(...)) insteadjava.util.* API added after Java 8 (Stream.toList, String.lines, Files.mismatch, etc.)demos/ should use Java 21 idioms — pattern matching, records, switch expressions, var — they exist to showcase modern Javatamboui-processor module and build scripts can also use newer Java if useful./gradlew -q assemble will fail if a library module uses a too-new feature./gradlew -q javadoc must also pass before considering a change done — TamboUI treats javadoc warnings as errors