playwright

Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test selectors, flaky tests, authentication state, API mocking, hydration testing, parallel execution, CI configuration, or debugging test failures.

Ir a la instalación

Repositorio: pproenca/dot-skills
Última actividad en el origen: 14 de mayo de 2026 a las 18:16
Idioma detectado de SKILL.md: inglés
Estrellas: 194
Forks: 17

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/pproenca/dot-skills --skill playwright

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

48 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

Ver todos los de este repositorio

name	playwright
description	Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test selectors, flaky tests, authentication state, API mocking, hydration testing, parallel execution, CI configuration, or debugging test failures.

Playwright + Next.js Testing Best Practices

Comprehensive testing optimization guide for Playwright with Next.js applications. Contains 43 rules across 8 categories, prioritized by impact to guide reliable, fast, and maintainable E2E tests.

When to Apply

Reference these guidelines when:

Writing new Playwright tests for Next.js apps
Debugging flaky or failing tests
Optimizing test execution speed
Setting up authentication state reuse
Configuring CI/CD pipelines for testing
Testing Server Components and App Router features
Reviewing test code for reliability issues

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Test Architecture	CRITICAL	`arch-`
2	Selectors & Locators	CRITICAL	`loc-`
3	Waiting & Assertions	HIGH	`wait-`
4	Authentication & State	HIGH	`auth-`
5	Mocking & Network	MEDIUM-HIGH	`mock-`
6	Next.js Integration	MEDIUM	`next-`
7	Performance & Speed	MEDIUM	`perf-`
8	Debugging & CI	LOW-MEDIUM	`debug-`

Quick Reference

1. Test Architecture (CRITICAL)

arch-test-isolation - Use fresh browser context for each test
arch-parallel-execution - Enable parallel test execution
arch-page-object-model - Use Page Object Model for complex pages
arch-fixtures - Use fixtures for shared setup
arch-test-production - Test against production builds
arch-cleanup-state - Clean up test state after each test

2. Selectors & Locators (CRITICAL)

loc-role-selectors - Use role-based selectors over CSS
loc-data-testid - Use data-testid for dynamic elements
loc-label-selectors - Use getByLabel for form inputs
loc-text-selectors - Use getByText for static content
loc-avoid-xpath - Avoid XPath selectors
loc-chained-locators - Chain locators for specificity
loc-placeholder-selector - Use getByPlaceholder sparingly

3. Waiting & Assertions (HIGH)

wait-web-first-assertions - Use web-first assertions
wait-avoid-hard-waits - Avoid hard waits
wait-network-idle - Use network idle for complex pages
wait-action-retries - Let actions auto-wait before interacting
wait-soft-assertions - Use soft assertions for non-critical checks
wait-custom-timeout - Configure timeouts appropriately

4. Authentication & State (HIGH)

auth-storage-state - Reuse authentication with storage state
auth-multiple-roles - Use separate storage states for different roles
auth-session-storage - Handle session storage for auth
auth-api-login - Use API login for faster auth setup
auth-parallel-workers - Use worker-scoped auth for parallel tests

5. Mocking & Network (MEDIUM-HIGH)

mock-api-responses - Mock API responses for deterministic tests
mock-intercept-modify - Intercept and modify real responses
mock-har-files - Use HAR files for complex mock scenarios
mock-abort-requests - Abort unnecessary requests
mock-network-conditions - Simulate network conditions

6. Next.js Integration (MEDIUM)

next-wait-hydration - Wait for hydration before interacting
next-server-components - Test server components correctly
next-app-router-navigation - Test App Router navigation patterns
next-server-actions - Test server actions end-to-end
next-baseurl-config - Configure baseURL for clean navigation

7. Performance & Speed (MEDIUM)

perf-sharding - Use sharding for large test suites
perf-headless-ci - Use headless mode in CI
perf-browser-selection - Select browsers strategically
perf-reuse-server - Reuse development server when possible
perf-retries - Configure retries for flaky test recovery

8. Debugging & CI (LOW-MEDIUM)

debug-trace-viewer - Use trace viewer for failed tests
debug-screenshots-videos - Capture screenshots and videos on failure
debug-inspector - Use Playwright Inspector for interactive debugging
debug-ci-reporters - Configure reporters for CI integration

How to Use

Read individual reference files for detailed explanations and code examples:

Section definitions - Category structure and impact levels
Rule template - Template for adding new rules

Reference Files

File	Description
AGENTS.md	Complete compiled guide with all rules
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

playwright

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Playwright + Next.js Testing Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Test Architecture (CRITICAL)

2. Selectors & Locators (CRITICAL)

3. Waiting & Assertions (HIGH)

4. Authentication & State (HIGH)

5. Mocking & Network (MEDIUM-HIGH)

6. Next.js Integration (MEDIUM)

7. Performance & Speed (MEDIUM)

8. Debugging & CI (LOW-MEDIUM)

How to Use

Reference Files

Playwright + Next.js Testing Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Test Architecture (CRITICAL)

2. Selectors & Locators (CRITICAL)

3. Waiting & Assertions (HIGH)

4. Authentication & State (HIGH)

5. Mocking & Network (MEDIUM-HIGH)

6. Next.js Integration (MEDIUM)

7. Performance & Speed (MEDIUM)

8. Debugging & CI (LOW-MEDIUM)

How to Use

Reference Files