Frontend Testing
Ohh-889/skyroc
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities.
“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…”
Install Dify Frontend Testing
$ npx skills add langgenius/dify --skill frontend-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langgenius/dify frontend-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/frontend-testing .claude/skills/frontend-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .claude/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langgenius/dify --skill frontend-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langgenius/dify frontend-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/frontend-testing .agents/skills/frontend-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .agents/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill frontend-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langgenius/dify frontend-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/frontend-testing .cursor/skills/frontend-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .cursor/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langgenius/dify.git --path .agents/skills/frontend-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langgenius/dify --skill frontend-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langgenius/dify frontend-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/frontend-testing .gemini/skills/frontend-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .gemini/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langgenius/dify frontend-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langgenius/dify --skill frontend-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/frontend-testing .github/skills/frontend-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .github/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill frontend-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langgenius/dify frontend-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/frontend-testing .opencode/skills/frontend-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontend-testing" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/frontend-testing into .opencode/skills/frontend-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontend-testing- GitHub stars
- 158k
- Token cost
- ~242 tokens
- SKILL.md length
- 72 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
About this skill
“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.”
Dify Frontend Testing is a skill in langgenius/dify (158k stars). Its SKILL.md is about 242 tokens. Licence: Custom licence.
What it can do on your machine
Read from SKILL.md and the folder at commit cecdb28. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dify Frontend Testing loads about 242 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 72 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 72 words (~242 tokens).
“Read the testing policy for the package that owns the changed tests:”
- name
- frontend-testing
Files
Just SKILL.md in .agents/skills/frontend-testing of langgenius/dify.
Open the folder on GitHubat commit cecdb28
Compare with similar skills
Dify Frontend Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dify Frontend Testing this skilllanggenius/dify | 158k | — | ~242 | Automated safety check: Pass | Custom licence | |
| Frontend TestingOhh-889/skyroc | 795 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| React Testingcitypaul/.dotfiles | 739 | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Front End Testingcitypaul/.dotfiles | 739 | — | ~6.2k | Automated safety check: Pass | Custom licence | |
| Storybook Testingyonatangross/orchestkit | 289 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Vitest Testing Patternscuriositech/some_claude_skills | 243 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
React Testing
citypaul/.dotfiles
React component testing patterns including components, hooks, context, and forms.
Front End Testing
citypaul/.dotfiles
Behavior-driven UI testing patterns across Vitest Browser Mode, Playwright E2E evidence boundaries, and DOM Testing Library.
Storybook Testing
yonatangross/orchestkit
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking…
Vitest Testing Patterns
curiositech/some_claude_skills
Write tests using Vitest and React Testing Library. An agent skill from curiositech/some_claude_skills.
Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
More from langgenius/dify
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Frontend Code Review
langgenius/dify
Reviews frontend changes under `web/` or `packages/dify-ui/` for concrete defects and broken project contracts, using routed rule packs and a severity scale for findings.
Dify Component Writing Guide
langgenius/dify
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data…
Dify Command Line with difyctl
langgenius/dify
Base skill for the difyctl CLI: discover a Dify server's operations through help output and run them as commands, always with JSON output.
Related
Works with
Categories
Questions about Dify Frontend Testing
How do I install Dify Frontend Testing in Claude Code?
Run `npx skills add langgenius/dify --skill frontend-testing -a claude-code`. Or copy the skill folder (.agents/skills/frontend-testing in langgenius/dify) into .claude/skills/frontend-testing in your project. Claude Code loads it when a task matches its description.
How do I install Dify Frontend Testing in Codex?
Run `npx skills add langgenius/dify --skill frontend-testing -a codex`. Or copy the skill folder (.agents/skills/frontend-testing in langgenius/dify) into .agents/skills/frontend-testing in your project. Codex loads it when a task matches its description.
Can I use Dify Frontend Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langgenius/dify --skill frontend-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-testing, .gemini/skills/frontend-testing, .github/skills/frontend-testing and .opencode/skills/frontend-testing in your project.
What does Dify Frontend Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Dify Frontend Testing is instructions for the agent only.
Does Dify Frontend Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dify Frontend Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dify Frontend Testing use?
Dify Frontend Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Dify Frontend Testing use?
About 242 tokens (SKILL.md is roughly 968 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dify Frontend Testing?
Skills that share tags, products or a category with Dify Frontend Testing: Frontend Testing (Ohh-889/skyroc, 795 stars), React Testing (citypaul/.dotfiles, 739 stars), Front End Testing (citypaul/.dotfiles, 739 stars) and Storybook Testing (yonatangross/orchestkit, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dify Frontend Testing?
langgenius (a GitHub organization) maintains it in langgenius/dify, which has 158,055 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: langgenius/dify on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.