e2e-example-acceptance
/e2e-example-acceptance
Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.
Original author description
Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.
How it works
- When to Use
- Mandatory Acceptance Flow
- Authoring Template
- Reporting Format
- Guardrails
SKILL.md preview
---
name: e2e-example-acceptance
description: Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.
license: MIT
compatibility: Requires Node, pnpm, and Playwright dependencies installed.
metadata:
author: farm
version: "1.0"
---
Run example acceptance with executable checks for start/build/preview and browser behavior.
## When to Use
- Adding a new `examples/<name>/e2e.spec.ts`
- Updating an existing E2E case for an example
- Verifying regression fixes in an example before merge
- Confirming no browser console/page/request anomalies during acceptance
## Mandatory Acceptance Flow
1. Identify affected examples
- From changed files, collect all `examples/<name>/...` paths.
- If no explicit list is provided, ask for the intended scope.
2. Build each affected example
- `cd examples/<name> && npm run build`
3. Run start and preview checks for each affected example
- For examples with dedicated `e2e.spec.ts`, run targeted E2E:
- `pnpm run test-e2e -- --example <name>`
- For examples without a dedicated test, run smoke checks manually:
- `cd examples/<name> && npm run start`
- `cd examples/<name> && npm run preview`
4. Browser-level acceptance criteria
- Console: no unhandled `error`/`pageerror` messages.
- Network: no unexpected `requestfailed` entries.
- Content: assert key selectors/text that prove feature correctness.
5. Update or add E2E tests when needed
- Prefer dedicated `examples/<name>/e2e.spec.ts` for feature-specific behavior.
- Keep assertions deterministic; avoid brittle timing-only checks.
- Include both `start` and `preview` coverage unless the example is explicitly single-mode.
## Authoring Template
```ts
import { basename, dirname } from "path";
import { fileURLToPath } from "url";
import { expect, startAndTest } from "../../e2e/index.js";
const name = basename(import.meta.url);
const projectPath = dirname(fileURLToPath(import.meta.url));
export default async function (ctx) {
const runTest = (command?: "start" | "preview") =>
startAndTest(
projectPath,
async (page) => {
await page.waitForSelector("#root > *", { timeout: 10000 });
// assert page content and absence of runtime anomalies
},
command,
);
await ctx.test("e2e start", () => runTest());
await ctx.test("e2e preview", () => runTest("preview"));
}
```
## Reporting Format
- `Examples`: list of verified examples
- `Build`: pass/fail per example
- `E2E Start`: pass/fail per example
- `E2E Preview`: pass/fail per example
- `Anomalies`: console/request/pageerror summary
- `Notes`: expected skips or known caveats
## Guardrails
- Do not rely only on build success; start/preview behavior must be observed.
- Do not use `pnpm run ready` unless the user explicitly asks for full CI parity.
- Do not edit generated `dist/` files.
- Use the new standalone E2E runner (see `scripts/test-e2e.mts`) — vitest is no longer involved.
Versions
The database has no other skills named e2e-example-acceptance.
Database snapshot: 13.11.2026 · package version d48f9a72d4e9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95skill-maintenance
Maintain the Frontend Testing Skill in this repo. Use when asked to review the skill, run a spec/quality review, install-local (wire one example app to the local marketplace), sync up (an example app → root), install-marketplace (switch the vitest-browser app to the published… - 100studio
Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally. - 100add-example-tutorial
Use when adding a public teaching example or a docs tutorial. Don't use for an internal Nx playground (that is new-react-playground), for a package API change with no walkthrough, or for a docs-only copy edit. - 100test-and-harden
Decide what to test and how, write acceptance criteria and tests that prove behavior, check web apps in a real browser with evidence, build a verify skill for a repo, prune bad tests, harden apps, and hold Python to a clear bar. Use for "write tests", "test plan", "acceptance… - 95Browser
Debug-first browser automation with always-on visibility. Console logs, network requests, and errors captured by default. USE WHEN browser, screenshot, debug web, verify UI, troubleshoot frontend. - 100playground-examples
This skill should be used when adding, editing, or fixing an example in apps/playground — when a task says "add a playground example", "example fails check:examples", "playgroundExamples.test.ts is failing", "regenerate ambient types", "generate-types", "example thumbnail is…