cypress-author

cypress-io/ai-toolkit

Creates, updates, and fixes Cypress tests for E2E and component testing.

What is cypress-author?

Cypress Author is a skill for authoring, updating, and fixing Cypress tests (both end-to-end and component tests). Use it when you need to create new tests, add tests to existing files, update test code, or fix failing or flaky tests—even if you don't explicitly mention Cypress.

Creates new Cypress test specs (E2E and component tests)
Updates and modifies existing test code
Fixes failing or flaky tests
Adds tests to existing files or components
Handles test authoring without requiring explicit Cypress terminology

How to install cypress-author

npx skills add https://github.com/cypress-io/ai-toolkit --skill cypress-author

Prerequisites

Cypress installed in your project
Read and Edit tool access to project files

Claude Code

Cursor

Windsurf

Cline

How to use cypress-author

1.Describe the testing task you need (create, update, or fix tests)
2.Provide context about what needs to be tested (file, component, or workflow)
3.The skill will identify task requirements following its structured flow
4.The skill will execute test authoring based on your specifications
5.Review the generated or updated test code

Use cases

Good for

Create E2E tests for a new user workflow
Add component tests for a React component
Fix a flaky test that intermittently fails
Update tests when application code changes
Write tests for a file when asked generically to 'test this'

Who it's for

QA automation engineers
Frontend developers writing tests
Teams using Cypress for testing
Anyone needing to create or modify test code

cypress-author FAQ

Do I need to mention 'Cypress' explicitly?

No. The skill applies even if you just say 'create tests for this file' or reference Cypress commands like cy.* without saying 'Cypress'.

When should I use cypress-explain instead?

Use cypress-explain when you only want to review or understand existing tests without making code changes. Use cypress-author when you need to create, update, or fix test code.

What types of tests can this skill create?

This skill creates both E2E (end-to-end) tests and component tests using Cypress.

What if my test is failing or flaky?

Provide details about the failure or flakiness, and the skill will help diagnose and fix the issue in your test code.

What tools does this skill have access to?

The skill has Read and Edit access to your project files, allowing it to create and modify test code.

Full instructions (SKILL.md)

Source of truth, from cypress-io/ai-toolkit.

name: cypress-author description: "Creates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code." model: inherit background: false allowed-tools: Read, Edit metadata: version: 1.0.1

Cypress Author

Use this skill when: The user wants to create, add, or write tests (including component tests or tests for a file); fix or update tests; or change test code. Use this skill even if they only say "tests" and do not mention Cypress, or if they mention cy.* (the word "cy", a period, and a suffix indicating a Cypress command).

Do NOT use this skill when: The user states they do not want to use Cypress; when the user mentions an alternative testing tool without referencing migrating to Cypress; when the user only wants to run or execute tests without authoring changes; or when the user only wants an explanation or review of a test with no edits.

Task

You are an expert QA automation engineer with vast experience in Cypress tests. Your task is to collect information from the user to determine the type, scope, and goals of necessary testing tasks so that you can automatically create or update Cypress tests and concepts.

Mandatory flow (do not skip)

You MUST complete the following steps in order. Do not skip structured identification: follow task.md before diving into implementation-only reading; you MUST run the full flow below.

Identify — Read and follow ./subskills/task.md; determine the necessary information (task, spec, test, type, instructions) as specified there.
Execute — Read and follow ./subskills/author.md using the determined task data.
Sign-off — End your response with a clear sign-off (e.g. "Thank you for using Cypress!"). Do not omit this for brevity.

Do not proceed when required data is missing; prompt the user for the missing information first, then re-run the skill if needed.

Conclusion

You MUST end your response with a clear sign-off (e.g. "Thank you for using Cypress!") so it stands out. In a long conversation with multiple turns, one sign-off at the end of the flow is sufficient.