Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
phaser4 - Skill - OpenSmartRoute
Skillv1.0.0
phaser4
This project uses Phaser 4 and should be treated as a browser game project rather than a generic TypeScript app.
Instruction file imported from FreezingMoon/AncientBeast (.github/instructions/phaser4.instructions.md). Copyright stays with the author.
Phaser 4 instructions for Ancient Beast
This project uses Phaser 4 and should be treated as a browser game project rather than a generic TypeScript app.
Prefer Phaser 4 scene, game object, and animation APIs already used in this codebase.
Keep rendering concerns separated from core turn-based game logic.
Preserve asset loading, scene creation, and lifecycle patterns that align with this repo.
When modifying gameplay, consider both simulation logic and visual presentation.
Keep edits compatible with Vite and the repository’s Jest setup.
Do not rewrite the project around React, a different engine, or a new framework unless explicitly requested.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install phaser4 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.
{
"ocm": "1",
"id": "freezingmoon-ancientbeast-phaser4-instructions",
"kind": "skill",
"name": "phaser4",
"description": "This project uses Phaser 4 and should be treated as a browser game project rather than a generic TypeScript app.",
"publisher": "FreezingMoon",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"This project uses Phaser 4 and should be treated as a browser game project rather than a generic TypeScript app."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/FreezingMoon/AncientBeast",
"path": ".github/instructions/phaser4.instructions.md",
"ref": "f92dafe57088c87828a6695af351c3dd71e054a6",
"url": "https://github.com/FreezingMoon/AncientBeast/blob/f92dafe57088c87828a6695af351c3dd71e054a6/.github/instructions/phaser4.instructions.md",
"key": "FreezingMoon/AncientBeast/.github/instructions/phaser4.instructions.md"
},
"applies_to": "**/*.{ts,js,tsx,jsx}"
},
"instructions": "# Phaser 4 instructions for Ancient Beast\n\nThis project uses Phaser 4 and should be treated as a browser game project rather than a generic TypeScript app.\n\n- Prefer Phaser 4 scene, game object, and animation APIs already used in this codebase.\n- Keep rendering concerns separated from core turn-based game logic.\n- Preserve asset loading, scene creation, and lifecycle patterns that align with this repo.\n- When modifying gameplay, consider both simulation logic and visual presentation.\n- Keep edits compatible with Vite and the repository’s Jest setup.\n- Do not rewrite the project around React, a",
"cost": {
"context_tokens": 166
}
}
Fetch it by URL: GET /api/v1/registry/freezingmoon-ancientbeast-phaser4-instructions/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
