Browser Account Guard — Design skill for Claude Code

browser-account-guard + flaky-browser-ui

Two Claude skills for agents that drive web panels. They were one file until it grew past 400 lines and started loading a browser-automation cookbook into every task that only needed to read a dashboard.

Skill	Answers	Fires when
browser-account-guard	Am I in the right account, pointed at the right thing?	you are about to act in a signed-in panel where more than one account or property could be selected
flaky-browser-ui	Why won't this UI obey?	tabs die between calls, clicks or typed values do not register, a batch died mid-write

They are independent. The second applies on public pages, in your own account, and under Playwright — no account question involved. The first points at it when you need it.

The mistake this exists to prevent

**The browser being right does not mean the account is right.**

If you automate Search Console, Google Ads, Analytics, Business Profile, wp-admin, a domain registrar, Cloudflare or Meta Business, and you work across more than one client, more than one browser, or more than one account on the same machine — you will eventually act in the wrong one. It rarely announces itself: the page loads, the data looks plausible, nothing errors.

Where it came from

Real work, not theory. Every rule is something that failed first:

• A browser correctly identified as client A's opened Search Console under client B's account, because that was the browser's default. One click from creating a client's property inside another client's account.
• The Google session index /u/N/ moved between /u/0/ and /u/3/ on consecutive navigations in the same browser, on the same day.
• Tabs died between almost every call, turning a five-step flow into twenty.
• A role=combobox in Search Console absorbed six attempts across four techniques before anyone asked whether the UI was the right path at all. **That failure is where the two-attempt budge