frontend-testing
Skill2k starsChanged 39 days agoLicence not identifiedView on GitHub
Use when writing or fixing tests in apps/frontend. Covers Jest and React Testing Library conventions, targeted test runs, the coverage mandate, Zustand mocking, and common pitfalls.
We split this skill into the rules it gives an agent
16 rules. 0 are common, 4 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- langgenius/dify★ 160ksame name
- langflow-ai/langflow★ 156ksame name
- YFGaia/dify-plus★ 2.3ksame name
- Ohh-889/skyroc-admin★ 795same name
- theexperiencecompany/gaia★ 324same name
- mcowger/plexus★ 238same name
- nightscout/nocturne★ 147same name
- nilecui/SkillsBase★ 27same name
- bestdeejay-design/agent-skills★ 6same name
- aboio-labs/aboio-skills★ 3same name
6 more not listed
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.
Used alongsideProjects with it also use backend-code-review, component-refactoring and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jpoindexterSkillbackend-code-review
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
Also in 4 projects that use this
Charlie85270Skillcomponent-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
Also in 3 projects that use this
chendongqiSkillfrontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
Also in 6 projects that use this
CloudflareSkillreceiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Also in 3 projects that use this
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backend-patternsSkill
- code-reviewSkill
- desktop-sonarSkill
- frontend-designSkill
- frontend-sonarSkill
- frontend-testingSkill
- mobile-patternsSkill
- monorepo-opsSkill
- react-doctorSkill
- yosemite-client-communicationsSkill
- yosemite-data-migration-auditSkill
- yosemite-inventory-planningSkill
- yosemite-practice-workflow-auditSkill
- yosemite-staff-onboardingSkill
- yosemite-vet-software-buyerSkill
- yosemite-vet-visit-prepSkill
- backend-patternsSkill
- code-reviewSkill
- desktop-sonarSkill
- frontend-designSkill
- frontend-sonarSkill
- mobile-patternsSkill
- monorepo-opsSkill
- react-doctorSkill
- yosemite-client-communicationsSkill
- yosemite-data-migration-auditSkill
- yosemite-inventory-planningSkill
- yosemite-practice-workflow-auditSkill
- yosemite-staff-onboardingSkill
- yosemite-vet-software-buyerSkill
- yosemite-vet-visit-prepSkill
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.