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.

wow-viewer World Runtime Plan Set - Prompt

Name: wow-viewer World Runtime Plan Set
Author: akspa0

Prompt file imported from akspa0/parp-tools (.codex/prompts/wow-viewer-world-runtime-plan-set.md). Copyright stays with the author.

Choose the right detailed prompt for the staged WorldScene to wow-viewer world-runtime split.

Read First

gillijimproject_refactor/memory-bank/activeContext.md
gillijimproject_refactor/memory-bank/progress.md
gillijimproject_refactor/src/MdxViewer/memory-bank/activeContext.md
gillijimproject_refactor/plans/wow_viewer_world_runtime_service_plan_2026-03-31.md
wow-viewer/README.md
AGENTS.md

Goal

Route the current request to the correct ordered prompt in .codex/prompts/wow-viewer-world-runtime/ so the WorldScene split happens as a sequence of narrow, validated slices instead of another monolithic renderer rewrite.

Ordered Prompts

wow-viewer-world-runtime/01-negative-asset-lookup-suppression.md
wow-viewer-world-runtime/02-visible-set-runtime-extraction.md
wow-viewer-world-runtime/03-world-pass-service-extraction.md
wow-viewer-world-runtime/04-world-scene-host-thinning.md
wow-viewer-world-runtime/05-wow-viewer-app-runtime-consumer.md

Routing Rules

Use 01-negative-asset-lookup-suppression.md when the problem is repeated .skin lookup churn, failed MDX retry spam, noisy asset logs, negative lookup caching, or unknown performance degradation from repeated asset misses.
Use 02-visible-set-runtime-extraction.md when the problem is visible WMO or MDX or taxi-actor collection, render-frame scratch ownership, culling buckets, or moving visible-set logic out of WorldScene.
Use 03-world-pass-service-extraction.md when the problem is explicit terrain or WMO or MDX or overlay runtime service ownership, pass sequencing, or a world-pass coordinator inside WowViewer.Core.Runtime.
Use 04-world-scene-host-thinning.md when the problem is reducing WorldScene to a thin host over runtime services without yet claiming a full app cutover.
Use 05-wow-viewer-app-runtime-consumer.md when the problem is making wow-viewer/src/viewer/WowViewer.App consume the extracted world-runtime seams after the earlier slices are already real.

Deliverables

Return all items:

the best next prompt to run
why it is the correct slice now
which ordered prompt should follow after it
what concrete repo and file scope the next slice should include
what should stay out of scope for the next slice
what proof level is realistic for that slice

First Output

Start with:

the exact world-runtime problem you think the user is trying to solve
the single best next prompt from the ordered set
the narrow proof that would make that slice real
what you are explicitly not claiming yet

Install wow-viewer World Runtime Plan Set 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.

Choose the right detailed prompt for the staged `WorldScene` to `wow-viewer` world-runtime split. ## Read First 1. `gillijimproject_refactor/memory-bank/activeContext.md` 2. `gillijimproject_refactor/memory-bank/progress.md` 3. `gillijimproject_refactor/src/MdxViewer/memory-bank/activeContext.md` 4. `gillijimproject_refactor/plans/wow_viewer_world_runtime_service_plan_2026-03-31.md` 5. `wow-viewer/README.md` 6. `AGENTS.md` ## Goal Route the current request to the correct ordered prompt in `.codex/prompts/wow-viewer-world-runtime/` so the `WorldScene` split happens as a sequence of narrow, validated slices instead of another monolithic renderer rewrite. ## Ordered Prompts - `wow-viewer-world-runtime/01-negative-asset-lookup-suppression.md` - `wow-viewer-world-runtime/02-visible-set-runtime-extraction.md` - `wow-viewer-world-runtime/03-world-pass-service-extraction.md` - `wow-viewer-world-runtime/04-world-scene-host-thinning.md` - `wow-viewer-world-runtime/05-wow-viewer-app-runtime-consumer.md` ## Routing Rules - Use `01-negative-asset-lookup-suppression.md` when the problem is repeated `.skin` lookup churn, failed MDX retry spam, noisy asset logs, negative lookup caching, or unknown performance degradation from repeated asset misses. - Use `02-visible-set-runtime-extraction.md` when the problem is visible WMO or MDX or taxi-actor collection, render-frame scratch ownership, culling buckets, or moving visible-set logic out of `WorldScene`. - Use `03-world-pass-service-extraction.md` when the problem is explicit terrain or WMO or MDX or overlay runtime service ownership, pass sequencing, or a world-pass coordinator inside `WowViewer.Core.Runtime`. - Use `04-world-scene-host-thinning.md` when the problem is reducing `WorldScene` to a thin host over runtime services without yet claiming a full app cutover. - Use `05-wow-viewer-app-runtime-consumer.md` when the problem is making `wow-viewer/src/viewer/WowViewer.App` consume the extracted world-runtime seams after the earlier slices are already real. ## Deliverables Return all items: 1. the best next prompt to run 2. why it is the correct slice now 3. which ordered prompt should follow after it 4. what concrete repo and file scope the next slice should include 5. what should stay out of scope for the next slice 6. what proof level is realistic for that slice ## First Output Start with: 1. the exact world-runtime problem you think the user is trying to solve 2. the single best next prompt from the ordered set 3. the narrow proof that would make that slice real 4. what you are explicitly not claiming yet

{ "prompt": "Choose the right detailed prompt for the staged `WorldScene` to `wow-viewer` world-runtime split.\n\n## Read First\n\n1. `gillijimproject_refactor/memory-bank/activeContext.md`\n2. `gillijimproject_refactor/memory-bank/progress.md`\n3. `gillijimproject_refactor/src/MdxViewer/memory-bank/activeContext.md`\n4. `gillijimproject_refactor/plans/wow_viewer_world_runtime_service_plan_2026-03-31.md`\n5. `wow-viewer/README.md`\n6. `AGENTS.md`\n\n## Goal\n\nRoute the current request to the correct ordered prompt in `.codex/prompts/wow-viewer-world-runtime/` so the `WorldScene` split happens as a sequence of narrow, validated slices instead of another monolithic renderer rewrite.\n\n## Ordered Prompts\n\n- `wow-viewer-world-runtime/01-negative-asset-lookup-suppression.md`\n- `wow-viewer-world-runtime/02-visible-set-runtime-extraction.md`\n- `wow-viewer-world-runtime/03-world-pass-service-extraction.md`\n- `wow-viewer-world-runtime/04-world-scene-host-thinning.md`\n- `wow-viewer-world-runtime/05-wow-viewer-app-runtime-consumer.md`\n\n## Routing Rules\n\n- Use `01-negative-asset-lookup-suppression.md` when the problem is repeated `.skin` lookup churn, failed MDX retry spam, noisy asset logs, negative lookup caching, or unknown performance degradation from repeated asset misses.\n- Use `02-visible-set-runtime-extraction.md` when the problem is visible WMO or MDX or taxi-actor collection, render-frame scratch ownership, culling buckets, or moving visible-set logic out of `WorldScene`.\n- Use `03-world-pass-service-extraction.md` when the problem is explicit terrain or WMO or MDX or overlay runtime service ownership, pass sequencing, or a world-pass coordinator inside `WowViewer.Core.Runtime`.\n- Use `04-world-scene-host-thinning.md` when the problem is reducing `WorldScene` to a thin host over runtime services without yet claiming a full app cutover.\n- Use `05-wow-viewer-app-runtime-consumer.md` when the problem is making `wow-viewer/src/viewer/WowViewer.App` consume the extracted world-runtime seams after the earlier slices are already real.\n\n## Deliverables\n\nReturn all items:\n\n1. the best next prompt to run\n2. why it is the correct slice now\n3. which ordered prompt should follow after it\n4. what concrete repo and file scope the next slice should include\n5. what should stay out of scope for the next slice\n6. what proof level is realistic for that slice\n\n## First Output\n\nStart with:\n\n1. the exact world-runtime problem you think the user is trying to solve\n2. the single best next prompt from the ordered set\n3. the narrow proof that would make that slice real\n4. what you are explicitly not claiming yet", "variables": [], "notes": "Route staged wow-viewer world-runtime and WorldScene split work to the right ordered Codex prompt. Use when planning or implementing negative asset lookup suppression, repeated .skin miss suppression, world visible-set extraction, terrain or WMO or MDX or overlay pass-service extraction, WorldScene host thinning, or early wow-viewer app consumer cutover. Arguments: Describe the WorldScene split seam, runtime service slice, or performance hotspot you want to attack next.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/akspa0/parp-tools", "path": ".codex/prompts/wow-viewer-world-runtime-plan-set.md", "ref": "5608d59a180dc4296e29bc19be1a3cc5e94ef309", "url": "https://github.com/akspa0/parp-tools/blob/5608d59a180dc4296e29bc19be1a3cc5e94ef309/.codex/prompts/wow-viewer-world-runtime-plan-set.md", "key": "akspa0/parp-tools/.codex/prompts/wow-viewer-world-runtime-plan-set.md" } } }

wow-viewer World Runtime Plan Set

About

Read First

Goal

Ordered Prompts

Routing Rules

Deliverables

First Output

Install wow-viewer World Runtime Plan Set 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