<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/8f898e43abdd4910a03368aa92be7d1f&quot; frameborder=&quot;0&quot; width=&quot;1660&quot; height=&quot;1245&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1245</height><width>1660</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1245</thumbnail_height><thumbnail_width>1660</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/8f898e43abdd4910a03368aa92be7d1f-0b6d5ff57ef04e67.gif</thumbnail_url><duration>300.313</duration><title>Part 1 - Problem Space, Moodboarding via Paper x Claude</title><description>I walked through how I used paper and Claude Code to redesign slow day AI loading states for the AI parsing stage. First, I screenshot the problem space states into a frame called problem space, then sent the notes and screenshots to Claude Code to analyze issues. Second, I moodboarded two directions, minimal to maximalist, plus a more Dynamic Island style, with rules to not copy inspirations one to one. Then I asked Claude to compile directions, and I went back into paper to test the early screen drafts. I did not request any viewer action.</description></oembed>