Start here
Choose a test account and fictional record where possible. Capture one normal path and a failure path. Identify which actions submit data or cause other external changes.Copy this prompt
Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.Check the result
Walk through the draft in a test environment. Verify the current UI and success receipt. A screenshot of a completed form is not evidence that it was submitted.See a worked example
See a worked example
Go deeper: setup choices and edge cases
Go deeper: setup choices and edge cases
Avoid turning historical coordinates into an automation contract. Browser layouts, labels, sessions, and records change. An implementation needs current element or API checks, expected state, and a stop condition when the page differs.Document duplicate prevention before retrying a submit action. If the network response is ambiguous, check the authoritative record before repeating the operation. Preserve the distinction between an observed step and a proposed shortcut.