frontend-testing

frontend-testing is a skill for Claude Code, Codex from clubpay/ronykit. It costs 48 tokens per session (797 once invoked), scanned A, original, BSD-3-Clause.

A guide for testing React and Next.js web frontends with unit tests, component tests, and Playwright end-to-end tests. It recommends checking what users see and doing the verification work through completion.

In plain words
What is it for?
Use it when adding or repairing frontend tests, testing components and hooks, checking Next.js routes, or writing browser-based user flows.
Why use it?
It reduces tests that depend on internal implementation details and helps catch failures across type checking, linting, builds, and tests. TDD, or test-driven development, is not required by the input.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/clubpay/ronykit/frontend-testing
Any agent
npx skills add clubpay/ronykit --skill frontend-testing
Clone the repo
git clone --depth 1 https://github.com/clubpay/ronykit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for frontend-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/clubpay/ronykit/frontend-testing.svg)](https://agentmods.dev/skills/clubpay/ronykit/frontend-testing)
Your own site
<a href="https://agentmods.dev/skills/clubpay/ronykit/frontend-testing"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/frontend-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 797 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00797
Opus 5 $0.00024 $0.00398
Sonnet 5 $0.00010 $0.00159
Haiku 4.5 $0.00005 $0.00080

Measured 4d ago against content hash da5e84bf3eb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ronyup/internal/skeleton/skills/frontend-testing/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Testing

Test what the user experiences, not implementation details. Query the DOM the way a user (or assistive tech) does.

Close the loop yourself (do not hand back to the user)

Writing tests/code is not the finish line — a clean run is. Drive the verify-and-fix loop autonomously; never ask the user to run the app, paste errors back, or confirm a fix worked.

  1. Run pnpm typecheck, pnpm lint, pnpm build, pnpm test (and pnpm build-storybook when present) for the target app.
  2. Read the full output, fix every error and meaningful warning, then re-run from the failed step.
  3. Repeat until all steps pass. Only stop to ask the user when genuinely blocked (missing secret, ambiguous product decision) — not for routine type/lint/test/build failures.
  4. Report completion only with fresh passing output as evidence.

When to use

  • Adding tests for React components, hooks, or Next.js routes.
  • Writing end-to-end flows with Playwright.
  • Fixing flaky or implementation-coupled frontend tests.

Levels

  1. Unit — pure functions, hooks, utilities. Fast, no DOM where possible.
  2. Component — render a component with Testing Library; assert on visible output and behavior.
  3. End-to-end — Playwright drives a real browser through whole user flows.

Prefer the lowest level that proves the behavior; reserve E2E for critical paths.

Component tests (Vitest + Testing Library)

  • Query by role/label/text, not test IDs or class names: getByRole('button', { name: /save/i }). Use data-testid only as a last resort.
  • Drive interactions with @testing-library/user-event, not raw fireEvent.
  • Assert on what the user sees (text, roles, ARIA state), never on component internals or props.
  • Use findBy* / waitFor for async UI instead of fixed timeouts.
  • Mock network at the boundary (e.g. MSW), not by stubbing your own components.
test('submits the form', async () => {
  const user = userEvent.setup()
  render(<LoginForm onSubmit={onSubmit} />)
  await user.type(screen.getByLabelText(/email/i), '[email protected]')
  await user.click(screen.getByRole('button', { name: /sign in/i }))
  expect(onSubmit).toHaveBeenCalledWith({ email: '[email protected]' })
})

Read the full file on GitHub · 86 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 86 lines · 48 tokens per session scan A da5e84bf3eb8

Subscribe to this mod's changes

frontend-testing is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.