agentsclimarketplace
Sign in

E2e playwright

Skill soden46/syarif-laravel-ai-skills/skills/e2e-playwright

Laravel guidance to generic E2E patterns with Playwright-state setup, seeds, test IDs, auth, environment, and Sail integrationFrom its SKILL.md

Install
npx -y skills add soden46/syarif-laravel-ai-skills --skill e2e-playwright

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 352 tokens by cl100k_base, as published. Nobody here has run it

E2e Playwright

Use this skill when a Laravel task involves e2e playwright.

This skill is adapted to the personal Laravel standards in this repository. It maps the public e2e-playwright topic from jpcaparas/superpowers-laravel into the local e2e-playwright catalog without copying third-party skill body text.

Syarif Defaults

  • Follow Laravel conventions before introducing custom abstractions.
  • Prefer project-local patterns when they are explicit and tested.
  • Keep controllers focused on HTTP orchestration.
  • Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
  • Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
  • Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

  1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
  2. Identify the smallest local skill set that overlaps this topic.
  3. Implement or review the change using Laravel-native APIs first.
  4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
  5. Run targeted tests and available quality checks before handoff.

Checkpoints

  • Authorization and validation boundaries are explicit.
  • Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
  • User-facing behavior has feature, unit, browser, or integration tests at the right level.
  • Logs and errors are useful without exposing secrets or unnecessary personal data.
  • Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

  • using-laravel-standards
  • architecture
  • testing
  • security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most e2e browser skills give in 352 tokens

Counted across 408 of the 410 authors here whose files we hold, read 2026-08-07

  • Use page object model patternin 34 of 408, across 24 files
  • Keep tests independentin 24 of 408, across 19 files
  • Interact using refs from the latest snapshotin 24 of 408, across 12 files
  • Snapshot to get element refsin 24 of 408, across 14 files
  • Clean up test data after each testin 20 of 408, across 14 files
  • Test user behavior not implementationin 19 of 408, across 13 files
  • Wait for specific network conditionsin 18 of 408, across 8 files
  • Quarantine flaky tests explicitlyin 18 of 408, across 9 files
  • Re-snapshot after navigation or DOM changesin 17 of 408, across 10 files
  • Detect running dev servers before writing test codein 17 of 408, across 7 files
  • Use web-first assertionsin 17 of 408, across 14 files
  • Ask the user which server to test if multiple are foundin 15 of 408, across 5 files

Said here and by no other author read

  • Follow Laravel conventions before custom abstractions
  • Keep controllers focused on HTTP orchestration
  • Verify behavior with the smallest meaningful tests
  • Detect the Laravel, PHP, and runner versions
  • Identify the smallest local skill set
  • Use Laravel-native APIs first

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.