new-e2e

Scaffold Playwright E2E test files with helpers and strict selectors.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/wordshepherd/colophony --skill new-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-e2e
Source: https://github.com/wordshepherd/colophony/tree/main/.claude/skills/new-e2e
Command: npx skills add https://github.com/wordshepherd/colophony --skill new-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of new Playwright end-to-end tests, ensuring consistency and adherence to best practices in your testing suite.

Core Features & Use Cases

  • Test File Generation: Creates new .spec.ts files in the correct directory (apps/web/e2e/).
  • Helper Integration: Automatically imports and utilizes existing authentication, API client, and database helpers.
  • Pattern Enforcement: Enforces strict selector patterns (role-based, scoped) and preferred navigation/interaction methods.
  • Use Case: When developing a new feature, use this Skill to quickly scaffold its corresponding E2E test file, pre-configured with necessary setup and best practices, allowing you to focus on writing test logic.

Quick Start

Use the new-e2e skill to scaffold a Playwright E2E test for the 'user-profile' feature.

Frequently Asked Questions about new-e2e

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

FAQPage Schema
How do I scaffold Playwright E2E tests with strict selectors and helper integration?

To scaffold Playwright E2E tests, use this tool to generate new `.spec.ts` files in the `apps/web/e2e/` directory. It automatically integrates authentication and API helpers while enforcing role-based selector patterns for consistent test creation.

What is the best way to generate Playwright test files with role-based selectors?

The best way to generate Playwright test files with role-based selectors is by using this scaffolding tool. It enforces strict, scoped selector patterns and applies best practices for user authentication and page navigation directly within the generated test files.

Does this Playwright test generator prefer API setup over UI interactions for test data?

Yes, this Playwright test generator prefers API and database setup over UI interactions for test data. It automatically integrates API client and database helpers to establish test prerequisites efficiently without relying on UI-driven data creation.

Can I use this tool to scaffold E2E tests for user authentication and data assertions?

Yes, you can use this tool to scaffold E2E tests for user authentication and data assertions. It ensures proper setup for authentication, page navigation, and data assertions by importing existing authentication and API helpers into the generated test files.

Why does my Playwright test scaffolding need to target the apps/web/e2e/ directory?

Playwright test scaffolding targets the `apps/web/e2e/` directory to ensure proper setup and consistent file organization. This strict placement guarantees that generated test files correctly import and utilize the existing project authentication, API, and database helpers.