New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fantasia Testing

by vishiri in vishiri/fantasia-archive

Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming.

GPL-3.0Auto-check passedTesting & QA

Install Fantasia Testing

skills CLI
$ npx skills add vishiri/fantasia-archive --skill fantasia-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vishiri/fantasia-archive fantasia-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/fantasia-testing .claude/skills/fantasia-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
fantasia-testing
GitHub stars
409
Token cost
~3.1k tokens
SKILL.md length
859 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
GPL-3.0

At a glance

Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming.

  • Works in 4 steps: Discover — ripgrep component/dialog… → Vitest — yarn vitest run with explicit… → Playwright (component) — each matching… → …
  • The user mentions Vitest
  • SKILL.md covers Cursor rules (detailed…, Connected tests for any…, Vitest coverage tiers (CI) and Unit tests (Vitest), plus 5 more sections
  • Calls yarn

What it does

Fantasia Testing is an agent skill from vishiri/fantasia-archive. Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming. Use when writing tests, debugging CI, or when the user mentions Vitest, Playwright, component tests, or e2e.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing, Browser testing and End-to-end testing. It works with Playwright, Vitest and Vue.js. The repository describes itself as: A world-builder's best friend! The licence is GPL-3.0.

When your agent uses it

  • The user mentions Vitest
  • Component tests

Example prompts

  • “/fantasia-testing”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Discover — ripgrep component/dialog folder, helpers, data-test-locator, T_dialogName, COMPONENT_NAME, action/keybind ids, store symbols…
  2. Vitest — yarn vitest run with explicit paths for every matching *.vitest.test.ts (feature _tests/, scripts/_tests/, src/scripts//_tests…
  3. Playwright (component) — each matching src//_tests/*.playwright.test.ts: yarn test:components:single --component=/ or yarn test:components…
  4. Playwright (E2E) — each matching e2e-tests/*.playwright.spec.ts: yarn test:e2e:single --spec=… or yarn test:e2e with same rebuild rule.

What it can do on your machine

Read from SKILL.md and the folder at commit 26d4648. 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

    Shell commands in SKILL.md call:

    • yarn

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.

    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

Fantasia Testing loads about 3.1k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 859 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

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

The full file from vishiri/fantasia-archive at commit 26d4648, republished under its GPL-3.0 licence (© vishiri). 859 words, ~3,112 tokens.

Download SKILL.mdSave it as .claude/skills/fantasia-testing/SKILL.md (or your agent's skills folder).
name
fantasia-testing
description
Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming. Use when writing tests, debugging CI, or when the user mentions Vitest, Playwright, component tests, or e2e.

Fantasia Archive — testing

Cursor rules (detailed structure)

Match existing tests when adding or editing:

Connected tests for any feature change

Tests = same deliverable as production edits.

  1. Discover — ripgrep component/dialog folder, helpers, data-test-locator, T_dialogName, COMPONENT_NAME, action/keybind ids, store symbols, i18n keys you changed. Follow imports + menu _data/ entries.
  2. Vitest — yarn vitest run with explicit paths for every matching *.vitest.test.ts (feature _tests/, scripts/_tests/, src/scripts/**/_tests, src/stores/_tests, src-electron/**/_tests, helpers/**/_tests, i18n/_tests when implicated). During edits: fantasia-dev-scoped-verify. Before commit / final cleanup: yarn testbatch:verify.
  3. Playwright (component) — each matching src/**/_tests/*.playwright.test.ts: yarn test:components:single --component=<bucket>/<ComponentFolder> or yarn test:components in own terminal after yarn quasar:build:electron when bundle exercises changed renderer code (testing-terminal-isolation.mdc).
  4. Playwright (E2E) — each matching e2e-tests/*.playwright.spec.ts: yarn test:e2e:single --spec=… or yarn test:e2e with same rebuild rule.

CI scope: default Verify workflow runs yarn testbatch:verify only — not component/E2E Playwright. Run locally (or yarn testbatch:ensure:nochange) when feature touches those flows.

Vitest coverage tiers (CI)

See vitest-tests.mdc Vitest coverage tiers (CI): per instrumented file (thresholds.perFile: true) — 95% statements/lines, 80% branches, 100% functions on src-electron, helpers/**/*.ts (helpers/playwrightHelpers_* excluded), unit-src-renderer src .ts, scoped i18n/ (unit-i18n), and unit-components .ts / .vue under src/components, src/layouts, src/pages (src/components/foundation/** excluded). Configs: vitest/.

Unit tests (Vitest)

  • Commands: yarn test:unit — multi-project root (vitest.config.mts: unit-electron, unit-src-renderer, unit-helpers, unit-i18n, unit-components) without coverage. yarn testbatch:verify ends with yarn test:coverage:verify. Debug slices: yarn test:coverage:electron, yarn test:coverage:helpers, yarn test:coverage:i18n, yarn test:coverage:src. Full tier detail: vitest-tests.mdc.
  • Execution: Dev edits — fantasia-dev-scoped-verify. Commit / final cleanup — yarn testbatch:verify. Do not chain unit/coverage with yarn quasar:build:electron or Playwright in one shell line.
  • Reports: test-results/vitest-report/test-results-vitest-*.json per project.
  • Scope: src/ + src-electron/ with *.vitest.test.ts under _tests/; component mounts use @vue/test-utils + vitest.setup.ts.
  • helpers/: playwrightHelpers_* = Playwright harness only — extend with yarn test:components / yarn test:e2e after yarn quasar:build:electron; no *.vitest.test.ts there. Non-Playwright helpers/<name>/: colocate _tests/*.vitest.test.ts.
  • SFC baseline: one _tests/<Name>.vitest.test.ts per feature .vue under src/components/**, src/layouts/**, src/pages/**. Extracted scripts/*.ts → scripts/_tests/*.vitest.test.ts when real logic. Merge tests when merging modules (code-size-decomposition.mdc).
  • Return object literals: same project-wide rule — identifiers/literals only in return { ... } (code-size-decomposition.mdc).
  • Floating Window* mounts: stub FaFloatingWindowBodyTeleport or query document.body — see fantasia-floating-windows.
  • _data/: production feeds only — no Vitest suites aimed only at _data/. Fixtures inline in test files; no _tests/_data/.
  • Style: flat test / test.skip (no describe), JSDoc per test, titles Test that ... — see vitest-tests.mdc.
  • Typing: no any; use I_ / T_ naming for imported types.

Playwright (component + E2E)

Critical: Playwright targets built, production Electron app. After any source change affecting exercised code: quasar build -m electron or yarn quasar:build:electron before Playwright. Node.js 22.22.0+ locally.

Stale packaged bundle — Harness starts Fantasia Archive.exe from dist/electron/Packaged, not live Vite dev server. IPC still matching pre-change behavior → rebuild before next Playwright run.

Electron userData isolation: TEST_ENV components / e2e → %APPDATA%/<package.json name>/playwright-user-data (here: fantasia-archive/playwright-user-data, not fantasia-archive-dev). appIdentity_manager.ts, playwrightIsolatedUserDataDirName.ts, playwrightUserDataReset.ts. Specs use test.describe.serial; test.beforeAll **await**s launchFaPlaywrightComponentHarnessWindow / launchFaPlaywrightE2eAppWindow (owns resetFaPlaywrightIsolatedUserData() ordering — not in test.beforeEach). Helpers: helpers/playwrightHelpers_universal / _e2e / _component. No test.describe.parallel unless user asks.

Playwright keyboard.press and app keybinds (cross-OS)
  • Module: faPlaywrightKeyboardChords.ts
  • Defaults with primary: use getters (getFaPlaywrightDefaultToggleDevtoolsPressString(), etc.) — not hardcoded Control+F12 / Meta+F12.
  • Overrides storing ctrl: physical Control on every OS — FA_PLAYWRIGHT_PRESS_CONTROL_SHIFT_F12, etc.
  • Monaco select all: getFaPlaywrightMonacoSelectAllPressString()
  • Full policy: playwright-tests.mdc Keyboard strings; product: fantasia-keybinds.
Show full SKILL.md (351 more words)Show less
Cross-toolchain (Storybook + Electron)
  • Storybook — .storybook-workspace/; staticDirs sync with Quasar public/. VRT: yarn test:storybook:visual* chains yarn storybook:build. Verbose: FA_STORYBOOK_VISUAL_VERBOSE=1.
  • Electron file:// — relative public/ paths when BASE_URL is '/' or empty (see SocialContactSingleButton.vue).
  • Playwright — same rebuild rule; flaky UI after green Storybook often = stale build or file:// mismatch.
  • Storybook VRT — EXCLUDED_STORY_IDS in .storybook-workspace/visual-tests/storybook.visual.playwright.test.ts; empty iframe root = failure unless tags: ['skip-visual-render-check'] or excluded id. #storybook-root and #root checked separately.
  • VRT maxDiffPixels — whole-image differing-pixel cap, not width. CI vs local: see README Storybook visual baseline policy, storybook-stories.mdc.
  • Full suite — yarn testbatch:ensure:nochange / yarn testbatch:ensure:change — see testing-terminal-isolation.mdc.
Config highlights (playwright.config.ts)
  • outputDir: test-results/playwright-artifacts. testMatch: src/components/**, e2e-tests/**. HTML: test-results/playwright-report. Yarn scripts trim artifacts via .utility-scripts/playwrightWithArtifactTrim.mjs.
  • workers: 1, fullyParallel: false
  • Serial suites: launchFaPlaywright* + tearDownFaPlaywrightElectronSerialSuite. Video: FA_PLAYWRIGHT_NO_VIDEO; cursor: FA_PLAYWRIGHT_CURSOR_MARKER=0.
Videos and HTML report
  • WebM attached per serial suite. Report regenerates each run — ephemeral. Agents: prefer user opens test-results/playwright-report/index.html over analyzing raw .webm.
Component tests
  • Renderer readiness: waitForFaRendererContentBridgeApis — not bare page.evaluate for bridge globals. E2E on #/: waitForFaE2eRendererDomReady.
  • Structure/locators/layout: playwright-tests.mdc
  • Command: yarn test:components — own terminal (src/components, src/layouts, src/pages)
  • Location: src/components|layouts|pages/**/_tests/*.playwright.test.ts
  • Single: yarn test:components:single --component=<bucket>/<ComponentName>
  • Picker: yarn test:components:list
  • Harness seed: I_faComponentTestingStoreSeed / projectContentOverrides — see AGENTS Component-testing seed
E2E tests
  • Structure: same serial pattern; TEST_ENV: 'e2e'
  • Project management: checkProjectManagementFlow.playwright.spec.ts; path staging via playwrightE2eProjectPaths.ts
  • Workspace sidebar: checkWorkspaceSidebar.playwright.spec.ts; drag + sidebar_width cold restart via faPlaywrightE2eWorkspaceSidebar.ts
  • Workspace docs/tree: e2e-tests/checkWorkspace*.playwright.spec.ts; helpers e2eWorkspaceHierarchyTree*
  • Command: yarn test:e2e — own terminal
  • Single: yarn test:e2e:single --spec=<stem> (no suffix) or yarn test:e2e:single:ci --spec=<full file>
  • Picker: yarn test:e2e:list
Full project gate

Checklist when changing UI or Electron shell

During edits (fantasia-dev-scoped-verify):

  1. Dev scoped gate — touched eslint, yarn lint:typescript, connected yarn vitest run
  2. 20s dev compile smoke — dev-electron-compile-check.mdc

Ship / commit / final cleanup:

  1. yarn testbatch:verify — one terminal
  2. Connected Playwright after yarn quasar:build:electron — own terminals
  3. Storybook in scope: yarn test:storybook:smoke + yarn test:storybook:visual (or testbatch:ensure:*)

Choosing Vitest vs Playwright

  • Vitest: pure/data/state in src/ — deterministic
  • Playwright: user-facing interaction, full render, built Electron runtime

Storybook smoke checks

  • yarn storybook:run, yarn test:storybook:smoke
  • VRT: yarn test:storybook:visual / :update
  • Stories: src/components/**/_tests/<Component>.stories.ts, meta.title Components/<bucket>/<ComponentName>
  • Layout/page stories: canvas-only, no Docs — storybook-stories.mdc
  • Storybook mocks: focused L_* imports + externalFileLoader.ts placeholders — mirror new keys from i18n/en-US/index.ts

Types

Shared types → types/ (app/types/...). See types-folder.mdc.

© vishiri, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/fantasia-testing of vishiri/fantasia-archive.

Open the folder on GitHubat commit 26d4648

Compare with similar skills

Fantasia 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.

Fantasia Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fantasia Testing this skillvishiri/fantasia-archive409—~3.1kAutomated safety check: PassGPL-3.0
Vue Testing Best PracticesJetBrains/skills3667 repos~563Automated safety check: PassMIT
Control UI E2Eopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT
Svelte Testingspences10/sveltest113—~579Automated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Vue Testing Best Practices

    JetBrains/skills

    Official

    A skill your agent uses for Vue.js testing. An agent skill from JetBrains/skills.

    366 GitHub starsUsed in 7 repos~563 tokens
    Testing & QAAuto-check passed

  • Control UI E2E

    openclaw/openclaw

    A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…

    392k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Svelte Testing

    spences10/sveltest

    Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

    113 GitHub stars~579 tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

More from vishiri/fantasia-archive

All 35 skills in this repo

  • Caveman Commit

    vishiri/fantasia-archive

    Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 13 repos~642 tokens
    Auto-check passed

  • Caveman Review

    vishiri/fantasia-archive

    Ultra-compressed code review comments. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 12 repos~674 tokens
    Auto-check passed

  • Caveman Compress

    vishiri/fantasia-archive

    Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens.

    409 GitHub starsUsed in 9 repos~1.1k tokens
    Auto-check: notes

  • Cavecrew

    vishiri/fantasia-archive

    Decision guide for delegating to caveman-style subagents. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 7 repos~1k tokens
    Auto-check passed

  • Caveman Help

    vishiri/fantasia-archive

    Quick-reference card for all caveman modes, skills, and commands.

    409 GitHub starsUsed in 6 repos~572 tokens
    Auto-check passed

  • Fantasia Context Menu Dividers

    vishiri/fantasia-archive

    Context menu divider policy: full primary-bright group separators vs low-opacity separatorAlt between consecutive items in the same group.

    409 GitHub stars~741 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Fantasia Testing

What does Fantasia Testing do?

Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming. Fantasia Testing is an agent skill from vishiri/fantasia-archive. Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming.

When should I use Fantasia Testing?

Fantasia Testing fits situations like: the user mentions Vitest; component tests.

How do I install Fantasia Testing in Claude Code?

Run `npx skills add vishiri/fantasia-archive --skill fantasia-testing -a claude-code`. Or copy the skill folder (.cursor/skills/fantasia-testing in vishiri/fantasia-archive) into .claude/skills/fantasia-testing in your project. Claude Code loads it when a task matches its description.

How do I install Fantasia Testing in Codex?

Run `npx skills add vishiri/fantasia-archive --skill fantasia-testing -a codex`. Or copy the skill folder (.cursor/skills/fantasia-testing in vishiri/fantasia-archive) into .agents/skills/fantasia-testing in your project. Codex loads it when a task matches its description.

Can I use Fantasia 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 vishiri/fantasia-archive --skill fantasia-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/fantasia-testing, .gemini/skills/fantasia-testing, .github/skills/fantasia-testing and .opencode/skills/fantasia-testing in your project.

What does Fantasia Testing need to run?

Going by SKILL.md and its folder, Fantasia Testing needs the command-line tools its instructions call (yarn). Our summary lists: Node.js.

Does Fantasia 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 Fantasia 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 Fantasia Testing use?

Fantasia Testing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fantasia Testing use?

About 3.1k tokens (SKILL.md is roughly 12k 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 Fantasia Testing?

Skills that share tags, products or a category with Fantasia Testing: Vue Testing Best Practices (JetBrains/skills, 366 stars), Control UI E2E (openclaw/openclaw, 392k stars), Svelte Testing (spences10/sveltest, 113 stars) and Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fantasia Testing?

vishiri (a GitHub user) maintains it in vishiri/fantasia-archive, which has 409 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: vishiri/fantasia-archive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.