test-conventions

Standardize TypeScript monorepo test conventions with Vitest and React Testing Library.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/feraudet/ssii --skill test-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-conventions
Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/test-conventions
Command: npx skills add https://github.com/feraudet/ssii --skill test-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests conventions are standardized for a TypeScript monorepo project to ensure consistency and quality across backend and frontend tests.

Core Features & Use Cases

  • Framework recommendations: Vitest for backend, React Testing Library for frontend.
  • File structure and naming conventions for unit and integration tests.
  • Use Case: when adding new components or services, apply these conventions to maintain uniformity.

Quick Start

Apply these conventions to create and organize tests for new and existing code.

Frequently Asked Questions about test-conventions

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

FAQPage Schema
How do I standardize testing conventions in a TypeScript monorepo?

Standardize testing in a TypeScript monorepo by specifying frameworks like Vitest and React Testing Library, defining file layouts, and enforcing naming patterns for unit and integration tests across backend and frontend directories.

What is the best way to structure unit and integration tests in a monorepo?

Structure unit and integration tests by applying consistent file layout and naming patterns across backend and frontend directories, ensuring uniform test quality and organization throughout the TypeScript monorepo.

Does this testing convention work with Vitest and React Testing Library?

Yes, these testing conventions specifically recommend Vitest for backend tests and React Testing Library for frontend tests to ensure consistent quality and framework alignment across the monorepo.

When do I need standardized test naming conventions for frontend and backend?

You need standardized test naming conventions when adding new components or services to the monorepo, applying these patterns to maintain uniformity and consistent test quality across existing and newly developed code.

Can I use these testing conventions to set coverage targets for my project?

Yes, you can use these conventions to specify coverage targets for your project, ensuring that both backend and frontend tests meet consistent quality benchmarks across the entire TypeScript monorepo.