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 Editor Plan Set - Prompt

Name: wow-viewer Editor Plan Set
Author: akspa0

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

Choose the right detailed prompt for the staged wow-viewer editor transition.

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_editor_plan_2026-04-03.md
wow-viewer/README.md
AGENTS.md

Goal

Route the current request to the correct focused prompt in .codex/prompts/ so the viewer-to-editor transition lands as narrow, validated slices instead of one unstable UI or persistence rewrite.

Companion Prompts

wow-viewer-map-editing-foundation-plan.md
wow-viewer-editor-ui-surface-plan.md
wow-viewer-cli-gui-surface-plan.md
wow-viewer-tool-migration-sequence-plan.md
wow-viewer-shared-io-implementation.md
wow-viewer-pm4-library-implementation.md

Routing Rules

Use wow-viewer-map-editing-foundation-plan.md when the problem is PM4 MPRL-assisted terrain conform, saved PM4 object choices, moved object persistence, ADT or WDT or object write ownership, dirty-map tracking, save pipelines, or the first real editor transaction boundary.
Use wow-viewer-editor-ui-surface-plan.md when the problem is viewer-vs-editor mode switching, preset panel layouts, dock profiles, editor affordances, tool clustering, inspector organization, or how existing chunk clipboard and alpha-mask tools should surface in an editor workspace.
Use wow-viewer-cli-gui-surface-plan.md when the problem is making an editor workflow exist both as headless commands and as GUI panels over the same shared services.
Use wow-viewer-shared-io-implementation.md when the editor ask has already collapsed to one concrete Core or Core.IO implementation seam such as ADT or WDT writing, object-placement persistence, map-file detection, or top-level editor save support.
Use wow-viewer-pm4-library-implementation.md when the ask is specifically the next Core.PM4 seam needed by editing, such as promoting MPRL summaries, terrain-contact helpers, placement solvers, or saved-object evidence contracts into the library.
Use wow-viewer-tool-migration-sequence-plan.md when the ask is broader phasing for the editor transition across runtime, tools, save paths, and UI cutover.

Deliverables

Return all items:

the best next prompt to run
why it is the correct slice now
which companion 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 editor problem you think the user is trying to solve
the single best next prompt from the set above
the narrow proof that would make that slice real
what you are explicitly not claiming yet

Install wow-viewer Editor 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 `wow-viewer` editor transition. ## 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_editor_plan_2026-04-03.md` 5. `wow-viewer/README.md` 6. `AGENTS.md` ## Goal Route the current request to the correct focused prompt in `.codex/prompts/` so the viewer-to-editor transition lands as narrow, validated slices instead of one unstable UI or persistence rewrite. ## Companion Prompts - `wow-viewer-map-editing-foundation-plan.md` - `wow-viewer-editor-ui-surface-plan.md` - `wow-viewer-cli-gui-surface-plan.md` - `wow-viewer-tool-migration-sequence-plan.md` - `wow-viewer-shared-io-implementation.md` - `wow-viewer-pm4-library-implementation.md` ## Routing Rules - Use `wow-viewer-map-editing-foundation-plan.md` when the problem is PM4 `MPRL`-assisted terrain conform, saved PM4 object choices, moved object persistence, ADT or WDT or object write ownership, dirty-map tracking, save pipelines, or the first real editor transaction boundary. - Use `wow-viewer-editor-ui-surface-plan.md` when the problem is viewer-vs-editor mode switching, preset panel layouts, dock profiles, editor affordances, tool clustering, inspector organization, or how existing chunk clipboard and alpha-mask tools should surface in an editor workspace. - Use `wow-viewer-cli-gui-surface-plan.md` when the problem is making an editor workflow exist both as headless commands and as GUI panels over the same shared services. - Use `wow-viewer-shared-io-implementation.md` when the editor ask has already collapsed to one concrete `Core` or `Core.IO` implementation seam such as ADT or WDT writing, object-placement persistence, map-file detection, or top-level editor save support. - Use `wow-viewer-pm4-library-implementation.md` when the ask is specifically the next `Core.PM4` seam needed by editing, such as promoting `MPRL` summaries, terrain-contact helpers, placement solvers, or saved-object evidence contracts into the library. - Use `wow-viewer-tool-migration-sequence-plan.md` when the ask is broader phasing for the editor transition across runtime, tools, save paths, and UI cutover. ## Deliverables Return all items: 1. the best next prompt to run 2. why it is the correct slice now 3. which companion 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 editor problem you think the user is trying to solve 2. the single best next prompt from the set above 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 `wow-viewer` editor transition.\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_editor_plan_2026-04-03.md`\n5. `wow-viewer/README.md`\n6. `AGENTS.md`\n\n## Goal\n\nRoute the current request to the correct focused prompt in `.codex/prompts/` so the viewer-to-editor transition lands as narrow, validated slices instead of one unstable UI or persistence rewrite.\n\n## Companion Prompts\n\n- `wow-viewer-map-editing-foundation-plan.md`\n- `wow-viewer-editor-ui-surface-plan.md`\n- `wow-viewer-cli-gui-surface-plan.md`\n- `wow-viewer-tool-migration-sequence-plan.md`\n- `wow-viewer-shared-io-implementation.md`\n- `wow-viewer-pm4-library-implementation.md`\n\n## Routing Rules\n\n- Use `wow-viewer-map-editing-foundation-plan.md` when the problem is PM4 `MPRL`-assisted terrain conform, saved PM4 object choices, moved object persistence, ADT or WDT or object write ownership, dirty-map tracking, save pipelines, or the first real editor transaction boundary.\n- Use `wow-viewer-editor-ui-surface-plan.md` when the problem is viewer-vs-editor mode switching, preset panel layouts, dock profiles, editor affordances, tool clustering, inspector organization, or how existing chunk clipboard and alpha-mask tools should surface in an editor workspace.\n- Use `wow-viewer-cli-gui-surface-plan.md` when the problem is making an editor workflow exist both as headless commands and as GUI panels over the same shared services.\n- Use `wow-viewer-shared-io-implementation.md` when the editor ask has already collapsed to one concrete `Core` or `Core.IO` implementation seam such as ADT or WDT writing, object-placement persistence, map-file detection, or top-level editor save support.\n- Use `wow-viewer-pm4-library-implementation.md` when the ask is specifically the next `Core.PM4` seam needed by editing, such as promoting `MPRL` summaries, terrain-contact helpers, placement solvers, or saved-object evidence contracts into the library.\n- Use `wow-viewer-tool-migration-sequence-plan.md` when the ask is broader phasing for the editor transition across runtime, tools, save paths, and UI cutover.\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 companion 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 editor problem you think the user is trying to solve\n2. the single best next prompt from the set above\n3. the narrow proof that would make that slice real\n4. what you are explicitly not claiming yet", "variables": [], "notes": "Route wow-viewer editor-transition work to the right planning prompt. Use when the ask is PM4 MPRL-assisted terrain conform, saved PM4 object choices, moved-object persistence, map save or write ownership, editor-mode panel presets, or the broader shift from viewer to viewer-editor. Arguments: Describe the editor feature family, persistence seam, or UI reorganization slice you want to attack.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/akspa0/parp-tools", "path": ".codex/prompts/wow-viewer-editor-plan-set.md", "ref": "4f7fb94cfad6bf6348c55c28ae9361c2d2fd9cb7", "url": "https://github.com/akspa0/parp-tools/blob/4f7fb94cfad6bf6348c55c28ae9361c2d2fd9cb7/.codex/prompts/wow-viewer-editor-plan-set.md", "key": "akspa0/parp-tools/.codex/prompts/wow-viewer-editor-plan-set.md" } } }

wow-viewer Editor Plan Set

About

Read First

Goal

Companion Prompts

Routing Rules

Deliverables

First Output

Install wow-viewer Editor 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