skill-maintenance

Maintain the Frontend Testing Skill in this repo. Use when asked to review the skill, run a spec/quality review, install-local (wire one example app to the local marketplace), sync up (an example app → root), install-marketplace (switch the vitest-browser app to the published GitHub marketplace), run a sanity test of the skill end-to-end (single app or the monorepo example, per package), run validate-release (install from GitHub marketplace → sanity → restore) against the vitest-browser app, or create a fresh example app copy at a given path for manual install testing.

Jump to install

Repository: practicajs/the-frontend-testing-skill
Last source activity: July 21, 2026 at 07:22
Detected SKILL.md language: English
Stars: 4
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/practicajs/the-frontend-testing-skill --skill skill-maintenance

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

12 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Skill Maintenance

A toolkit for local maintainers of this repo. It reviews, syncs, and sanity-tests the Frontend Testing Skill, whose source of truth is plugin/frontend-testing/ (this is what ships to users). The two example apps — example-app-vitest-browser/ and example-app-playwright/ — resolve the skill via a local marketplace reference; no skill files are embedded in them. The root the-testing-skill/ tree is deprecated; ignore it.

Keep all maintenance docs short. Trust your judgment and ask the user when unsure.

Operations

Pick the matching reference doc and follow it.

When the user asks to…

Read

review / audit the skill, check the spec, find issues

references/review.md

install local — wire one named example app to the local marketplace (the current, non-copy way both apps are actually set up)

references/install-local.md

sync up — pull one named example app back to root

references/sync-up.md

install-marketplace — switch vitest-browser from local wiring to the published GitHub marketplace

references/install-marketplace.md

sanity-test the skill end-to-end (build a feature, verify tests)

references/sanity-test.md

sanity-test the skill in the monorepo (example-monorepo, per package)

references/sanity-test-monorepo.md

validate-release — install from GitHub marketplace → sanity → restore, on vitest-browser

references/validate-release.md

publish / release the skill to the Claude plugin marketplace

references/publish-claude.md

publish / release the skill to the Cursor marketplace

references/publish-cursor.md

fresh example app — copy vitest-browser to a path, stripped of skill/marketplace, ready for a clean install