What Changed When the Same Kata Needed a UI
说明与用途
在 Hangman 任务中添加强制 UI 要求,使代理探索更广泛的模块组合,产生不同的 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"
- 记录日期: 2026-09-17T21:00:22.328Z