e2e-manual-debugging
Skill4 starsChanged 57 days agoAGPL-3.0View on GitHub
Use this skill when an e2e scenario can't find a UI element — `iosTap`/`iosWaitForElement`/`macClickButton`/`macWaitForElement` keeps timing out, you don't know the right `ElementQuery` to use, you need to know what `AXLabel` / `AXIdentifier` / `.help()` / `accessibilityLabel` a button actually exposes, or `iosLogUI` output isn't enough. This skill boots an interactive e2e-mode instance of the apps and walks through inspecting the running UI (XCUITest view hierarchy, AppleScript accessibility tree, Xcode's Accessibility Inspector, on-the-fly screenshots) to discover the exact attributes a scenario step needs. Use whenever someone says "I can't find this element", "what's the right query for X", "the test can't see Y", "what label does the macOS button expose", "find the accessibility identifier", or "the button isn't being clicked". Do NOT use this skill for writing new scenarios from scratch (use e2e-for-feature) or running/fixing scenarios when the issue isn't an unknown element (use e2e-testing).
- Sends data out
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- baseline-reviewSkill
- e2e-for-featureSkill
- e2e-testingSkill
- fix-e2e-failuresSkill
- installSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.

