Enable the agent to retrieve accurate, up-to-date, and verifiable information about the Cypress testing framework by prioritizing official documentation and structured sources.
When to use
Apply this skill whenever the task depends on
finding, reading, or quoting Cypress documentation
rather than general testing intuition:
Look up facts
commands, APIs, assertions, lifecycle hooks, configuration options, environment variables, CLI flags, plugins, or TypeScript types as documented by Cypress.
Confirm behavior
how something works in a given Cypress version, E2E vs component testing differences, browser support, or networking/cy.intercept semantics.
Before asserting “Cypress can/cannot…”
search docs first; do not rely on memory for exact signatures, defaults, or deprecated APIs.
Extract structured content
follow the LLM-optimized docs strategy below (
llms.txt
,
/llm/*
) when fetching or summarizing doc pages.
Ground answers for others
when explaining Cypress to a user, writing examples, or reviewing code where correctness must match official docs.
If the user only needs
writing or fixing tests
without a documentation lookup, prefer
cypress-author
; if they only need
test explanation
without fetching docs, prefer
cypress-explain
. Use
this
skill when official documentation is the source of truth.
Source Prioritization
Show more
Installs
429
Repository
cypress-io/ai-toolkit
GitHub Stars
27
First Seen
May 7, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Warn