Frontend Testing
by langgenius2b65f0e89309No license157K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or Cucumber/Playwright E2E.
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| SKILL.md | 966 B | text/markdown |
Source and attribution
Source:langgenius/difyin.agents/skills/frontend-testingat commit2b65f0e
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from langgenius/dify
Frontend Code Review
langgenius
Reviews frontend code under web/ or packages/dify-ui/ for defects and contract violations, reporting severity-ranked findings.
Backend Code Review
langgenius
Reviews backend code under api/ for concrete defects, routing to bundled rule packs by change type.
More in Software Development
Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.
Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.
Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.
Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.