- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies layout errors in LLM-generated visual code such as SVG. The method first generates a layout skeleton and then the final code, using SFT to learn this process and RL to assign geometric penalties to the tokens of defective elements. The authors also propose an inference-time stepwise detect-and-rewrite mechanism to identify and locally fix layout errors during generation. Evaluation is mainly conducted on a custom 450-task benchmark, with additional tests on cross-format transfer and an existing PPT agent workflow.
Critical strengths
- I like the overall design of the method. The structured layout skeleton makes spatial constraints explicit and easy to verify, which naturally supports both inference-time correction and element-level reward assignment during RL. These components fit together quite well.
- The experimental improvements are substantial. The ablation against outcome-only GRPO supports the effectiveness of fine-grained geometric rewards, and the experiments within an existing agentic workflow provide further evidence of its practical value.
Critical weaknesses
- The evaluation relies heavily on a custom benchmark and author-defined geometric metrics. Although the paper includes some additional evaluations, the lack of validation on established benchmarks for related tasks makes it difficult to assess the generalizability of the reported improvements.
- The main experiments only compare against general-purpose LLMs, without comparisons to existing specialized methods for slide or SVG generation, including some cited in the paper. This makes it difficult to assess the method's performance relative to prior work.
Questions for authors
- Could the authors evaluate the method on an existing benchmark for visual code or layout generation? Any suitable benchmark would be helpful.
- Could the authors include comparisons with some existing specialized methods, particularly those already cited in the paper, such as IntroSVG, AeSlides, or GeoSVG-RL? Even one or two representative comparisons under the same evaluation setting would help establish the method's effectiveness relative to prior work.
- Table 21 provides an important ablation of training and inference-time correction, and I think it deserves more discussion in the main text. Also, could the authors clarify the inconsistent LQS results for Qwen3.5-4B (base, two-stage) between Tables 10 and 17 (12.6 vs. 13.8)?
Response to Reviewer 3
Thank you for recognizing the value of our framework and its effectiveness in an agentic workflow. We address the evaluation setting, specialized methods, and the two table-related questions below.
Critical Weakness 1 / Question 1: Use of established benchmarks
The original tasks in existing SVG, webpage, and slide benchmarks are not always fully compatible with ours. Our task is to generate dense, content-complete visual pages from text across multiple code formats. Some benchmarks, for example, take images as input or focus on vector illustrations, whereas we assess whether specified content is delivered in a layout that satisfies spatial constraints. Directly comparing published scores would therefore conflate different inputs and outputs.
Nevertheless, we have made as much use of existing benchmarks as our unified setting allows. Our 450 evaluation tasks include examples from Design2Code, WebCode2M, PPTAgent, Slide2Code, Zenodo10K, and pptx_templates. We reformulated them as a common text-to-page task and generated each in the target formats. We also applied selected PPTEval-style and WebGen-Bench-style evaluation criteria to the outputs. Our main measures—overlap, spacing violations, misalignment, text overflow, out-of-bounds elements, content coverage, and delivery—capture layout issues shared across these applications. Thus, our evaluation draws extensively on existing data and evaluation methods. We will also clarify that reformulating these tasks is not equivalent to running any one benchmark under its complete original protocol.
To further test generalization under an unchanged public protocol, we have prepared the VGBench/VGen text-to-SVG prompts and a fixed pilot manifest. We will report its official metrics alongside our layout and delivery measures.
Critical Weakness 2 / Question 2: Comparisons with specialized methods
Our existing ablation already addresses part of this methodological comparison. AeSlides uses composite criteria to score a completed slide and a GRPO-family method to optimize a page-level outcome reward. Our outcome-only GRPO arm examines a similar reward granularity in our task. With the model, training data, and outcome term held constant, adding our element-to-token reward raises SVG end-to-end delivery from 77.1% to 88.0% and reduces overlap from 0.07 to 0.02 per page. This controlled ablation supports the value of localized geometric feedback and can also be viewed as an ablation analogous to the AeSlides approach.
In addition, the outputs of IntroSVG may be more oriented toward illustrative graphics than toward layout tasks like ours. The different styles of the resulting artifacts lead to different priorities in training and evaluation, which is why we did not fully follow its setup. GeoSVG-RL focuses on technical diagrams with connector and graph constraints, unlike our dense, content-bearing pages. These task differences explain why we did not directly juxtapose their published scores with ours.
In follow-up work, we will draw on ideas from IntroSVG and GeoSVG-RL and implement them, where feasible, as ablations in our experimental setting.
Question 3a: Why is Table 21 in the appendix, and what does it show?
Thank you for highlighting Table 21. Due to main-text space constraints, we placed the full training stage × inference strategy × feedback strategy ablation in the appendix. We agree that its main conclusions deserve more discussion in the main text. This ablation helps assess whether the gains in the trained models merely result from using more steps and tokens. In particular, adding a further stepwise detect-and-rewrite round after two-stage generation with the trained models does not yield a clear additional gain, suggesting that the inference paradigm matters beyond simply increasing inference cost. We will expand the main-text discussion of these findings.
Question 3b: Why do Tables 10 and 17 report different LQS values?
Thank you for catching this inconsistency. For the Qwen3.5-4B base model with two-stage inference, 12.6% is the correct value, matching the archived aggregate score report and Table 10. The 13.8% entry in Table 17 was an oversight when we filled the table. We will correct Table 17 to 12.6% and check the related text and tables for consistency.