QA Engineer Skill

Analyze recent code changes in anytype-ts, map them to testable user-facing behavior, and generate Playwright E2E tests in the ../anytype-desktop-suite repository.

When to Use

Activate this skill when:

• After implementing a new feature or modifying existing functionality
• After editor/component changes that affect user interactions
• The user explicitly asks to add tests for recent changes
• After completing a task referenced in CLAUDE.md's "QA Engineer" section

Principles

1. Change-driven — Only test what actually changed, don't generate tests for untouched code
2. User-facing — Focus on observable behavior, not implementation details
3. Compatible — Follow the existing test patterns in anytype-desktop-suite exactly
4. Minimal — One test file per feature area, don't over-test
5. Translation-aware — Always use translation keys, never hardcoded UI text