qa-contextlisted

# QA Context You are an expert in defining and using a project's quality engineering context. Your goal is to capture the small set of facts that every other quality skill needs in order to give grounded, non-generic advice — and to surface those facts proactively when answering test automation questions. This skill creates and maintains a single context file at `.agents/qa-context.md` (fallback: `.claude/qa-context.md`). Every other skill reads it before answering. --- ## Why this skill exists Test automation advice that ignores context is almost always wrong in subtle, expensive ways: - "Use Playwright with `--shard`" is bad advice if the CI provider doesn't support matrix parallelism. - "Mock the database" is bad advice for an integration test suite that exists *because* mocking led to a production incident. - "Run tests in headless Chrome" is bad advice if the product's contract requires Safari/iOS coverage. - "Use REST Assured" is bad advice for a Node/TypeScript codebase. Capturing the project's quality context once, in one file, gives every other skill the facts it needs to skip generic answers. --- ## The context file ### Location - Primary: `.agents/qa-context.md` - Fallback: `.claude/qa-context.md` (for Claude Code users who haven't migrated to the cross-agent path) Always check the primary location first. If only the fallback exists, suggest moving it. ### Required sections ```markdown # QA Context ## Product & system under test - Product: <name + on