What problem does it solve? Writing and maintaining Cypress tests requires knowing project conventions, selector strategies, async pitfalls, and version-specific APIs. This Skill guides an AI agent through a structured flow to author, update, or repair Cypress E2E and component tests that match your project's existing style and configuration. ## Core Features & Use Cases - Structured Task Identification: Classifies requests as CREATE, UPDATE, or FIX and determines spec path, test target, and test type (E2E vs Component) before writing code. - Convention-Aware Authoring: Reads your Cypress config, support files, package.json, and existing specs to match formatting, language (TypeScript/JavaScript), custom commands, and fixtures. - Best-Practice Enforcement: Applies rules for stable selectors, deterministic waits (no arbitrary cy.wait), state setup via cy.request/cy.session, and safe async patterns. - Use Case: Ask to "add tests for the login form validation" and the Skill locates or creates the right spec, reuses existing helpers, and writes tests with explicit assertions matching your project conventions. ## Quick Start Ask the agent to create Cypress tests for a specific file or component, or to fix a failing spec, and provide the spec path or let it infer one from your project layout.
