in-editor-testing
Skill0 starsChanged 3 months agoMITView on GitHub
Perform silent, headless in-editor browser testing using Playwright MCP without launching external desktop windows.
In this repository11 other files it gives its agents.
- frontend/AGENTS.mdAGENTS.md
- .agents/skills/ui-ux-pro-max/CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- contract-risk-analyzerSkill
- deep-causal-reasoningSkill
- fable-reasoningSkill
- frontend-designSkill
- opus-reasoningSkill
- rufloSkill
- sonnet-reasoningSkill
- ui-ux-pro-maxSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When asked to test web endpoints, UI components, or local servers:
- Very specific: line 9
Use the Playwright MCP Tools: Prefer playwright-headless MCP tools to navigate, click, fill forms, and assert page states.
- Distinctive: line 10
Stay Headless: Do not launch external headful browser windows.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
In-Editor Browser Testing Workflow
When asked to test web endpoints, UI components, or local servers:
- Use the Playwright MCP Tools: Prefer
playwright-headlessMCP tools to navigate, click, fill forms, and assert page states. - Stay Headless: Do not launch external headful browser windows.
- Capture Inline Output: Return test assertions, console logs, and accessibility tree diffs directly in the chat or test report.
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.

