What Changed When the Same Kata Needed a UI

Описание и применение

Добавление обязательного пользовательского интерфейса в задачу Hangman заставило агента выбирать более широкий набор модулей, приводя к разным реализациям UI (Spring Boot/Thymeleaf и TypeScript/React), при этом сохраняя функциональную корректность. Seed4J CLI обеспечил прозрачное обнаружение и планирование, а эксперименты показали влияние специфичности подсказки на решения агента.

Задача

Assess how adding a mandatory UI requirement alters the behavior of a coding agent using Seed4J CLI for a Hangman kata.

Результат

Adding a mandatory UI requirement caused agents to explore a broader set of modules, leading to distinct UI implementations (Spring Boot/Thymeleaf vs. TypeScript/React) while maintaining functional correctness. Seed4J CLI enabled transparent discovery and planning, and the experiments highlighted the impact of prompt specificity on agent decisions.

Рабочий процесс

• 1. Set up empty repo and run Codex to generate Java library.
• 2. Repeat with six Codex runs, varying prompts but same base.
• 3. Run first Hangman experiment with optional UI; capture outputs.
• 4. Modify SPEC.md and prompt to require UI; run second experiment.
• 5. Record module selections, plans, and preflight results.
• 6. Compare Seed4J effectiveness scores and final UI screenshots.
• 7. Analyze module choices and plan corrections.
• 8. Summarize findings on agent behavior under low collaboration.

Доказательства

All six implementations passed their shared functional checks.

Источник

Luna composed a Java application with Spring Boot and Thymeleaf. Terra and Sol both selected TypeScript, React and Vite.

Источник

Seed4J rejected the composition without changing the repository: "Preflight: INVALID Missing modules: init, java-base, logs-spy, spring-boot-mvc-empty"

Источник