القائمة
Validate product changes against requirements using emulator-backed integration tests, regression checks, and release signoff criteria. Use when reviewing features, writing QA plans, expanding tests, or deciding ship readiness.
Validate whether a proposed or shipped feature fits the product, solves a meaningful user problem, and stays differentiated from existing surfaces. Use when reviewing overlap between features, checking product market fit, challenging roadmap ideas, evaluating retention or adoption risk, or pressure-testing new UX against the current product.
Validate whether a proposed or shipped feature fits the product, solves a meaningful user problem, and stays differentiated from existing surfaces. Use when reviewing overlap between features, checking product market fit, challenging roadmap ideas, evaluating retention or adoption risk, or pressure-testing new UX against the current product.
Implement approved product work across UI, API routes, shared libraries, and tests using this repo's feature packet and architecture conventions. Use when building features, integrating Firebase-backed flows, or coordinating delivery with PM and QA docs.
Drive feature requirements, scope, acceptance criteria, and cross-role handoff for this repo. Use when reviewing product gaps, writing PRDs, choosing MVP scope, defining success metrics, or synchronizing PM, engineering, and QA around a feature.
Standardize Firebase integration for this project across client SDK, Admin SDK, auth/session flows, Firestore usage, and environment variables. Use when adding or modifying Firebase auth, Firestore reads/writes, API routes touching Firebase, or Firebase-related setup.
Implement and maintain Gemini-powered question generation in this project using shared prompt, Zod parsing, model configuration, and robustness checks. Use when editing quiz generation, embeddings, Gemini API calls, prompt logic, or related API routes.
| name | qa-engineer |
| description | Validate product changes against requirements using emulator-backed integration tests, regression checks, and release signoff criteria. Use when reviewing features, writing QA plans, expanding tests, or deciding ship readiness. |
Use this skill when you need to:
Read these first:
docs/product/<feature>/PRD.mddocs/product/<feature>/IMPLEMENTATION.mddocs/product/<feature>/QA.mdThen use:
integration-testingintegration-standardstests/integration/ for API-backed features.Use this order:
setAuthedUser(...) in integration tests.Request objects.Do not: