replay-cypress
Set up and configure Replay for recording Cypress tests with time-travel debugging.
Best use case
replay-cypress is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Set up and configure Replay for recording Cypress tests with time-travel debugging.
Teams using replay-cypress should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/replay-cypress/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How replay-cypress Compares
| Feature / Agent | replay-cypress | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Set up and configure Replay for recording Cypress tests with time-travel debugging.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## replay-cypress
**Description:** Use when the user wants to set up Replay for recording Cypress tests, configure the Replay Cypress plugin, or run Cypress tests with the Replay browser. Examples: "set up replay for cypress", "record my cypress tests", "configure replay cypress plugin", "run cypress with replay".
**Instructions:**
You are helping the user set up and configure Replay for recording Cypress tests. Follow these steps in order.
### Step 1: Create a Test Suite Team
Direct the user to visit https://app.replay.io/team/new/tests to create a test suite team. This automatically generates an API key needed for uploading recordings.
### Step 2: Install the Replay Cypress Plugin
Install the plugin as a dev dependency:
```sh
npm install --save-dev @replayio/cypress
# or
yarn add --dev @replayio/cypress
# or
pnpm add --save-dev @replayio/cypress
# or
bun add --dev @replayio/cypress
```
### Step 3: Install the Replay Browser
```sh
npx replayio install
```
This installs the Replay Chromium browser required for recording.
### Step 4: Store the API Key
The API key must be available as the `REPLAY_API_KEY` environment variable. Save it in a `.env` file at the project root:
```
REPLAY_API_KEY=<your_api_key>
```
Alternatively, export it directly:
```sh
export REPLAY_API_KEY=<your_api_key>
```
### Step 5: Configure the Cypress Support File
Add the Replay support import to `cypress/support/e2e.js` (or `e2e.ts`):
**CommonJS:**
```js
require('@replayio/cypress/support')
```
**ESM:**
```js
import '@replayio/cypress/support'
```
### Step 6: Configure cypress.config.js (or cypress.config.ts)
Add the Replay plugin to the Cypress config:
```js
const { defineConfig } = require('cypress')
const { plugin: replayPlugin, wrapOn } = require('@replayio/cypress')
require('dotenv').config()
module.exports = defineConfig({
e2e: {
setupNodeEvents(cyOn, config) {
const on = wrapOn(cyOn)
replayPlugin(on, config, {
upload: true,
apiKey: process.env.REPLAY_API_KEY,
})
return config
},
},
})
```
For TypeScript (`cypress.config.ts`):
```ts
import { defineConfig } from 'cypress'
import { plugin as replayPlugin, wrapOn } from '@replayio/cypress'
import 'dotenv/config'
export default defineConfig({
e2e: {
setupNodeEvents(cyOn, config) {
const on = wrapOn(cyOn)
replayPlugin(on, config, {
upload: true,
apiKey: process.env.REPLAY_API_KEY,
})
return config
},
},
})
```
### Step 7: Run Tests with Replay
```sh
npx cypress run --browser replay-chromium
```
Recordings are automatically uploaded and a URL is provided for each recording to view in Replay DevTools.
## Important Notes
- The `upload: true` option in the plugin config enables automatic upload after tests complete.
- The `wrapOn` wrapper is required — it wraps the Cypress `on` event handler so Replay can hook into test lifecycle events.
- Cypress events (test starts, commands, assertions) appear in the Replay DevTools timeline.
- For CI/CD, set the `REPLAY_API_KEY` as a secret environment variable in your CI provider.
### Debugging your recorded application
**Run Replay MCP Server to debug your recored application**
to install the MCP server in Claude, run the following command:
```
claude --mcp-config "{
"mcpServers": {
"replay": {
"type": "http",
"url": "https://dispatch.replay.io/nut/mcp",
"headers": {
"Authorization": "${REPLAY_API_KEY}"
}
}
}
}"
```Related Skills
replay-playwright
Set up and run Playwright tests with Replay Browser to record test executions for debugging and performance analysis.
replay-mcp
Use Replay MCP to inspect the contents of https://replay.io recordings.
replay-cli
Record your application to gather performance data and debug issues. It enables users to install Replay ClI, record a session, upload and manage them.
render-daily-replay
Auto-render a Remotion video replay of a Nums game on Mainnet. Resolves the target `gameId` from Torii (best reward of the day OR best score of the day, OR a specific gameId the user provides), silently auto-fetches the current NUMS price from Ekubo, then runs `pnpm remotion:render:game` with the right props. Use when the user asks to render today's top game, the daily winner, the biggest reward, the highest score, or any specific gameId, without having to assemble the render command by hand.
nums-remotion-replay
Project-specific skill for the Nums Remotion package that generates game replay videos by reusing the existing client React components. Covers the cross-package webpack setup, client-component overrides, Torii data fetching, font loading, render flow quirks, and hosting. Use when working on `remotion/` or the `SlidingNumber` component, adding new compositions, debugging font/animation issues, or setting up hosting for the Remotion Studio. Pairs with the generic `remotion-best-practices` skill.
posthog-replay-analysis
Decode and analyse PostHog session replay recordings programmatically via the API. Use when investigating a user-reported incident (crash, infinite loop, unexpected navigation) where a PostHog session replay exists, and you want to extract the URL sequence, network request timeline, console logs, or DOM state WITHOUT opening the replay UI. Especially valuable when diagnosing iOS Safari/WebKit crashes ("A problem repeatedly occurred"), request storms, or any bug where the replay UI can't be scripted. Bypasses the broken `rrvideo` npm packages with a direct decode-and-chart approach.
cypress
Cypress end-to-end testing for web apps. Use for E2E testing.
proxy-replay
Replay recorded HTTP/HTTPS traffic using dev-proxy-recorder. Covers starting replay mode, selecting sessions, miss handling, and switching between record and replay.
VibeCollab — Setup Instructions for AI Assistants
You are helping a user set up VibeCollab in their project.
raycast-extension-docs
Guidance for building, debugging, and publishing Raycast extensions using the Raycast documentation set. Use when Codex needs to create or modify Raycast extensions (React/TypeScript/Node), consult Raycast API reference or UI components, build AI extensions, handle manifest/lifecycle/preferences, troubleshoot issues, or prepare/publish extensions to the Raycast Store or Teams.
evomap
Connect to the EvoMap collaborative evolution marketplace. Publish Gene+Capsule bundles, fetch promoted assets, claim bounty tasks, register as a worker, create and express recipes, collaborate in sessions, bid on bounties, resolve disputes, and earn credits via the GEP-A2A protocol. Use when the user mentions EvoMap, evolution assets, A2A protocol, capsule publishing, agent marketplace, worker pool, recipe, organism, session collaboration, or service marketplace.
maestro
Intelligent skill knowledge gateway. Routes tasks to the right knowledge without loading all skills into context. MUST be consulted before any coding task — call the search_skills MCP tool to retrieve relevant expertise from 100+ indexed skills covering Swift, SwiftUI, concurrency, testing, architecture, performance, and security.