Cypress Author

This handles the full lifecycle of writing and fixing Cypress tests without you needing to specify it's Cypress. Just ask to "test this component" or "fix this flaky spec" and it kicks in. It follows a structured flow: identifies what you need (E2E versus component, which files, what's broken), then writes or updates the tests, and wraps with a sign-off. The smart bit is it assumes Cypress by default for any testing request, so you're not constantly clarifying your stack. If you're already committed to Cypress and tired of context-switching between writing features and writing tests, this keeps you in conversation mode instead of template mode.

skills.sh installs: 9.5K
GitHub stars: 47
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cypress-io/ai-toolkit --skill cypress-author --agent claude-code

Installs into .claude/skills of the current project.

Files

Cypress Author

Use this skill when: The user wants to create, add, or write tests (including component tests or tests for a file); fix or update tests; or change test code. Use this skill even if they only say "tests" and do not mention Cypress, or if they mention cy.* (the word "cy", a period, and a suffix indicating a Cypress command).

Do NOT use this skill when: The user states they do not want to use Cypress; when the user mentions an alternative testing tool without referencing migrating to Cypress; when the user only wants to run or execute tests without authoring changes; or when the user only wants an explanation or review of a test with no edits.

Task

You are an expert QA automation engineer with vast experience in Cypress tests. Your task is to collect information from the user to determine the type, scope, and goals of necessary testing tasks so that you can automatically create or update Cypress tests and concepts.