メニュー
Route VIVERSE feature requests to the correct skill set based on project type. Use when the user asks about multiplayer, leaderboard, publishing, or other features that exist in both general and PlayCanvas Toolkit variants.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Three.js Polygon Streaming .xrg integration and debugging playbook for @polygon-streaming/web-player-threejs, including correct wrapper events, asset publishing, model fitting, and fallback replacement policy
Bundle entry for the exported VIVERSE PlayCanvas Toolkit workflow pack. Use when you want bundled VIVERSE PlayCanvas Toolkit skills, prompts, catalogs, and helper assets in one standalone package.
Collision detection patterns for Three.js games without physics engines
Protect third-party API keys by moving secret-bearing calls into VIVERSE Play Lambda scripts and keeping only non-secret user data in VIVERSE Storage.
Build or fix CPU racing drivers for Three.js or VIVERSE racing games. Use for waypoint loops, tile-to-route reconstruction, lap completion, recovery logic, and low-overhead debug workflows.
VIVERSE Login SDK integration for user authentication and SSO
| name | viverse-skill-router |
| description | Route VIVERSE feature requests to the correct skill set based on project type. Use when the user asks about multiplayer, leaderboard, publishing, or other features that exist in both general and PlayCanvas Toolkit variants. |
| user-invocable | false |
This skill resolves ambiguity when a user request could match both a general VIVERSE skill and a PlayCanvas Toolkit-specific skill.
It does not perform the work itself — it identifies the correct downstream skill and hands off.
Use this router when the user's request matches a keyword that exists in both skill sets:
viverse-leaderboard OR toolkit viverse-playcanvas-leaderboardviverse-multiplayer OR toolkit viverse-default-room-multiplayerviverse-world-publishing OR toolkit viverse-cli-publishCheck the user's workspace and context for these signals to determine project type:
| Signal Present | Route To |
|---|---|
packages/network/, toolkit-capability-catalog.json, or viverse-playcanvas-toolkit in dependencies | PlayCanvas Toolkit skills |
skills/viverse-playcanvas-toolkit/ exists in workspace | PlayCanvas Toolkit skills |
| User explicitly says "PlayCanvas Toolkit", "engine-only world", or "local world" | PlayCanvas Toolkit skills |
Raw <script src="viverse-sdk"> tags, no toolkit packages | General skills |
| Three.js, React Three Fiber, or vanilla JS project | General skills |
| User says "matchmaking", "named rooms", "host-authoritative", "custom state sync" | General viverse-multiplayer (toolkit doesn't cover this) |
| No clear project type detected | Ask user (see below) |
When both a root skill and a toolkit skill could match:
| Context | Skill | Path |
|---|---|---|
| General VIVERSE project (any framework) | viverse-leaderboard | skills/viverse-leaderboard/SKILL.md |
| PlayCanvas Toolkit local world | viverse-playcanvas-leaderboard | skills/viverse-playcanvas-toolkit/skills/viverse-playcanvas-leaderboard/SKILL.md |
| Context | Skill | Path |
|---|---|---|
| Full matchmaking, named rooms, host-authoritative, custom sync | viverse-multiplayer | skills/viverse-multiplayer/SKILL.md |
| Default-room shared presence only (PlayCanvas Toolkit) | viverse-default-room-multiplayer | skills/viverse-playcanvas-toolkit/skills/viverse-default-room-multiplayer/SKILL.md |
| Context | Skill | Path |
|---|---|---|
| General VIVERSE world publishing | viverse-world-publishing | skills/viverse-world-publishing/SKILL.md |
| PlayCanvas Toolkit local build → VIVERSE CLI | viverse-cli-publish | skills/viverse-playcanvas-toolkit/skills/viverse-cli-publish/SKILL.md |