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.

3d-games - Skill - OpenSmartRoute

Imported from sickn33/agentic-awesome-skills (skills/game-development/3d-games/SKILL.md). Install upstream with npx skills add sickn33/agentic-awesome-skills --skill 3d-games. Copyright stays with the author.

3D Game Development

Principles for 3D game systems.

1. Rendering Pipeline

Stages

1. Vertex Processing → Transform geometry
2. Rasterization → Convert to pixels
3. Fragment Processing → Color pixels
4. Output → To screen

Optimization Principles

Technique	Purpose
Frustum culling	Don't render off-screen
Occlusion culling	Don't render hidden
LOD	Less detail at distance
Batching	Combine draw calls

2. Shader Principles

Shader Types

Type	Purpose
Vertex	Position, normals
Fragment/Pixel	Color, lighting
Compute	General computation

When to Write Custom Shaders

Special effects (water, fire, portals)
Stylized rendering (toon, sketch)
Performance optimization
Unique visual identity

3. 3D Physics

Collision Shapes

Shape	Use Case
Box	Buildings, crates
Sphere	Balls, quick checks
Capsule	Characters
Mesh	Terrain (expensive)

Principles

Simple colliders, complex visuals
Layer-based filtering
Raycasting for line-of-sight

4. Camera Systems

Camera Types

Type	Use
Third-person	Action, adventure
First-person	Immersive, FPS
Isometric	Strategy, RPG
Orbital	Inspection, editors

Camera Feel

Frame-rate-independent smoothing; test camera collision and teleports
Collision avoidance
Look-ahead for movement
FOV changes for speed

5. Lighting

Light Types

Type	Use
Directional	Sun, moon
Point	Lamps, torches
Spot	Flashlight, stage
Ambient	Base illumination

Performance Consideration

Real-time shadows are expensive
Bake when possible
Shadow cascades for large worlds

6. Level of Detail (LOD)

LOD Strategy

Distance	Model
Near	Full detail
Medium	Reduced detail based on measured visual error
Far	Low-detail mesh or billboard when visually appropriate

7. Anti-Patterns

❌ Don't	✅ Do
Mesh colliders everywhere	Simple shapes
Real-time shadows on mobile	Baked or blob shadows
One LOD for all distances	Distance-based LOD
Unoptimized shaders	Profile and simplify

Remember: 3D is about illusion. Create the impression of detail, not the detail itself.

When to Use

Use when implementing or profiling a 3D rendering pipeline, shaders, colliders, cameras, lighting or level-of-detail transitions.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Verification

Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.

Install 3d-games 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.

3d-games

About