frontend-testing

frontend-testing is a cursor rule for Cursor from williamisnotdefined/rubiks-cube-solver. It costs 0 tokens per session (3,465 once invoked), scanned A, original, MIT.

A set of instructions for testing web interfaces, application programming interfaces (APIs), and browser workflows. It covers unit tests, component tests, Storybook checks, coverage, and Playwright end-to-end tests.

In plain words
What is it for?
Use it when changing Vitest or Testing Library tests, API-domain tests, Storybook stories, coverage settings, or Playwright browser tests.
Why use it?
It helps keep tests focused on user-visible behavior and reminds you to check failures, cancellation, accessibility, and coverage consistently.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when changing Vitest or Testing Library tests, API-domain tests, Storybook stories, coverage settings, or Playwright browser tests.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/williamisnotdefined/rubiks-cube-solver/frontend-testing
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.

Clone the repo
git clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solver

Made for: Cursor.

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/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing/github.svg)](https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing)
Your own site
<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for frontend-testing

Your own site · 80×15
<a href="https://agentmods.dev/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing"><img src="https://agentmods.dev/badge/rules/williamisnotdefined/rubiks-cube-solver/frontend-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.03465
Opus 5.5 $0.00000 $0.01386
Sonnet 5.5 $0.00000 $0.00693
Haiku 4.5 $0.00000 $0.00347

Measured 1mo ago against content hash 73119bc3038e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

.cursor/rules/frontend-testing.mdc · 222 lines

How it starts

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

Generated from ai/registry.json. Do not edit manually.

Canonical skill: ../../ai/skills/frontend-testing.md.

Referenced context:

  • ../../ai/rules/frontend-rules.md
  • ../../ai/rules/testing-rules.md
  • ../../ai/rules/frontend-quality-rules.md
  • ../../ai/architecture/web-architecture.md

This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.

Compiled AI Skill: frontend-testing

Canonical Skill: ai/skills/frontend-testing.md

Frontend Testing

Use for Vitest, Testing Library, API-domain tests, coverage, Storybook, and Playwright E2E.

Read First

  • ai/rules/frontend-rules.md
  • ai/rules/testing-rules.md
  • ai/rules/frontend-quality-rules.md
  • ai/architecture/web-architecture.md

Workflow

  • Test observable behavior at the narrowest public boundary and place it in the nearest established __tests__ folder.
  • Use accessible queries and shared API/E2E helpers; cover cancellation and recoverable failures where relevant.
  • Keep global statements, branches, functions, and lines thresholds at 90%.
  • Run the targeted test first, then coverage, Storybook, or the relevant E2E split for the changed surface.

Referenced Context

Reference: ai/rules/frontend-rules.md

Frontend Rules

Boundaries

  • Keep solving, notation semantics, puzzle validity, and replay verification in Rust. React renders and coordinates typed product workflows.
  • Keep HTTP mechanics and normalization in apps/web/src/api; UI consumes domain hooks/adapters.
  • Typed scan-session contracts MAY contain reviewed stickers, confidence, and manual overrides. Notation solve UI MUST NOT expose facelet, Kociemba, or raw cube-state inputs.
  • Keep API load, form, page workflow, solve result, scanner review, and visualization playback state separately owned unless a focused page owner coordinates them.
  • Use the active @rubiks-cube-solver/rubiks-cube package as a visualization adapter, never as canonical solver state.

Read the full file on GitHub · 222 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. 1mo ago First seen · 222 lines · 0 tokens per session scan A 73119bc3038e

Subscribe to this mod's changes

frontend-testing is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,465 tokens. 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-31.