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.