frontend-testing
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.
Profile →npx skills add langgenius/dify --skill frontend-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Frontend Testing `web/docs/test.md` is the single policy owner. Read it before changing frontend tests; this skill adds no separate requirements. 1. Identify the observable contract and regression risk. 2. Choose the smallest boundary that includes the behavior owner. 3. Establish the failing case first when practical, then implement one coherent scenario. 4. Run the focused spec before the affected suite and relevant static checks. 5. Report the behavior verified and any remaining browser, visual, or end-to-end risk. Recommend deleting low-value tests as readily as adding missing behavior coverage. Use `web/docs/test.md` for policy and Web commands; use the `packages/dify-ui/README.md` Development section for Dify UI commands.
What does the frontend-testing skill do?
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.
How do I install it?
Run `npx skills add langgenius/dify --skill frontend-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From langgenius/dify, a repository with 151,326 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.