菜单
Run the toolbox-web Playwright e2e suites — docs-demo tests, cross-framework parity tests, performance-regression and stability tests. Covers starting demo servers, the various run commands, and updating visual baselines.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepare a @toolbox-web library for release AND drive release-please versioning. Covers the pre-release checklist (lint, test, build, bundle size, CHANGELOG, docs) PLUS release-please version operations — graduating a prerelease to GA (rc → stable), switching the prerelease identifier (beta → rc), and the per-package path-scoped Release-As bootstrap commits. Use when cutting a release, promoting a prerelease line to stable, or whenever release-please proposes the wrong version (e.g. an rc/patch bump when you expect the clean GA version like 3.0.0).
Run deterministic codebase-intelligence analysis with fallow. Covers health scoring (complexity/CRAP/refactor targets), dead code, duplication, dependency hygiene, and PR-scoped audit. Use before opening a PR, as part of `/qa`, or to identify refactoring opportunities in a file or plugin. Produces machine-actionable JSON findings that can be fed directly into `qa-apply-findings`.
Add a new feature OR backport a bugfix consistently across the Angular, React, and Vue adapter libraries for @toolbox-web/grid. Use whenever you touch one adapter, to confirm the other two need the same change and to keep full parity.
Create a new framework adapter library for @toolbox-web/grid, with a matching demo app. Covers library scaffolding, adapter implementation, demo setup, workspace wiring, and e2e parity testing.
Author, restructure, or update documentation for the Astro/Starlight docs site. Covers ADDING a new docs page or route (MDX + sidebar registration in astro.config.mjs + llms.txt/llms-full.txt inclusion), which prose/MDX and API-reference docs to check after a code change, how to write them, the `<Audience>` and `llmsFull` curation knobs, and regenerating typedoc API docs. Use whenever you create, move, rename, or edit any file under apps/docs/, or after any feature, fix, or refactor that touches user-visible behaviour. (For building a new interactive demo component, use the astro-demo skill instead.)
Read, reply to, and resolve review-comment threads on a GitHub pull request using the gh CLI. Use whenever you need to triage PR feedback (fetch all unresolved review threads as structured JSON, post inline replies on specific threads, and mark threads resolved) instead of hand-writing a one-off gh/GraphQL script each time. Prefer this over the generic address-pr-comments skill for bulk thread triage and programmatic gh/GraphQL access.
| name | run-e2e |
| description | Run the toolbox-web Playwright e2e suites — docs-demo tests, cross-framework parity tests, performance-regression and stability tests. Covers starting demo servers, the various run commands, and updating visual baselines. |
Two Playwright e2e suites exist. This skill is the runbook — how to execute them and manage servers/baselines. For how to write e2e tests (conventions, utilities, selectors, wait strategies), see the auto-applied e2e-testing instruction.
| Suite | Location | Purpose | Server |
|---|---|---|---|
| Docs demos | apps/docs-e2e/ | Every Astro demo page renders and works correctly | Auto-starts Astro on port 4450 |
| Cross-framework | e2e/ | Visual/functional parity across Vanilla, React, Angular, Vue demos | Manual server start required |
Auto-starts the Astro dev server — no manual setup:
bun nx e2e docs-e2e
Demo servers must be running first (these tests do not auto-start servers).
# Option 1: start the 4 demo servers in a separate terminal, then run tests
bun run demo # vanilla=4000, react=4300, angular=4200, vue=4100
bun nx e2e e2e # run tests against the running servers
# Option 2: build + start dist servers + wait for ports + test (CI-friendly)
bun run e2e:full
If a run fails with connection-refused / timeout on ports 4000/4100/4200/4300, the demo servers aren't up — start them (Option 1) or use e2e:full (Option 2).
Only after intentionally changing rendered output. Review the regenerated PNGs before committing.
bun nx e2e:update-snapshots e2e
Part of the regular e2e suite. Compares the current build against the latest published release (loaded from CDN) in the same browser session, so runner variance cancels out. Flags a regression if the current build is >10% slower; auto-retries up to 2× to absorb CI noise.
# Requires a build first (for the local UMD bundle)
bun nx build grid
# Run the self-comparison tests (no demo server needed)
bunx playwright test --config=e2e/playwright.config.ts performance-regression
| Env var | Purpose |
|---|---|
PERF_CDN_VERSION | Override CDN version to compare against (default: latest) |
PERF_RUN_ID | Unique ID for the output file (perf-metrics-{runId}.json) |
Structural assertions against the vanilla demo (virtualization bounds, zero JS errors, no memory/DOM leaks). Fast, deterministic, part of the regular e2e suite — no separate command needed.
| File | Purpose |
|---|---|
e2e/tests/performance-regression.spec.ts | Self-comparison benchmarks (no demo needed) |
e2e/tests/grid-stability.spec.ts | Structural stability tests (vanilla demo) |
e2e/tests/perf-metrics-helper.ts | Metric accumulator + flush utility |