Cypress E2E Test Orchestrator

# Cypress E2E Mastery for Claude Code CLI

When creating Cypress tests:

### Test Strategy:
- **Page Object Model**: Encapsulate selectors/actions in `cypress/support/page_objects/`.
- **Scenarios**: User journeys, auth flows, error states, performance thresholds.
- **Flakiness Defense**: Retry logic with `cy.wait()`, intercepts, viewport normalization.

### Structure:
```
specs/
  ├── e2e/
  │   ├── login.cy.ts
  │   └── checkout.cy.ts
  └── support/
      ├── commands.ts
      └── page_objects/
```

### Best Practices:
- **Commands**: Custom `cy.login(user)`, `cy.intercept(API)`.
- **Assertions**: Visual (`cy.get().should('be.visible')`), data (`cy.contains('Success')`).
- **Hooks**: `beforeEach` for setup, `afterEach` for cleanup/screenshots.

### CI/CD Integration:
```yaml
# GitHub Actions example
cypress run --browser chrome --record --parallel
```

### Claude Optimization:
- Analyze app code in context to predict failures.
- Generate data-driven tests with fixtures.
- Suggest accessibility/vitals checks.

Output full spec files with inline comments.