sk-e2e

Name: sk-e2e
Availability: InStock
Author: TimeKast

Orchestrate Playwright E2E runs with isolated Neon branches and per-role auth sessions.

Updated May 19, 2026

Search Tags:#rbac #nextjs #playwright #e2e testing #test stability #auth setup #neon db

Ready to run

npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sk-e2e
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-e2e
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents flaky end-to-end tests by providing a kit-shipped Playwright infrastructure that runs against an isolated Neon database branch and generates per-role authenticated sessions automatically.

Core Features & Use Cases

Neon branch isolation per run: Creates an isolated Neon branch for the duration of the E2E run and cleans it up afterward to avoid cross-run state bleed.
Per-role auth session bootstrapping: Runs a dedicated setup project that creates users for every role and writes storageState files consumed by specs.
SSOT-driven RBAC coverage: Automatically expands RBAC route tests from ROUTE_ACL × ROLES, with structural skipping when ACL is empty.
Stability guardrails for Next.js: Enforces hydration-aware waits and recommends semantic selectors and deterministic test data patterns to reduce flakes.

Quick Start

Ask the AI to create or update Playwright E2E specs using the kit runner so your tests reuse tests/e2e/auth.setup.ts storage states and automatically validate RBAC from ROUTE_ACL.

Frequently Asked Questions about sk-e2e

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

FAQPage Schema

How do I stop flaky Playwright E2E tests in Next.js?▼

Flaky Playwright E2E tests are stabilized by running against isolated Neon database branches and enforcing hydration-aware waits with semantic selectors to prevent cross-run state bleed and timing issues.

How do I set up per-role authenticated sessions for Playwright specs?▼

Per-role authenticated sessions are bootstrapped using a dedicated auth setup project that creates users for every role and writes storageState files consumed by subsequent Playwright specs.

How do I automate RBAC route access testing in Next.js App Router?▼

RBAC route access testing is automated by parametrizing Playwright specs over ROUTE_ACL and ROLES, with structural skipping applied when the route access control list is empty.

Does this Playwright E2E runner work with Neon database branching?▼

Yes, the runner orchestrates Playwright E2E by creating an isolated Neon database branch for the duration of the run and automatically cleaning it up afterward to ensure test isolation.

Why do my Next.js E2E tests fail during hydration?▼

Next.js E2E tests fail during hydration due to timing mismatches; applying hydration-aware waits and deterministic test data patterns before interacting with selectors resolves these flakes.