
Cross-Browser Testing Checklist
Reviews a site's CI and test coverage to confirm it works across Chrome, Firefox, Safari and Edge
- Repository
- thedaviddias/Front-End-Checklist
- Stars
- 74,632
- Licence
- MIT
- Files
- 2 files
What it does
This skill gives an AI agent a checklist for cross-browser testing, meaning checking that a website works the same in Chrome, Firefox, Safari and Edge, on desktop and mobile. When asked to review a project, the agent checks whether these browser tests are actually automated and enforced in CI (the automated pipeline that runs on each code change), not just written down. It can also suggest fixes for browser-specific problems and explain why this matters.
Great for
- Front-end developers reviewing whether their test pipeline covers multiple browsers
- Teams auditing CI workflows for gaps in browser coverage
- Anyone learning what a basic cross-browser testing standard looks like
Skip it if
- Projects that need full end-to-end test code written for them: the skill is a review checklist and points to references/rule.md for details, not a complete test suite generator
- Situations where the agent's judgment alone must certify compatibility; it gives guidance, not a guarantee, and real device testing is still needed
Try asking
- “Review my CI workflows and tell me where cross-browser tests are missing or not blocking merges”
- “Check whether this website is verified in Chrome, Firefox, Safari and Edge and list the gaps”
- “Suggest how to add Playwright cross-browser tests to my GitHub Actions pipeline”
- “Explain to my team why we should test across browsers”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 2 original files, the MIT licence and an attribution note.
cross-browser-testing.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip cross-browser-testing.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip cross-browser-testing.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at your CI configuration files and test folders so its review is grounded in your real setup
- Ask it to flag specifically which browsers or mobile views are untested, rather than a general opinion
- Use references/rule.md for framework-specific examples such as Playwright or BrowserStack
What's inside
- references/rule.md
- SKILL.md
Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.