Testing Rules

Name: Testing Rules
Availability: InStock
Author: taikiwt

Enforce AI-TDD testing rules for monorepo API, extension, and UI layers.

Updated Jan 27, 2026

Search Tags:#vitest #testing #monorepo #playwright #msw #ai-tdd

Ready to run

npx skills add https://github.com/taikiwt/sitecue --skill testing-rules-taikiwt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Testing Rules
Source: https://github.com/taikiwt/sitecue/tree/main/.agent/skills/testing
Command: npx skills add https://github.com/taikiwt/sitecue --skill testing-rules-taikiwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-TDD in monorepos often suffers from drifting testing strategies and inconsistent mocks; this skill codifies and enforces a unified set of testing rules across API, extension, and UI layers.

Core Features & Use Cases

Standardized test stacks for API, extension, and E2E tests, with clear tooling guidance (bun test for API, vitest + React Testing Library + jsdom for UI on web, Playwright for E2E).
MSW-based mocking guidelines to ensure deterministic network behavior in UI tests and to avoid flaky tests.
Monorepo-specific guardrails such as test file placement, naming conventions, and configuration checks to prevent drift across packages.

Quick Start

Add the prescribed testing configurations across all packages and enable the Playwright webServer integration to ensure reliable end-to-end tests.

Frequently Asked Questions about Testing Rules

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

FAQPage Schema

How do I enforce consistent AI-TDD testing rules across a monorepo?▼

To enforce consistent AI-TDD testing rules across a monorepo, you need codified guardrails for test file placement, naming conventions, and configuration checks to prevent strategy drift across different packages. This ensures unified testing discipline.

What's the best way to standardize test stacks for API, extension, and E2E layers?▼

Standardize test stacks by assigning specific tooling per layer: use bun test for APIs, vitest with React Testing Library and jsdom for web extensions, and Playwright for application end-to-end testing to ensure reliable coverage.

How do I avoid flaky tests when mocking network requests in vitest?▼

To avoid flaky tests when mocking network requests in vitest, implement MSW-based mocking with strict file naming and placement conventions to ensure deterministic network behavior across your UI tests.

Do I need to configure Playwright webServer integration for reliable E2E tests in a monorepo?▼

Yes, configuring Playwright webServer integration is required for reliable E2E tests in a monorepo, as it ensures stable server startup and teardown across packages to prevent end-to-end test failures.

Why does my monorepo testing strategy drift across different packages?▼

Your monorepo testing strategy drifts across packages due to inconsistent mocks and lacking codified rules for test stacks, file placement, and MSW mocking conventions, which requires enforcing unified guardrails to resolve.