cypress-test-agent

Generate Cypress tests with data-testid locators via a four-step interview.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill cypress-test-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cypress-test-agent
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/cypress-test-agent
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill cypress-test-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates framework-aligned Cypress tests by orchestrating a 4-step interview and a temporary inline scraper to discover real data-testid locators.

Core Features & Use Cases

  • Four-step test authoring: Confirm, Navigate, Assert, Build → Run → Fix → Clean to produce deterministic Cypress tests.
  • Inline locator discovery: Injects a temporary scraper to extract live locators, then strips it before commit for a clean codebase.
  • Framework-driven orchestration: Uses the project’s framework profile to determine navigation, selectors, stop points, and viewport handling.
  • Desktop & Mobile parity: Outputs test scaffolds for both desktop and mobile paths, with locator outputs and drift-detection guidance.

Quick Start

Describe your test scenario and I will generate a Cypress test skeleton that follows the framework’s navigation, uses the scraper to collect locators, and creates ready-to-run desktop and mobile tests.

Frequently Asked Questions about cypress-test-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Cypress tests using real data-testid locators from my web pages?

Generating Cypress tests with real data-testid locators is done by injecting a temporary inline scraper to extract live selectors, which is then removed before commit to ensure a clean codebase.

What is the process for creating framework-aligned Cypress tests for new user journeys?

Creating framework-aligned Cypress tests involves a 4-step interview process: Confirm, Navigate, Assert, and Build, using your project's framework profile to determine navigation, selectors, and stop points.

Can I output separate Cypress test scaffolds for both desktop and mobile paths?

Yes, you can output separate desktop and mobile Cypress test scaffolds, providing locator outputs and drift-detection guidance for both viewport paths based on your project framework profile.

How do I automate Cypress test creation for multi-step flows and dynamic pages?

Automating Cypress tests for multi-step flows and dynamic pages uses a temporary scraper to discover live locators and applies your framework profile to produce fully wired, deterministic tests.

Do I need a project framework profile to generate Cypress tests with this approach?

Yes, a project framework profile is required because it determines the navigation, selectors, stop points, and viewport handling needed to produce deterministic and fully wired Cypress tests.