· Standard
T
llmstxt.info Verzeichnis · Standard
test-proxy-recorder
Community-Eintrag
llms.txt erreichbar
KI-Impact-Score 90/100 · A
Die Organisation test-proxy-recorder nutzt den llms.txt-Standard für eine bessere Auffindbarkeit durch KI-Systeme. Branche: Entwickler-Tools. Die Website test-proxy-recorder.dev stellt ihre llms.txt unter https://test-proxy-recorder.dev/llms.txt bereit. Der Eintrag besteht seit 4. August 2026.
llms.txt-Adresse
https://test-proxy-recorder.dev/llms.txt
Gemäß DSGVO Art. 17 kannst du die Löschung deiner Daten beantragen. Rechtsverletzung melden (Art. 16 DSA) →
llms.txt — Aktueller Inhalt
Öffnen ↗
# test-proxy-recorder
> VCR for Playwright — record real HTTP + WebSocket traffic once, replay it deterministically on CI with the backend turned off. No hand-written mocks. Covers Next.js & TanStack Start SSR, browser, and WebSocket traffic. Node >= 20, MIT.
Last updated: 2026-08-18. Canonical: <https://test-proxy-recorder.dev/llms.txt>.
## For AI coding agents — preferred path
This package ships task-focused `SKILL.md` files via [@tanstack/intent](https://www.npmjs.com/package/@tanstack/intent). If your agent supports Intent, load those instead of this file — they are the maintained, deeper source:
```bash
# in the user's project, once
npm install --save-dev test-proxy-recorder
npx @tanstack/intent@latest install
# list skills discoverable from installed packages
npx @tanstack/intent@latest list
# load a specific skill into the current context
npx @tanstack/intent@latest load test-proxy-recorder#proxy-setup
```
Available skills (under `node_modules/test-proxy-recorder/skills/`):
| Skill | Type | When to load |
|---|---|---|
| `proxy-setup` | core | Installing the library, the proxy CLI, `playwright.config.ts` `webServer`, per-test fixtures, record/replay/transparent modes, secret redaction, the config file, and the record-once → commit → CI-replay lifecycle |
| `nextjs-ssr` | framework | Next.js App Router: tagging server-side fetches with `registerProxyFetch` / `registerProxyAxios` / `createHeadersWithRecordingId`, the build-and-start vs `next dev` caveat, why the m
[…gekürzt]