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.

Full-Stack Feature - Prompt

Name: Full-Stack Feature
Author: themkarimi

Prompt file imported from themkarimi/redisnavigator (.github/prompts/full-stack-feature.prompt.md). Fill in {{arguments}} before use. Copyright stays with the author.

Implement the requested RedisNavigator feature end to end: {{arguments}}

Follow the workspace defaults in AGENTS.md.

Use these scoped instructions when relevant:

backend-routes.instructions.md for Express route handlers, validation, RBAC, audit logging, and route registration.
frontend-hooks-query.instructions.md for frontend data fetching, hooks, mutations, and query invalidation.
prisma-workflow.instructions.md if the feature changes schema, models, migrations, or seed compatibility.

Execution requirements:

Identify whether the work is backend-only, frontend-only, or full-stack before editing.
Reuse existing patterns before introducing new abstractions.
If the feature adds or changes an API endpoint, update both the backend route wiring and the matching frontend hook or API call path.
If the feature changes persisted data, update Prisma-related code and follow the migration workflow.
Keep changes scoped and avoid touching generated output or unrelated files.

Implementation checklist:

Find the closest existing feature pattern in the backend routes, frontend hooks, and relevant pages.
Implement backend changes first when the frontend depends on new API behavior.
Register new backend routes in backend/src/index.ts if needed.
Add or update frontend hooks under frontend/src/hooks/ rather than fetching directly inside pages.
Update the page or component that consumes the feature and keep query invalidation aligned with the changed data.
Update tests or add focused coverage when backend behavior changes.
Run the smallest relevant validation commands for the files you changed and report what was or was not verified.

Response requirements:

Make the code changes instead of only describing them.
Summarize the implemented behavior, the files changed, and any validation performed.
Call out follow-up risks or gaps if a part of the feature could not be verified locally.

Install Full-Stack Feature 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.

Implement the requested RedisNavigator feature end to end: {{arguments}} Follow the workspace defaults in [AGENTS.md](../../AGENTS.md). Use these scoped instructions when relevant: - [backend-routes.instructions.md](../instructions/backend-routes.instructions.md) for Express route handlers, validation, RBAC, audit logging, and route registration. - [frontend-hooks-query.instructions.md](../instructions/frontend-hooks-query.instructions.md) for frontend data fetching, hooks, mutations, and query invalidation. - [prisma-workflow.instructions.md](../instructions/prisma-workflow.instructions.md) if the feature changes schema, models, migrations, or seed compatibility. Execution requirements: - Identify whether the work is backend-only, frontend-only, or full-stack before editing. - Reuse existing patterns before introducing new abstractions. - If the feature adds or changes an API endpoint, update both the backend route wiring and the matching frontend hook or API call path. - If the feature changes persisted data, update Prisma-related code and follow the migration workflow. - Keep changes scoped and avoid touching generated output or unrelated files. Implementation checklist: - Find the closest existing feature pattern in the backend routes, frontend hooks, and relevant pages. - Implement backend changes first when the frontend depends on new API behavior. - Register new backend routes in `backend/src/index.ts` if needed. - Add or update frontend hooks under `frontend/src/hooks/` rather than fetching directly inside pages. - Update the page or component that consumes the feature and keep query invalidation aligned with the changed data. - Update tests or add focused coverage when backend behavior changes. - Run the smallest relevant validation commands for the files you changed and report what was or was not verified. Response requirements: - Make the code changes instead of only describing them. - Summarize the implemented behavior, the files changed, and any validation performed. - Call out follow-up risks or gaps if a part of the feature could not be verified locally.

{ "prompt": "Implement the requested RedisNavigator feature end to end: {{arguments}}\n\nFollow the workspace defaults in [AGENTS.md](../../AGENTS.md).\n\nUse these scoped instructions when relevant:\n- [backend-routes.instructions.md](../instructions/backend-routes.instructions.md) for Express route handlers, validation, RBAC, audit logging, and route registration.\n- [frontend-hooks-query.instructions.md](../instructions/frontend-hooks-query.instructions.md) for frontend data fetching, hooks, mutations, and query invalidation.\n- [prisma-workflow.instructions.md](../instructions/prisma-workflow.instructions.md) if the feature changes schema, models, migrations, or seed compatibility.\n\nExecution requirements:\n- Identify whether the work is backend-only, frontend-only, or full-stack before editing.\n- Reuse existing patterns before introducing new abstractions.\n- If the feature adds or changes an API endpoint, update both the backend route wiring and the matching frontend hook or API call path.\n- If the feature changes persisted data, update Prisma-related code and follow the migration workflow.\n- Keep changes scoped and avoid touching generated output or unrelated files.\n\nImplementation checklist:\n- Find the closest existing feature pattern in the backend routes, frontend hooks, and relevant pages.\n- Implement backend changes first when the frontend depends on new API behavior.\n- Register new backend routes in `backend/src/index.ts` if needed.\n- Add or update frontend hooks under `frontend/src/hooks/` rather than fetching directly inside pages.\n- Update the page or component that consumes the feature and keep query invalidation aligned with the changed data.\n- Update tests or add focused coverage when backend behavior changes.\n- Run the smallest relevant validation commands for the files you changed and report what was or was not verified.\n\nResponse requirements:\n- Make the code changes instead of only describing them.\n- Summarize the implemented behavior, the files changed, and any validation performed.\n- Call out follow-up risks or gaps if a part of the feature could not be verified locally.", "variables": [ "arguments" ], "notes": "Implement a RedisNavigator full-stack feature that may touch backend routes, frontend hooks/pages, and optionally Prisma schema or migrations. Arguments: Describe the feature, affected user flow, API behavior, and any schema or permission changes.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/themkarimi/redisnavigator", "path": ".github/prompts/full-stack-feature.prompt.md", "ref": "7c76c96a0c8ce448c00420624e9dfe51d98bcf37", "url": "https://github.com/themkarimi/redisnavigator/blob/7c76c96a0c8ce448c00420624e9dfe51d98bcf37/.github/prompts/full-stack-feature.prompt.md", "key": "themkarimi/redisnavigator/.github/prompts/full-stack-feature.prompt.md" } } }

Full-Stack Feature

About

Install Full-Stack Feature 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

Use it

Manifest

Reviews