mobileqa
Skill2 starsChanged 5 months agoLicence not identifiedView on GitHub
Run the mobile compatibility suite (mobileqa.mjs) against a web app ONLY when the prompter explicitly asks for it in the current conversation — real phone emulation, per-route and per-modal screenshots in light and dark, and automated checks for modals taller than the screen, unreachable controls, horizontal overflow, iOS input zoom, tap targets and safe areas; plus the one-time install into a repo. Use ONLY when the user says to run mobile QA, asks for the mobile suite, asks to install it, or types /mobileqa. NEVER use it on your own initiative — not as part of a UI change, a commit, a ship, the screenshotqa loop or the builder flow, and not because a pre-commit hook or a gate script asks for it. For ordinary visual verification (render a screen, look at the PNG, desktop + mobile widths) use the screenshotqa skill, which does not run this suite.
In this repository7 other files it gives its agents.
- builderSkill
- crew-execSkill
- screenshotqaSkill
- securitySkill
- skillwriterSkill
- styleSkill
- themeSkill
The file
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.