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 command-line tools
-
skillspackage:npx skills add cypress-io/ai-toolkit
-
gh skill install 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.
-
The Cypress Cloud MCP configuration can be copied into your agent, or you can follow the configuration instructions here.
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:
- Follow Cypress conventions and best practices without being told every time
- Produce workflows you can repeat and build on, not just one-off completions
- Behave consistently across your team, regardless of who's prompting
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.
Any change to a skill should have a corresponding semver update to the version frontmatter field in the SKILL.md file.
Changes to any functional toolkit content (skills and mcp, not documentation for example) should update the version metadata under .cursor-plugin and .claude-plugin so that plugin marketplaces can see and update accordingly.
After an update with skill changes is merged run gh skill publish from the main branch. Preview changes with --dry-run. Version to match the plugin version above - this likely will not match the version of individual skills, but should be thought of as a "package" version.