Why Browser Automation Needs Intent-Based Skills

Browser automation has a fundamental problem. We've been teaching computers how to do things instead of teaching them what we want to achieve. This approach creates brittle systems that break at the slightest change. The Selector Trap Traditional browser automation relies on CSS selectors, XPath queries, and coordinate-based interactions. These are implementation details that have nothing to do with the actual task being performed. When a developer writes: await page . click ( ' #submit-btn-3 ' ); await page . fill ( ' .form-input[name="email"] ' , ' user@example.com ' ); They're not saying "submit the form" or "enter the email address." They're saying "click the element with ID submit-btn-3" and "fill the input with name email." This is fragile. When the website updates and the ID changes to submit-button , the automation breaks. Not because the task changed, but because the implementation details changed. Intent Over Implementation Intent-based automation flips this model. Instead of