Thirumalai-Tech-DeveloperThirumalai-Tech-Developer/Kratos_Agent/skills/frontend-testing-debugging/SKILL.mdfrontend-testing-debugging
Skill1 starsChanged 47 days agoMITView on GitHub
Diagnose rendered frontend issues and inspect interaction, responsive layout, browser errors, and accessibility evidence.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- openai/pluginstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- openai/plugins★ 7.8ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- build-web-appsSkill
- cavemanSkill
- composioSkill
- context7Skill
- diagnoseSkill
- gitnexusSkill
- grill-meSkill
- security-auditSkill
- superpowersSkill
- tddSkill
- to-prdSkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use when the user requests frontend debugging, visual QA, or validation of an interaction.
- Distinctive: line 15
Use the available browser or project verification tools only as authorized.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Review a rendered frontend
Use when the user requests frontend debugging, visual QA, or validation of an interaction.
- Identify the target route and the user interaction that should work. Inspect project scripts and current browser state before starting a server.
- Reproduce the issue and capture the relevant state, console output, or screenshot when available.
- Trace the UI state to its source: component, event handler, request, route, and data. Make the smallest useful fix.
- Inspect desktop and narrow-screen behavior, keyboard access, labels, focus, and loading/error states relevant to the change.
- Use the available browser or project verification tools only as authorized. Describe the evidence and environment; do not say a full browser suite passed when only a screenshot was inspected.
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.