Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

repo-playwright-e2e-workflow

Sterne17

Forks0

Aktualisiert11. April 2026 um 03:03

Adds and maintains Playwright end-to-end coverage using this repo's local dev-server configuration and test style. Use when writing `e2e/` specs, validating homepage flows, or covering API-backed UI behavior in the browser.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

emzinnia

emzinnia/emzinnia.dev

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	repo-playwright-e2e-workflow
description	Adds and maintains Playwright end-to-end coverage using this repo's local dev-server configuration and test style. Use when writing `e2e/` specs, validating homepage flows, or covering API-backed UI behavior in the browser.

Repo Playwright E2E Workflow

Use this skill when

Adding or editing files in e2e/
Covering a homepage flow, modal, tab set, or editor/debug interaction
Unsure how this repo boots the app for Playwright

Repo-specific setup

Config file: playwright.config.ts
Test directory: e2e
Base URL: http://127.0.0.1:4173
Web server command: npm run dev -- --host 127.0.0.1 --port 4173

Guidelines

Write specs under e2e/ near related flows.
Prefer roles, labels, and visible text before CSS selectors.
Reuse tiny helpers when a setup step repeats, such as enabling debug sections through localStorage.
Keep tests parallel-safe and independent.
Assert user-visible outcomes, not implementation details.

Important repo gotchas

The default Playwright config runs the dev server, not preview.
Dev-only surfaces such as /editor depend on import.meta.env.DEV, so the default config is the correct environment for them.
If a scenario needs a different server mode or env setup, create that intentionally instead of mutating the default flow.

Verification

Run npm run test:e2e for the full suite.
Run a focused Playwright command while iterating, then rerun the closest broader coverage before finishing.

Mehr aus diesem Repository

gleiches Repository

repo-content-markdown-workflow

emzinnia/emzinnia.dev

Maintains article, project, and markdown-backed content flows in this SvelteKit portfolio. Use when editing `src/articles/**`, blog/project routes, `src/lib/articles.ts`, `src/lib/markdown.ts`, content reader panels, or the dev content editor.

2026-04-2717

repo-design-system-catalog

emzinnia/emzinnia.dev

Maintains this repo's UI component library, design page, component documentation registry, and design-system docs. Use when editing `src/lib/components/ui/**`, `src/lib/components/design/**`, `src/lib/registry/designComponents.ts`, `src/routes/design/**`, or `docs/components/**`.

2026-04-2717

repo-homepage-grid-registry

emzinnia/emzinnia.dev

Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

2026-04-2717

repo-performance-analytics-workflow

emzinnia/emzinnia.dev

Maintains the dev performance analytics pipeline across browser instrumentation, persisted analytics API, Prisma storage, and editor analytics UI. Use when editing `performanceAnalytics`, `/api/performance-analytics`, analytics Prisma models, or editor analytics sections.

2026-04-2717

repo-api-route-patterns

emzinnia/emzinnia.dev

Implements SvelteKit API routes in this repo using the existing server, env, and response conventions. Use when editing `src/routes/api/**/+server.ts`, adding new endpoints, or connecting server routes to Prisma or GitHub-backed data.

2026-04-1117

repo-editor-dev-surface

emzinnia/emzinnia.dev

Maintains the dev-only editor route and its shared homepage customization state. Use when changing `/editor`, grid layout behavior, local user settings, debug toggles, or editor section components.

2026-04-1117

name	repo-playwright-e2e-workflow
description	Adds and maintains Playwright end-to-end coverage using this repo's local dev-server configuration and test style. Use when writing `e2e/` specs, validating homepage flows, or covering API-backed UI behavior in the browser.

Repo Playwright E2E Workflow

Use this skill when

Adding or editing files in e2e/
Covering a homepage flow, modal, tab set, or editor/debug interaction
Unsure how this repo boots the app for Playwright

Repo-specific setup

Config file: playwright.config.ts
Test directory: e2e
Base URL: http://127.0.0.1:4173
Web server command: npm run dev -- --host 127.0.0.1 --port 4173

Guidelines

Write specs under e2e/ near related flows.
Prefer roles, labels, and visible text before CSS selectors.
Reuse tiny helpers when a setup step repeats, such as enabling debug sections through localStorage.
Keep tests parallel-safe and independent.
Assert user-visible outcomes, not implementation details.

Important repo gotchas

The default Playwright config runs the dev server, not preview.
Dev-only surfaces such as /editor depend on import.meta.env.DEV, so the default config is the correct environment for them.
If a scenario needs a different server mode or env setup, create that intentionally instead of mutating the default flow.

Verification

Run npm run test:e2e for the full suite.
Run a focused Playwright command while iterating, then rerun the closest broader coverage before finishing.