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.

ux-ui - Prompt - OpenSmartRoute

Name: ux-ui
Author: 3270io

Prompt file imported from 3270io/3270Web (.github/prompts/ux-ui.prompt.md). Copyright stays with the author.

UX / UI Change Prompt

When to use

Adding or modifying a modal, button, or control in web/templates/ or web/static/.
Changing the terminal screen layout or 3270 field styles.
Updating the log viewer, workflow controls, or keyboard-shortcut panel.
Fixing a visual regression reported against the rendered screen or a modal.

Inputs

Goal:
Scope: (e.g., web/templates/screen.html, web/static/keys.js)
Files:
Constraints: (e.g., must work without a JS bundler, must not break the terminal grid layout)

Prompt

Follow the conventions in .github/copilot-instructions.md and .github/instructions/frontend.instructions.md.

Implement the UI change described by: .

Rules:

Write plain ES6. No npm dependencies, no bundler, no TypeScript.
Do not move 3270 field <input> generation out of internal/render/html_renderer.go into templates.
New state-mutating actions must call a JSON endpoint (not a form POST) and handle errors in JS.
All fetch POST calls rely on the browser sending the Origin header automatically; do not add a custom CSRF token mechanism.
Preserve the monospace grid layout so 3270 field positions remain accurate. Do not change the font-family or cell dimensions without an explicit requirement.
Keep existing endpoint paths (/logs, /screen, /key, etc.) unchanged.

Produce a minimal diff covering only .

Done looks like

go test ./... passes (Go handler side unchanged or tested)
No new npm/node dependencies introduced
Existing JS files edited in-place (no new files unless clearly necessary)
Terminal grid layout visually intact (monospace, correct cell sizing)
New JS functions follow the existing naming and fetch-based pattern
go vet ./... reports no new issues
Diff is scoped to web/ only (unless a new JSON endpoint was required)

Install ux-ui 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.

# UX / UI Change Prompt ## When to use - Adding or modifying a modal, button, or control in `web/templates/` or `web/static/`. - Changing the terminal screen layout or 3270 field styles. - Updating the log viewer, workflow controls, or keyboard-shortcut panel. - Fixing a visual regression reported against the rendered screen or a modal. ## Inputs - **Goal:** <goal> - **Scope:** <scope> (e.g., `web/templates/screen.html`, `web/static/keys.js`) - **Files:** <files> - **Constraints:** <constraints> (e.g., must work without a JS bundler, must not break the terminal grid layout) ## Prompt Follow the conventions in `.github/copilot-instructions.md` and `.github/instructions/frontend.instructions.md`. Implement the UI change described by: **<goal>**. Rules: - Write plain ES6. No npm dependencies, no bundler, no TypeScript. - Do not move 3270 field `<input>` generation out of `internal/render/html_renderer.go` into templates. - New state-mutating actions must call a JSON endpoint (not a form POST) and handle errors in JS. - All `fetch` POST calls rely on the browser sending the `Origin` header automatically; do not add a custom CSRF token mechanism. - Preserve the monospace grid layout so 3270 field positions remain accurate. Do not change the `font-family` or cell dimensions without an explicit requirement. - Keep existing endpoint paths (`/logs`, `/screen`, `/key`, etc.) unchanged. Produce a minimal diff covering only <files>. ## Done looks like - [ ] `go test ./...` passes (Go handler side unchanged or tested) - [ ] No new npm/node dependencies introduced - [ ] Existing JS files edited in-place (no new files unless clearly necessary) - [ ] Terminal grid layout visually intact (monospace, correct cell sizing) - [ ] New JS functions follow the existing naming and `fetch`-based pattern - [ ] `go vet ./...` reports no new issues - [ ] Diff is scoped to `web/` only (unless a new JSON endpoint was required)

{ "prompt": "# UX / UI Change Prompt\n\n## When to use\n- Adding or modifying a modal, button, or control in `web/templates/` or `web/static/`.\n- Changing the terminal screen layout or 3270 field styles.\n- Updating the log viewer, workflow controls, or keyboard-shortcut panel.\n- Fixing a visual regression reported against the rendered screen or a modal.\n\n## Inputs\n- **Goal:** <goal>\n- **Scope:** <scope> (e.g., `web/templates/screen.html`, `web/static/keys.js`)\n- **Files:** <files>\n- **Constraints:** <constraints> (e.g., must work without a JS bundler, must not break the terminal grid layout)\n\n## Prompt\n\nFollow the conventions in `.github/copilot-instructions.md` and `.github/instructions/frontend.instructions.md`.\n\nImplement the UI change described by: **<goal>**.\n\nRules:\n- Write plain ES6. No npm dependencies, no bundler, no TypeScript.\n- Do not move 3270 field `<input>` generation out of `internal/render/html_renderer.go` into templates.\n- New state-mutating actions must call a JSON endpoint (not a form POST) and handle errors in JS.\n- All `fetch` POST calls rely on the browser sending the `Origin` header automatically; do not add a custom CSRF token mechanism.\n- Preserve the monospace grid layout so 3270 field positions remain accurate. Do not change the `font-family` or cell dimensions without an explicit requirement.\n- Keep existing endpoint paths (`/logs`, `/screen`, `/key`, etc.) unchanged.\n\nProduce a minimal diff covering only <files>.\n\n## Done looks like\n- [ ] `go test ./...` passes (Go handler side unchanged or tested)\n- [ ] No new npm/node dependencies introduced\n- [ ] Existing JS files edited in-place (no new files unless clearly necessary)\n- [ ] Terminal grid layout visually intact (monospace, correct cell sizing)\n- [ ] New JS functions follow the existing naming and `fetch`-based pattern\n- [ ] `go vet ./...` reports no new issues\n- [ ] Diff is scoped to `web/` only (unless a new JSON endpoint was required)", "variables": [], "notes": "Follow the conventions in `.github/copilot-instructions.md` and `.github/instructions/frontend.instructions.md`.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/3270io/3270Web", "path": ".github/prompts/ux-ui.prompt.md", "ref": "01a3852f5b7812621ee2640dc057f89fdf19ed8d", "url": "https://github.com/3270io/3270Web/blob/01a3852f5b7812621ee2640dc057f89fdf19ed8d/.github/prompts/ux-ui.prompt.md", "key": "3270io/3270Web/.github/prompts/ux-ui.prompt.md" } } }

ux-ui

About

UX / UI Change Prompt

When to use

Inputs

Prompt

Done looks like

Install ux-ui 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