create-e2e-test

Create Playwright E2E test specs with structured templates and helpers.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill create-e2e-test-camilopiedra92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-e2e-test
Source: https://github.com/camilopiedra92/YNAB-Clone/tree/main/.agent/skills/create-e2e-test
Command: npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill create-e2e-test-camilopiedra92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often duplicate boilerplate when adding new Playwright E2E tests, leading to inconsistent auth flows, navigation, and isolation handling. This skill provides a structured template and best practices to create reliable specs with project-specific helpers.

Core Features & Use Cases

  • Structured workflow for adding new Playwright E2E specs with project-specific auth, navigation, and isolation patterns.
  • Reusable helpers: use e2e-helpers.ts to navigate and inspect app state, ensuring deterministic tests.
  • Reference examples: adapt annotated samples (examples/example.spec.ts, examples/isolation.spec.ts) to cover common scenarios like auth and tenant isolation.

Quick Start

Create a new spec under tests/ using the provided template, and hook in the e2e-helpers and auth setup.

Frequently Asked Questions about create-e2e-test

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

FAQPage Schema
How do I standardize Playwright E2E tests with auth and helpers?

Standardize Playwright E2E tests by using a structured template that provides reusable e2e-helpers for navigation and explicit auth setup, ensuring consistent and deterministic test specs across your team.

What's the best way to reduce boilerplate in Playwright test creation?

Reduce Playwright test boilerplate by adapting annotated reference examples like example.spec.ts and isolation.spec.ts, which provide example-driven conventions for common scenarios like auth and tenant isolation.

How do I handle test isolation patterns in Playwright E2E specs?

Handle Playwright E2E test isolation patterns by adapting the provided isolation.spec.ts reference example, which demonstrates best practices for maintaining deterministic tests and navigating app state safely.

Can I use this E2E test template with existing project-specific auth flows?

Yes, you can adapt the structured E2E test workflow to existing project-specific auth flows by hooking your current auth setup into the provided template and utilizing the e2e-helpers.ts file.

Why do my Playwright E2E tests have inconsistent navigation and auth handling?

Playwright E2E tests often have inconsistent auth and navigation handling due to duplicated boilerplate; applying a structured template with reusable helpers eliminates these variations and standardizes test creation.