How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

prepare-functional-tests - Prompt

Name: prepare-functional-tests
Author: RaveenGitHub

Prompt file imported from RaveenGitHub/tharaNaayagan (.github/prompts/prepare-functional-tests.prompt.md). Copyright stays with the author.

Prepare Functional Tests Prompt

Use this prompt to convert ready-to-automate functional test scenarios into executable TypeScript Playwright code.

Goal

Generate clean, maintainable Playwright functional automation code following repository conventions:

Reusable Page Object Models in pages/ extending BasePage
Centralized, accessible semantic locators in locators/common.locators.ts (getByRole, getByLabel, getByTestId)
Modular functional test specs in tests/functional/ (e.g., tests/functional/smoke.spec.ts, tests/functional/auth.spec.ts, tests/functional/security.spec.ts, tests/functional/boundary.spec.ts)
Reusable fixtures and dynamic test data builders in fixtures/test-data.ts
Verification with npm run quality-gate and npm test

Inputs

Functional test scenarios from docs/scenarios.md or docs/traceability-tracker.md
Application structure in public/ or live target URL
Existing POM classes in pages/

# Prepare Functional Tests Prompt Use this prompt to convert ready-to-automate functional test scenarios into executable TypeScript Playwright code. ## Goal Generate clean, maintainable Playwright functional automation code following repository conventions: - Reusable Page Object Models in `pages/` extending `BasePage` - Centralized, accessible semantic locators in `locators/common.locators.ts` (`getByRole`, `getByLabel`, `getByTestId`) - Modular functional test specs in `tests/functional/` (e.g., `tests/functional/smoke.spec.ts`, `tests/functional/auth.spec.ts`, `tests/functional/security.spec.ts`, `tests/functional/boundary.spec.ts`) - Reusable fixtures and dynamic test data builders in `fixtures/test-data.ts` - Verification with `npm run quality-gate` and `npm test` ## Inputs - Functional test scenarios from `docs/scenarios.md` or `docs/traceability-tracker.md` - Application structure in `public/` or live target URL - Existing POM classes in `pages/`

Install prepare-functional-tests and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Prepare Functional Tests Prompt\n\nUse this prompt to convert ready-to-automate functional test scenarios into executable TypeScript Playwright code.\n\n## Goal\n\nGenerate clean, maintainable Playwright functional automation code following repository conventions:\n\n- Reusable Page Object Models in `pages/` extending `BasePage`\n- Centralized, accessible semantic locators in `locators/common.locators.ts` (`getByRole`, `getByLabel`, `getByTestId`)\n- Modular functional test specs in `tests/functional/` (e.g., `tests/functional/smoke.spec.ts`, `tests/functional/auth.spec.ts`, `tests/functional/security.spec.ts`, `tests/functional/boundary.spec.ts`)\n- Reusable fixtures and dynamic test data builders in `fixtures/test-data.ts`\n- Verification with `npm run quality-gate` and `npm test`\n\n## Inputs\n\n- Functional test scenarios from `docs/scenarios.md` or `docs/traceability-tracker.md`\n- Application structure in `public/` or live target URL\n- Existing POM classes in `pages/`", "variables": [], "notes": "Transform ready-to-automate functional test scenarios into robust Playwright TypeScript Page Objects, accessible locators, and test specs. Mode: agent. Tools: read, search, edit, execute.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/RaveenGitHub/tharaNaayagan", "path": ".github/prompts/prepare-functional-tests.prompt.md", "ref": "c45a2fcb5786d736cedefddd94bbd153ed955108", "url": "https://github.com/RaveenGitHub/tharaNaayagan/blob/c45a2fcb5786d736cedefddd94bbd153ed955108/.github/prompts/prepare-functional-tests.prompt.md", "key": "RaveenGitHub/tharaNaayagan/.github/prompts/prepare-functional-tests.prompt.md" } } }

prepare-functional-tests

About

Prepare Functional Tests Prompt

Goal

Inputs

Use it

Install prepare-functional-tests and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews