The latest articles on DEV Community by Angelo (@angeloforz). https://dev.to/angeloforz https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3184711%2F0f07f167-65d6-4aa2-8b15-117ea096be1a.jpg https://dev.to/angeloforz en Angelo Mon, 19 Oct 2026 15:00:56 +0000 https://dev.to/angeloforz/make-ai-website-edits-easier-to-check-1ihk https://dev.to/angeloforz/make-ai-website-edits-easier-to-check-1ihk <p>Suppose you ask an AI assistant to restyle a button. The page looks better, but the mobile navigation stops opening. Asking for several changes at once makes it harder to work out which change caused the problem.</p> <p>A smaller editing loop helps: choose one visible change, describe what must stay working, then check the page before moving on.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo2i4wexaxz0c4bv0aicd.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo2i4wexaxz0c4bv0aicd.png" alt="Pulse’s actual desktop workspace, with the conversation and a running space-themed page visible together." width="800" height="412"></a></p> <p><em>The conversation and running page stay visible together in Pulse.</em></p> <h2> Give the change a clear boundary </h2> <p>“Improve this page” leaves almost everything open. A specific request gives you something you can verify:</p> <blockquote> <p>Change the main signup button to a filled blue style. Keep its label, destination and position unchanged. Preserve the visible keyboard focus state. Leave the other buttons alone.</p> </blockquote> <p>Adapt the request to the element you are editing.</p> <h2> Point to the element </h2> <p>If your tool supports selecting an element in a preview, use that reference. Otherwise, give its label and location, or attach a marked screenshot. Two buttons can look similar while serving different purposes.</p> <p>Keep the running page visible beside the conversation where possible. Check the result itself as well as the assistant’s description of its changes.</p> <h2> Check more than the appearance </h2> <p>For a button change, click it and verify the destination. Reach it with the keyboard and check that focus is visible. Try a narrow screen. For a form, also try an empty submission and an invalid value.</p> <p>If something breaks, stop adding changes. Ask the assistant to inspect the latest edit against the previous working version. Save a working copy or commit before starting the next change.</p> <h2> Why I built around this workflow </h2> <p>I built Pulse because I wanted to work with AI while keeping the code and result in view. Extra configuration kept pulling my attention away from what I was trying to make.</p> <p>Pulse puts chat, its editor and live preview in one desktop workspace. Point-to-edit notes let you identify an element in the preview for the AI. It also includes token optimization, optional smart routing and local voice setup handled inside the app.</p> <p>The software costs $39 once for macOS and Windows. You bring your own supported provider keys; cloud AI usage is billed separately. Product details and actual workspace screenshots are at <a href="https://www.builtbyangelo.co/?utm_source=devto&amp;utm_medium=community&amp;utm_campaign=pulse_workflow&amp;utm_content=one_visible_change" rel="noopener noreferrer">builtbyangelo.co</a>.</p> webdev ai productivity