playwright-automation
CLAUDE.md0 starsChanged 3 months agoApache-2.0View on GitHub
Read and follow AGENTS.md for this entire repository. In particular, when the tester opens this clone and only says "test" or "kiểm thử", run npm run test:standalone yourself. Use npm test only for an explicit full regression request. Do not ask them to import the skill into another project or manually install npm/Playwright dependencies; the repository runner bootstraps those automatically. For authenticated live targets, use only the ignored root .env that bootstrap/helper creates; never treat a dotenv under template/example/fixture paths…
- Reads credentials
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- playwright-automationSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read and follow AGENTS.md for this entire repository.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code repository instructions
Read and follow AGENTS.md for this entire repository.
In particular, when the tester opens this clone and only says "test" or "kiểm thử", run npm run test:standalone yourself. Use npm test only for an explicit full regression request. Do not ask them to import the skill into another project or manually install npm/Playwright dependencies; the repository runner bootstraps those automatically.
For authenticated live targets, use only the ignored root .env that bootstrap/helper creates; never treat a dotenv under template/example/fixture paths as real. On a confirmed non-production certificate interstitial, switch to the repository Playwright helper with --ignore-https-errors --confirm-non-production instead of asking the tester to bypass the warning manually.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

