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 Tool Suite Plan Set - Prompt

Name: wow-viewer Tool Suite Plan Set
Author: akspa0

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

Choose the right detailed planning or implementation prompt for the wow-viewer tool-suite refactor.

Read First

gillijimproject_refactor/memory-bank/activeContext.md
gillijimproject_refactor/memory-bank/progress.md
gillijimproject_refactor/src/MdxViewer/memory-bank/activeContext.md
AGENTS.md

Goal

Route the current request to the correct focused prompt in .codex/prompts/ so the planning work stays specific, detailed, and tied to the actual tool/library mess in parp-tools.

Companion Prompts

wow-viewer-dataset-builder-plan.md
wow-viewer-editor-plan-set.md
wow-viewer-pm4-library-implementation.md
wow-viewer-shared-io-implementation.md
wow-viewer-world-runtime-plan-set.md
wow-viewer-m2-runtime-plan-set.md
m2-cross-build-native-investigation.md
wow-viewer-bootstrap-layout-plan.md
wow-viewer-shared-io-library-plan.md
wow-viewer-tool-inventory-cutover-plan.md
wow-viewer-cli-gui-surface-plan.md
wow-viewer-tool-migration-sequence-plan.md

Routing Rules

Use wow-viewer-pm4-library-implementation.md when the problem is the next Core.PM4 extraction, such as pm4 inspect, pm4 audit, pm4 linkage, pm4 mscn, pm4 unknowns, or pm4 export-json, a PM4 regression coverage slice, or a narrow PM4 consumer or solver seam that should stay library-first.
Use wow-viewer-shared-io-implementation.md when the problem is the next real Core or Core.IO shared-format slice, such as ADT root or split-ADT (_tex0.adt, _obj0.adt, _lod.adt) work, WDT summary work, WMO or BLP or DBC or DB2 detection work, a file detector, a chunk reader, a non-PM4 inspect verb, a converter command, or a shared-format regression update.
Use wow-viewer-dataset-builder-plan.md when the problem is dataset corpus export cutover, terrain-supervision artifact ownership, manifest or harvest cutover, minimap cleanup or mask-stitch ownership, dataset explorer design, supervised training-tooling ownership, BYOD distribution policy, or planning a new wow-viewer dataset tool over shared services instead of extending WoWMapConverter as the design owner.
Use wow-viewer-editor-plan-set.md when the problem is turning wow-viewer into an editor, including PM4 MPRL-assisted terrain conform, saved object choices, moved-object persistence, map save ownership, or viewer-vs-editor workspace design.
Use wow-viewer-world-runtime-plan-set.md when the problem is splitting WorldScene, extracting world-runtime services, suppressing repeated asset-miss churn such as .skin lookup spam, or sequencing terrain/WMO/MDX/overlay runtime ownership into wow-viewer.
Use wow-viewer-m2-runtime-plan-set.md when the problem is M2 runtime ownership, exact %02d.skin behavior, active section classification, material/effect routing, animation/lighting state, scene submission/batching, or planning how M2 rendering moves into wow-viewer instead of staying trapped in MdxViewer.
Use m2-cross-build-native-investigation.md when the problem is recovering native behavior differences across multiple client builds (for example 3.3.5 through 6.x) before committing parser or runtime ownership decisions.
Use wow-viewer-bootstrap-layout-plan.md when the problem is repo shape, solution structure, bootstrap scripts, project layout, or where each tool/app/lib should live.
Use wow-viewer-shared-io-library-plan.md when the problem is the broader ownership plan for reading/writing ADT, WDT, M2, MDX, WMO, PM4, DBC, BLP, placement, or related formats.
Use wow-viewer-tool-inventory-cutover-plan.md when the problem is inventorying old tools, deciding what migrates, what merges, what stays archaeology-only, and what becomes a first-class tool in the new repo.
Use wow-viewer-cli-gui-surface-plan.md when the problem is making tools available both as CLI commands and existing GUI panels over the same shared services.
Use wow-viewer-tool-migration-sequence-plan.md when the problem is phasing, dependencies, vertical slices, or what order to migrate tool families without exploding scope.

Deliverables

Return all items:

the best prompt to run next
why it is the right prompt for the current ask
which companion prompts should follow after it
what concrete repo/tool/file-type scope the next prompt should include
what not to waste time on yet

First Output

Start with:

the exact planning problem you think the user is actually trying to solve
the single best next prompt from the set above
the concrete migration/tool scope that prompt should cover first

Install wow-viewer Tool Suite 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 planning or implementation prompt for the `wow-viewer` tool-suite refactor. ## 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. `AGENTS.md` ## Goal Route the current request to the correct focused prompt in `.codex/prompts/` so the planning work stays specific, detailed, and tied to the actual tool/library mess in `parp-tools`. ## Companion Prompts - `wow-viewer-dataset-builder-plan.md` - `wow-viewer-editor-plan-set.md` - `wow-viewer-pm4-library-implementation.md` - `wow-viewer-shared-io-implementation.md` - `wow-viewer-world-runtime-plan-set.md` - `wow-viewer-m2-runtime-plan-set.md` - `m2-cross-build-native-investigation.md` - `wow-viewer-bootstrap-layout-plan.md` - `wow-viewer-shared-io-library-plan.md` - `wow-viewer-tool-inventory-cutover-plan.md` - `wow-viewer-cli-gui-surface-plan.md` - `wow-viewer-tool-migration-sequence-plan.md` ## Routing Rules - Use `wow-viewer-pm4-library-implementation.md` when the problem is the next `Core.PM4` extraction, such as `pm4 inspect`, `pm4 audit`, `pm4 linkage`, `pm4 mscn`, `pm4 unknowns`, or `pm4 export-json`, a PM4 regression coverage slice, or a narrow PM4 consumer or solver seam that should stay library-first. - Use `wow-viewer-shared-io-implementation.md` when the problem is the next real `Core` or `Core.IO` shared-format slice, such as ADT root or split-ADT (`_tex0.adt`, `_obj0.adt`, `_lod.adt`) work, WDT summary work, WMO or BLP or DBC or DB2 detection work, a file detector, a chunk reader, a non-PM4 inspect verb, a converter command, or a shared-format regression update. - Use `wow-viewer-dataset-builder-plan.md` when the problem is dataset corpus export cutover, terrain-supervision artifact ownership, manifest or harvest cutover, minimap cleanup or mask-stitch ownership, dataset explorer design, supervised training-tooling ownership, BYOD distribution policy, or planning a new `wow-viewer` dataset tool over shared services instead of extending `WoWMapConverter` as the design owner. - Use `wow-viewer-editor-plan-set.md` when the problem is turning `wow-viewer` into an editor, including PM4 `MPRL`-assisted terrain conform, saved object choices, moved-object persistence, map save ownership, or viewer-vs-editor workspace design. - Use `wow-viewer-world-runtime-plan-set.md` when the problem is splitting `WorldScene`, extracting world-runtime services, suppressing repeated asset-miss churn such as `.skin` lookup spam, or sequencing terrain/WMO/MDX/overlay runtime ownership into `wow-viewer`. - Use `wow-viewer-m2-runtime-plan-set.md` when the problem is M2 runtime ownership, exact `%02d.skin` behavior, active section classification, material/effect routing, animation/lighting state, scene submission/batching, or planning how M2 rendering moves into `wow-viewer` instead of staying trapped in `MdxViewer`. - Use `m2-cross-build-native-investigation.md` when the problem is recovering native behavior differences across multiple client builds (for example 3.3.5 through 6.x) before committing parser or runtime ownership decisions. - Use `wow-viewer-bootstrap-layout-plan.md` when the problem is repo shape, solution structure, bootstrap scripts, project layout, or where each tool/app/lib should live. - Use `wow-viewer-shared-io-library-plan.md` when the problem is the broader ownership plan for reading/writing ADT, WDT, M2, MDX, WMO, PM4, DBC, BLP, placement, or related formats. - Use `wow-viewer-tool-inventory-cutover-plan.md` when the problem is inventorying old tools, deciding what migrates, what merges, what stays archaeology-only, and what becomes a first-class tool in the new repo. - Use `wow-viewer-cli-gui-surface-plan.md` when the problem is making tools available both as CLI commands and existing GUI panels over the same shared services. - Use `wow-viewer-tool-migration-sequence-plan.md` when the problem is phasing, dependencies, vertical slices, or what order to migrate tool families without exploding scope. ## Deliverables Return all items: 1. the best prompt to run next 2. why it is the right prompt for the current ask 3. which companion prompts should follow after it 4. what concrete repo/tool/file-type scope the next prompt should include 5. what not to waste time on yet ## First Output Start with: 1. the exact planning problem you think the user is actually trying to solve 2. the single best next prompt from the set above 3. the concrete migration/tool scope that prompt should cover first

{ "prompt": "Choose the right detailed planning or implementation prompt for the `wow-viewer` tool-suite refactor.\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. `AGENTS.md`\n\n## Goal\n\nRoute the current request to the correct focused prompt in `.codex/prompts/` so the planning work stays specific, detailed, and tied to the actual tool/library mess in `parp-tools`.\n\n## Companion Prompts\n\n- `wow-viewer-dataset-builder-plan.md`\n- `wow-viewer-editor-plan-set.md`\n- `wow-viewer-pm4-library-implementation.md`\n- `wow-viewer-shared-io-implementation.md`\n- `wow-viewer-world-runtime-plan-set.md`\n- `wow-viewer-m2-runtime-plan-set.md`\n- `m2-cross-build-native-investigation.md`\n- `wow-viewer-bootstrap-layout-plan.md`\n- `wow-viewer-shared-io-library-plan.md`\n- `wow-viewer-tool-inventory-cutover-plan.md`\n- `wow-viewer-cli-gui-surface-plan.md`\n- `wow-viewer-tool-migration-sequence-plan.md`\n\n## Routing Rules\n\n- Use `wow-viewer-pm4-library-implementation.md` when the problem is the next `Core.PM4` extraction, such as `pm4 inspect`, `pm4 audit`, `pm4 linkage`, `pm4 mscn`, `pm4 unknowns`, or `pm4 export-json`, a PM4 regression coverage slice, or a narrow PM4 consumer or solver seam that should stay library-first.\n- Use `wow-viewer-shared-io-implementation.md` when the problem is the next real `Core` or `Core.IO` shared-format slice, such as ADT root or split-ADT (`_tex0.adt`, `_obj0.adt`, `_lod.adt`) work, WDT summary work, WMO or BLP or DBC or DB2 detection work, a file detector, a chunk reader, a non-PM4 inspect verb, a converter command, or a shared-format regression update.\n- Use `wow-viewer-dataset-builder-plan.md` when the problem is dataset corpus export cutover, terrain-supervision artifact ownership, manifest or harvest cutover, minimap cleanup or mask-stitch ownership, dataset explorer design, supervised training-tooling ownership, BYOD distribution policy, or planning a new `wow-viewer` dataset tool over shared services instead of extending `WoWMapConverter` as the design owner.\n- Use `wow-viewer-editor-plan-set.md` when the problem is turning `wow-viewer` into an editor, including PM4 `MPRL`-assisted terrain conform, saved object choices, moved-object persistence, map save ownership, or viewer-vs-editor workspace design.\n- Use `wow-viewer-world-runtime-plan-set.md` when the problem is splitting `WorldScene`, extracting world-runtime services, suppressing repeated asset-miss churn such as `.skin` lookup spam, or sequencing terrain/WMO/MDX/overlay runtime ownership into `wow-viewer`.\n- Use `wow-viewer-m2-runtime-plan-set.md` when the problem is M2 runtime ownership, exact `%02d.skin` behavior, active section classification, material/effect routing, animation/lighting state, scene submission/batching, or planning how M2 rendering moves into `wow-viewer` instead of staying trapped in `MdxViewer`.\n- Use `m2-cross-build-native-investigation.md` when the problem is recovering native behavior differences across multiple client builds (for example 3.3.5 through 6.x) before committing parser or runtime ownership decisions.\n- Use `wow-viewer-bootstrap-layout-plan.md` when the problem is repo shape, solution structure, bootstrap scripts, project layout, or where each tool/app/lib should live.\n- Use `wow-viewer-shared-io-library-plan.md` when the problem is the broader ownership plan for reading/writing ADT, WDT, M2, MDX, WMO, PM4, DBC, BLP, placement, or related formats.\n- Use `wow-viewer-tool-inventory-cutover-plan.md` when the problem is inventorying old tools, deciding what migrates, what merges, what stays archaeology-only, and what becomes a first-class tool in the new repo.\n- Use `wow-viewer-cli-gui-surface-plan.md` when the problem is making tools available both as CLI commands and existing GUI panels over the same shared services.\n- Use `wow-viewer-tool-migration-sequence-plan.md` when the problem is phasing, dependencies, vertical slices, or what order to migrate tool families without exploding scope.\n\n## Deliverables\n\nReturn all items:\n\n1. the best prompt to run next\n2. why it is the right prompt for the current ask\n3. which companion prompts should follow after it\n4. what concrete repo/tool/file-type scope the next prompt should include\n5. what not to waste time on yet\n\n## First Output\n\nStart with:\n\n1. the exact planning problem you think the user is actually trying to solve\n2. the single best next prompt from the set above\n3. the concrete migration/tool scope that prompt should cover first", "variables": [], "notes": "Route wow-viewer migration work to the right detailed Codex prompt. Use when the task is choosing between PM4 implementation for inspect or audit or linkage or MSCN or unknowns work, shared-I/O implementation for ADT or WDT or WMO or BLP or DBC families, bootstrap, shared-library ownership planning, tool inventory, CLI or GUI parity, or migration sequencing. Arguments: Describe the tool family, file type, migration problem, or planning slice you want to attack.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/akspa0/parp-tools", "path": ".codex/prompts/wow-viewer-tool-suite-plan-set.md", "ref": "5608d59a180dc4296e29bc19be1a3cc5e94ef309", "url": "https://github.com/akspa0/parp-tools/blob/5608d59a180dc4296e29bc19be1a3cc5e94ef309/.codex/prompts/wow-viewer-tool-suite-plan-set.md", "key": "akspa0/parp-tools/.codex/prompts/wow-viewer-tool-suite-plan-set.md" } } }

wow-viewer Tool Suite Plan Set

About

Read First

Goal

Companion Prompts

Routing Rules

Deliverables

First Output

Install wow-viewer Tool Suite 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