<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: rivi mizuiro</title>
    <description>The latest articles on DEV Community by rivi mizuiro (@rivi_mizuiro_147c9219f6d5).</description>
    <link>https://dev.to/rivi_mizuiro_147c9219f6d5</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2670287%2Fd72ace47-23dc-4789-b556-6eae51b8fa19.jpg</url>
      <title>DEV Community: rivi mizuiro</title>
      <link>https://dev.to/rivi_mizuiro_147c9219f6d5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rivi_mizuiro_147c9219f6d5"/>
    <language>en</language>
    <item>
      <title>The silent layout bug in AI-generated slides</title>
      <dc:creator>rivi mizuiro</dc:creator>
      <pubDate>Mon, 19 Jan 2026 02:13:31 +0000</pubDate>
      <link>https://dev.to/rivi_mizuiro_147c9219f6d5/the-silent-layout-bug-in-ai-generated-slides-2oml</link>
      <guid>https://dev.to/rivi_mizuiro_147c9219f6d5/the-silent-layout-bug-in-ai-generated-slides-2oml</guid>
      <description>&lt;p&gt;I often generate slides by summarizing documents or PDFs.&lt;/p&gt;

&lt;p&gt;The workflow itself is convenient, but I kept running into the same issue:&lt;br&gt;
parts of the generated slides were silently cropped.&lt;/p&gt;

&lt;p&gt;What made this tricky was that the slides usually looked fine during editing and review.&lt;br&gt;
The overflow only became obvious after export — or worse, during the actual presentation.&lt;/p&gt;

&lt;p&gt;After missing this a few times, I realized the problem wasn’t how I generated the slides,&lt;br&gt;
but how hard it was to notice when something was already broken.&lt;/p&gt;




&lt;h3&gt;
  
  
  Why layout issues are easy to miss
&lt;/h3&gt;

&lt;p&gt;Slide layouts depend on many factors:&lt;br&gt;
screen size, font rendering, code block wrapping, and export targets.&lt;/p&gt;

&lt;p&gt;Even with careful review, it’s surprisingly easy to miss small layout failures.&lt;br&gt;
If everything &lt;em&gt;mostly&lt;/em&gt; looks fine, our attention moves on.&lt;/p&gt;

&lt;p&gt;This problem becomes worse when slides are generated automatically.&lt;br&gt;
There’s often no strong “this looks wrong” moment, and broken output can slip through silently.&lt;/p&gt;




&lt;h3&gt;
  
  
  The real problem: detectability, not fixing
&lt;/h3&gt;

&lt;p&gt;At some point, I realized the hard part wasn’t fixing layouts.&lt;/p&gt;

&lt;p&gt;It was noticing failures early enough to matter.&lt;/p&gt;

&lt;p&gt;Before fixing anything, you need a reliable signal that something is wrong.&lt;br&gt;
Without that signal, both humans and automated systems tend to miss problems.&lt;/p&gt;




&lt;h3&gt;
  
  
  A small experiment
&lt;/h3&gt;

&lt;p&gt;To explore this idea, I built a small CLI tool that tries to detect layout overflows&lt;br&gt;
in Slidev presentations.&lt;/p&gt;

&lt;p&gt;It’s intentionally heuristic-based and far from perfect.&lt;br&gt;
The goal isn’t to guarantee correctness, but to make layout failures&lt;br&gt;
&lt;em&gt;machine-detectable&lt;/em&gt; early in the workflow — for example, in CI or automated pipelines.&lt;/p&gt;

&lt;p&gt;If you’re curious, the repository is here:&lt;br&gt;
&lt;a href="https://github.com/mizuirorivi/slidev-overflow-checker" rel="noopener noreferrer"&gt;https://github.com/mizuirorivi/slidev-overflow-checker&lt;/a&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  Takeaway
&lt;/h3&gt;

&lt;p&gt;This project reminded me that many real-world problems aren’t about generating better output,&lt;br&gt;
but about making failures visible.&lt;/p&gt;

&lt;p&gt;Especially in AI-assisted workflows, the absence of clear failure signals&lt;br&gt;
can be more limiting than generation quality itself.&lt;/p&gt;

&lt;p&gt;I’m curious how others handle layout or visual validation&lt;br&gt;
in generated documents or presentations.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>frontend</category>
      <category>devtool</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
