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.
2d-games - Skill - OpenSmartRoute
Skillv1.0.0
2d-games
2D game development principles. Sprites, tilemaps, physics, camera.
Imported from ndc87/MSTE_Baitap03 (.antigravity/.agent/skills/game-development/2d-games/SKILL.md). Install upstream with npx skills add ndc87/MSTE_Baitap03 --skill 2d-games. Copyright stays with the author.
2D Game Development
Principles for 2D game systems.
1. Sprite Systems
Sprite Organization
Component
Purpose
Atlas
Combine textures, reduce draw calls
Animation
Frame sequences
Pivot
Rotation/scale origin
Layering
Z-order control
Animation Principles
Frame rate: 8-24 FPS typical
Squash and stretch for impact
Anticipation before action
Follow-through after action
2. Tilemap Design
Tile Considerations
Factor
Recommendation
Size
16x16, 32x32, 64x64
Auto-tiling
Use for terrain
Collision
Simplified shapes
Layers
Layer
Content
Background
Non-interactive scenery
Terrain
Walkable ground
Props
Interactive objects
Foreground
Parallax overlay
3. 2D Physics
Collision Shapes
Shape
Use Case
Box
Rectangular objects
Circle
Balls, rounded
Capsule
Characters
Polygon
Complex shapes
Physics Considerations
Pixel-perfect vs physics-based
Fixed timestep for consistency
Layers for filtering
4. Camera Systems
Camera Types
Type
Use
Follow
Track player
Look-ahead
Anticipate movement
Multi-target
Two-player
Room-based
Metroidvania
Screen Shake
Short duration (50-200ms)
Diminishing intensity
Use sparingly
5. Genre Patterns
Platformer
Coyote time (leniency after edge)
Jump buffering
Variable jump height
Top-down
8-directional or free movement
Aim-based or auto-aim
Consider rotation or not
6. Anti-Patterns
ā Don't
ā Do
Separate textures
Use atlases
Complex collision shapes
Simplified collision
Jittery camera
Smooth following
Pixel-perfect on physics
Choose one approach
Remember: 2D is about clarity. Every pixel should communicate.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/ndc87-mste-baitap03-2d-games/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
