test-write

Implement Vitest and Playwright test suites for Convex and Next.js 15 applications.

3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/LunchTable-TCG/LTCG --skill test-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-write
Source: https://github.com/LunchTable-TCG/LTCG/tree/main/.claude/skills/test-write
Command: npx skills add https://github.com/LunchTable-TCG/LTCG --skill test-write

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for comprehensive and reliable testing systems that can uncover real bugs in complex applications, specifically targeting issues across backend (Convex) and frontend (Next.js) codebases.

Core Features & Use Cases

  • Comprehensive Test Strategy: Develops a multi-layered testing approach (unit, integration, E2E) tailored to the project's stack.
  • Bug Detection Focus: Creates tests designed to catch specific, high-impact bugs like authentication flaws, race conditions, and data integrity issues.
  • Runnable Test Harness: Implements and configures testing frameworks (Vitest, Playwright) and ensures tests are CI-friendly.
  • Mutation Testing: Proactively injects bugs to validate test effectiveness.
  • Use Case: A senior test engineer uses this Skill to establish a robust testing suite for a new e-commerce platform, ensuring that critical user journeys like checkout and payment processing are thoroughly validated before launch.

Quick Start

Use the test-write skill to create a comprehensive testing strategy and implement runnable test suites for the project.

Frequently Asked Questions about test-write

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a comprehensive testing strategy for Next.js and Convex?

To establish a comprehensive testing strategy for Next.js and Convex, you need a multi-layered approach covering unit, integration, and end-to-end tests. This involves configuring test harnesses to validate backend data integrity and frontend auth flows effectively.

What is the best way to test for race conditions and authentication flaws in web applications?

The best way to test for race conditions and authentication flaws is by writing deterministic, isolation-focused tests. This approach targets specific high-impact bugs by validating concurrency and data integrity across both backend and frontend integration layers.

How do I configure Vitest and Playwright to run CI-friendly E2E tests?

Configuring Vitest and Playwright for CI-friendly E2E tests involves implementing a runnable test harness that ensures deterministic execution. This setup validates critical user journeys and E2E flows while maintaining isolation across the testing environment.

Can I use mutation testing to validate the effectiveness of my E2E and integration tests?

Yes, you can use mutation testing to validate test effectiveness by proactively injecting bugs into the codebase. This process verifies whether your existing unit, integration, and E2E tests can successfully detect and catch the introduced defects.

Does this testing approach support concurrency and data integrity validation for backend systems?

Yes, this testing approach specifically supports concurrency and data integrity validation for backend systems. It writes deterministic tests designed to uncover real bugs related to authentication, race conditions, and data flows within the Convex backend.

Why should I implement mutation testing instead of just writing more E2E tests?

You should implement mutation testing because it proactively validates test effectiveness by injecting bugs, ensuring your suite catches real defects. Simply adding more E2E tests increases coverage but does not guarantee the tests fail when high-impact bugs are introduced.