cypress-docs

Search the /api/commands/ section of docs.cypress.io, preferably via the /llm/* markdown endpoints listed in /llms.txt. Extract the syntax, required arguments, optional options, return behavior, and an official example for the command.

Use cy.intercept to stub and spy on network requests. The skill classifies this as an API/network query, searches the intercept documentation, and returns the syntax, usage examples, and relevant notes from official docs.

Yes. docs.cypress.io publishes /llms.txt, and every page has an optimized markdown version under /llm/, for example /llm/markdown/app/faq.md. These are cleaner and easier to parse than HTML pages.

The skill states that the claim could not be verified in Cypress documentation and offers the closest supported alternative if one exists. It never invents APIs, syntax, or behavior.

Queries containing errors are routed first to /references/error-messages/ in the official docs, then expanded to guides and API documentation if needed. This ensures troubleshooting answers match documented error behavior.

Use documentation lookup whenever correctness depends on official sources, such as exact signatures, defaults, deprecated APIs, or version differences. For writing or fixing tests without doc lookups, a test-authoring skill is more appropriate.