test-forge

Designs, writes, and debugs TypeScript unit, integration, and Playwright E2E test suites.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill test-forge-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-forge
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/test-forge
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill test-forge-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing and maintaining reliable test suites is hard: flaky tests, brittle selectors, and unclear coverage gaps erode trust in CI. This Skill acts as a senior test engineer that designs test strategies, authors Vitest and Playwright tests, and systematically debugs failures so suites stay fast, deterministic, and maintainable. ## Core Features & Use Cases - Test Strategy & Mapping: Builds a test pyramid per feature, defining what to test, fixtures, data strategy, and CI tiers (smoke vs full). - Authoring Standards: Writes Vitest unit tests with AAA structure, integration tests validating contracts across boundaries, and Playwright E2E tests using role-based locators, fixtures, and Page Object Models. - Systematic Debugging: Uses Playwright UI Mode, Inspector, Trace Viewer, and structured console breadcrumbs to triage flaky or failing tests, producing root-cause statements and prevention fixes. - Use Case: Ask it to "Add E2E test for the checkout flow" and it produces a Playwright test with proper fixtures, stable locators, failure artifacts, plus TEST_REPORT.md and TEST_DESIGN.md documentation. ## Quick Start Ask the assistant to add unit tests for a specific file or to debug a flaky Playwright test by name.

Frequently Asked Questions about test-forge

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

FAQPage Schema
How do I write Playwright E2E tests in TypeScript?▼

Playwright E2E tests in TypeScript use built-in locators like getByRole, getByLabel, and getByText with web assertions that auto-wait for actionability. Use fixtures to isolate setup and Page Object Models for large suites to keep selectors maintainable.

How to debug a flaky Playwright test?▼

Debug flaky Playwright tests systematically using UI Mode for time-travel inspection, Trace Viewer for CI-only failures, and targeted console breadcrumbs with a flow, step, and request id. Replace sleep-based timeouts with explicit web assertions to remove nondeterminism.

What is the difference between Vitest unit tests and integration tests?▼

Vitest unit tests cover pure logic like parsing, formatting, and validators using AAA structure and fake timers. Integration tests validate contracts across boundaries such as API handlers and database adapters, checking error mapping, retries, and idempotency with real dependencies where feasible.

Should I use Vitest or Playwright for testing?▼

Use Vitest for unit and integration tests of TypeScript logic, API handlers, and multi-module flows. Use Playwright Test for end-to-end coverage of 1-3 critical user journeys per feature where real browser behavior matters.

Why are my E2E tests flaky and how do I fix them?▼

Flakiness usually comes from sleep-based timeouts, brittle CSS selectors, shared state, or nondeterministic data. Fix it by using auto-waiting locators, test fixtures for isolation, stable test data, and retries only as a last resort rather than to hide real issues.