By cypress-io
AI-power Cypress testing: create, update, fix E2E and component tests from natural requests; explain, review, and search official docs; connect to Cypress Cloud for test runs, results, and suite management.
npx claudepluginhub cypress-io/ai-toolkit --plugin cypressCreates, 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.
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
Explains Cypress tests (E2E and component tests), and answers questions about Cypress use and behavior. Use when the user asks to explain how a test works, explain how Cypress works, review or critique a test without writing code. Apply even when the user does not say 'Cypress' (e.g. 'explain this test'). Prefer the cypress-author skill when the user wants to create, fix, or update tests.
Open-source Cypress AI skills, built by the Cypress team. Works with Claude, Cursor, GitHub Copilot, and more.
Your AI tool is capable. It just does not know Cypress the way you do. The toolkit fixes that with skills, context, and guidance built by the team that built Cypress.
Cypress also ships AI capabilities in the App and Cypress Cloud - such as cy.prompt(), Studio AI, Cloud MCP, Test Intent and Error Summaries, and UI Coverage test generation. Learn more in the Cypress AI documentation.
AI tools can work with Cypress. What they struggle with is applying it consistently and correctly.
Without guidance, AI tools fall back on generic patterns — underusing the Cypress API, misapplying selectors, skipping best practices that experienced Cypress developers internalize over time. The result is output that technically runs but that you can't rely on.
The Cypress AI Toolkit gives your AI tools the Cypress-specific context they need to produce output you can actually build on — consistently, across your team and your workflows.
Skills are instruction sets your AI tool loads to apply Cypress-specific knowledge when generating or reviewing test code. They fill the gap between what an AI learned during training and what current, well-written Cypress tests actually look like.
Three skills are available now:
cypress-author — Improves how AI tools create, update, and fix Cypress tests. Use it when you're writing new tests or fixing broken ones.cypress-explain — Helps you understand, describe, and critique existing tests. Use it when auditing a suite, onboarding a new team member, or investigating a brittle test before rewriting it.cypress-docs - Helps your agent research and retrieve information about Cypress more efficiently and reliably.Skills work with any AI tool that accepts custom instructions, including Claude, Cursor, and GitHub Copilot.
See the skills documentation for installation instructions, example prompts, and troubleshooting.
We're building toward a broader toolkit.
The community will help shape what gets prioritized. If you're already unlocking AI-powered Cypress workflows, we want to hear how. Open an issue or open a PR.
The Cypress AI toolkit is published as a plugin for both Claude and Cursor. This is the easiest way to install and configure the various capabilities in this package and also enables an auto-update capability.
Note: Listings in the Claude and Cursor official plugin marketplaces are currently pending. This README will be updated once they are available. Until then, this repository can be cloned and installed as a local plugin in your agent of choice.
If you're using another agent or prefer to pick-and-choose you can pick the portions of this repository you want.
Install the skills using the skills package:
npx skills add cypress-io/ai-toolkit
Prompt your AI tool as you normally would. The skills will activate automatically when relevant, or invoke one directly with a slash command (e.g. /cypress-author).
For manual installation, example prompts, and more, see the skills documentation or the Cypress AI Skills docs.
This toolkit is for Cypress developers who use AI coding tools and want consistent, reliable output — not just code that runs.
It's the right fit if you want your AI tool to:
You do not need AI expertise to use it. You need Cypress and an AI coding tool.
We welcome contributions of all kinds: new skills, improvements to existing ones, bug reports, and ideas.
If you've built something that makes AI tools smarter about Cypress, this is the right place to share it.
Read the contributing guide to get started.
End-to-end test execution and recording for web applications
End-to-end test automation with Playwright, Cypress, and Selenium for browser-based testing
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
Comprehensive Cypress testing framework skills for end-to-end testing of web applications with custom commands and CI/CD integration.
End-to-end testing with Playwright: browser automation, test generation, and UI testing
External network access
Connects to servers outside your machine
Share bugs, ideas, or general feedback.
Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim