The Form Watchdog.
A daily check that your signup form still works, and speaks up only when it doesn't.
What this prompt does
- Fills in your signup form properly and submits it
- Decides honestly whether it worked, ignoring reassuring words
- Checks where signups land, not just what the page said
- Runs on a schedule and only speaks up on bad news
Why it works
Checks every morning that your signup form still works, and only speaks up when it doesn't. Your form breaking is silent by nature — no error, no alert, just a thinner week you work out later from the numbers.
The most-tested item in the pack, and tested in both directions, which is the part that makes it trustworthy. It passed on a working form five times, each pass confirmed against a real record at the destination rather than against a reassuring page. It correctly reported FAIL on a page with no form. Then it fired unattended, passed in under half a minute, and deleted its own test signup.
The trap it exists to catch: a signup that had failed still showed the word "confirm" on the page, because the field underneath was labeled Confirm Password. Anything hunting for reassuring words would have called that a healthy form every single morning. So this one ignores words entirely.
Setup
Fill in the two brackets
Swap
[YOUR FORM PAGE]and[YOUR EMAIL]for your own.Paste it into Claude Code and let it set itself up
It checks whether Playwright is installed and installs it if it isn't. Say yes. It runs with no visible window, which is what you want for something that runs while you sleep.
Watch it run once on a form you know works
It should come back PASS. Read what it checked, not just the verdict.
Now break the form on purpose and run it again
It must come back FAIL. A watchdog that has only ever seen a working form has not been tested — the failure that costs money is the silent one, where the form breaks and the check still says PASS.
Only then let it schedule the daily check
Not before. A schedule you have not watched work is a schedule you are trusting blind.
Tested in both directions
This one was run against a working form and against a form engineered to fail. It returned PASS on the first and FAIL on the second. That second run is the one that matters: a naive check looking for the word "confirm" would have called the broken form a pass, because the page carries a field labeled "Confirm Password". Scheduling has since been proven too: it now runs unattended on a daily schedule, and every run, pass or fail, is written to its own log.
Put it on a schedule
Ask for the schedule only after a clean manual run
Both directions tested — a PASS on a working form and a FAIL on a broken one.
Make it tell you three things
What day and time it will run, where the schedule lives, and how to switch it off. A scheduled job nobody can find or stop is a liability, not an asset.
Then leave it alone. Never force a test run.
A forced test run can replace the recurring schedule instead of adding to it, and then switch itself off when it finishes. You are left with a monitor that looks healthy in the list and never runs again — which is the exact failure this job exists to catch. That happened here, once, while these jobs were being tested. If you do force a run, check afterwards that the daily one is still there and still on.
Check where it will actually run
A schedule that lands on a machine with no browser and no login fails every morning without telling you.
Tips for this prompt
- Silence is the good outcome. You should rarely hear from it.
- Break the form on purpose once, and check it says FAIL.
- Give it access to where signups land if you can.
- Never force a test run — it can wipe the schedule.
How to use the prompt
- 1Swap [YOUR FORM PAGE] and [YOUR EMAIL] for your own
- 2Paste it into Claude Code and let it set itself up
- 3Watch it run once on a form you know works
- 4Break the form and watch it report FAIL
- 5Only then let it schedule the daily check
More like thisSetup prompts
Browse all →