Skills github awesome-copilot

game-engine

Use it when:
You're making a game that runs in the browser, from a Breakout clone or a platformer to a 3D scene.
It does:
Guides the agent through the game loop, Canvas or WebGL rendering, collision, physics, controls, audio and multiplayer, with step lists for a 2D game, a 3D game and publishing.
You get:
Browser game code in HTML5 and JavaScript, optionally started from one of its five working templates, with nine reference files to draw on.
Works with:
Plain JavaScript, or frameworks such as Phaser, Three.js, Babylon.js, A-Frame and PlayCanvas.

TL;DR

Reference material and short build steps for web game development. Its core is the game loop: read input, update state, render, driven by requestAnimationFrame. Around it, the skill covers when to use Canvas 2D, WebGL, SVG or CSS; AABB, circle and SAT collision in 2D, bounding volumes and raycasting in 3D; simple Newtonian movement and gravity; and the Web Audio API. Short workflows outline a basic 2D game, a 3D game built on a framework, and publishing: optimizing assets, testing across browsers, choosing a platform, monetizing and promoting. Starter templates in its assets folder include a Breakout-style paddle game, a maze game with device-orientation controls, a Phaser platformer and a simple 2D engine with collisions. References cover web APIs, algorithms, 3D and WebXR, controls, publishing and a glossary. A troubleshooting table answers common problems: a blank canvas, game speed that varies with frame rate, unreliable collisions, audio that won't play before a click, and a lost WebGL context.

Summarizes the skill at 797337f.

npx skills add https://github.com/github/awesome-copilot --skill game-engine
Total Downloads
13,400 on skills.sh, Nov 9, 2026
Repo stars
40,943 github/awesome-copilot
First seen
Feb 25, 2026 on skills.sh
Weekly Downloads
108
+29% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 2184
Sep 2888
Oct 5124
Oct 12105
Oct 19112
Oct 26150
Nov 2114
Nov 9108
Category

Guides for frameworks, databases and SDKs, mostly from their vendors.

Make games: design, genres, game feel and game-jam workflows, whatever the engine.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.

Type

A multi-step process the agent follows: interview, debug, run a TDD loop, review.

Effect

Its own steps create or change files, git state or local tools.

Needs

Instructions only. Works in any agent that supports skills.

Publisher

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.

Topics
Stack

SKILL.md

From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: game-engine
description: 'Expert skill for building web-based game engines and games using HTML5, Canvas, WebGL, and JavaScript. Use when asked to create games, build game engines, implement game physics, handle collision detection, set up game loops, manage sprites, add game controls, or work with 2D/3D rendering. Covers techniques for platformers, breakout-style games, maze games, tilemaps, audio, multiplayer via WebRTC, and publishing games.'

Game Engine Skill

Build web-based games and game engines using HTML5 Canvas, WebGL, and JavaScript. This skill includes starter templates, reference documentation, and step-by-step workflows for 2D and 3D game development with frameworks such as Phaser, Three.js, Babylon.js, and A-Frame.

When to Use This Skill

  • Building a game engine or game from scratch using web technologies
  • Implementing game loops, physics, collision detection, or rendering
  • Working with HTML5 Canvas, WebGL, or SVG for game graphics
  • Adding game controls (keyboard, mouse, touch, gamepad)
  • Creating 2D platformers, breakout-style games, maze games, or 3D experiences
  • Working with tilemaps, sprites, or animations
  • Adding audio to web games
  • Implementing multiplayer features with WebRTC or WebSockets
  • Optimizing game performance
  • Publishing and distributing web games

Prerequisites

  • Basic knowledge of HTML, CSS, and JavaScript
  • A modern web browser with Canvas/WebGL support
  • A text editor or IDE
  • Optional: Node.js for build tooling and local development servers

Core Concepts

The following concepts form the foundation of every web-based game engine.

Game Loop

Every game engine revolves around the game loop -- a continuous cycle of:

  1. Process Input - Read keyboard, mouse, touch, or gamepad input
  2. Update State - Update game object positions, physics, AI, and logic
  3. Render - Draw the current game state to the screen

Use requestAnimationFrame for smooth, browser-optimized rendering.

Rendering
  • Canvas 2D - Best for 2D games, sprite-based rendering, and tilemaps
  • WebGL - Hardware-accelerated 3D and advanced 2D rendering
  • SVG - Vector-based graphics, good for UI elements
  • CSS - Useful for DOM-based game elements and transitions
Physics and Collision Detection
  • 2D Collision Detection - AABB, circle, and SAT-based collision
  • 3D Collision Detection - Bounding box, bounding sphere, and raycasting
  • Velocity and Acceleration - Basic Newtonian physics for movement
  • Gravity - Constant downward acceleration for platformers
Controls
  • Keyboard - Arrow keys, WASD, and custom key bindings
  • Mouse - Click, move, and pointer lock for FPS-style controls
  • Touch - Mobile touch events and virtual joysticks
  • Gamepad - Gamepad API for controller support
Audio
  • Web Audio API - Programmatic sound generation and spatial audio
  • HTML5 Audio - Simple audio playback for music and sound effects

Step-by-Step Workflows

Creating a Basic 2D Game
  1. Set up an HTML file with a <canvas> element
  2. Get the 2D rendering context
  3. Implement the game loop using requestAnimationFrame
  4. Create game objects with position, velocity, and size properties
  5. Handle keyboard/mouse input for player control
  6. Implement collision detection between game objects
  7. Add scoring, lives, and win/lose conditions
  8. Add sound effects and music
Building a 3D Game
  1. Choose a framework (Three.js, Babylon.js, A-Frame, or PlayCanvas)
  2. Set up the scene, camera, and renderer
  3. Load or create 3D models and textures
  4. Implement lighting and shaders
  5. Add physics and collision detection
  6. Implement player controls and camera movement
  7. Add audio and visual effects
Publishing a Game
  1. Optimize assets (compress images, minify code)
  2. Test across browsers and devices
  3. Choose distribution platform (web, app stores, game portals)
  4. Implement monetization if needed
  5. Promote through game communities and social media

Game Templates

Starter templates are available in the assets/ folder. Each template provides a complete, working example that can be used as a starting point for a new project.

Template Description
paddle-game-template.md 2D Breakout-style game with pure JavaScript
2d-maze-game.md Maze game with device orientation controls
2d-platform-game.md Platformer game using Phaser framework
gameBase-template-repo.md Game base template repository structure
simple-2d-engine.md Simple 2D platformer engine with collisions

Reference Documentation

Detailed reference material is available in the references/ folder. Consult these files for in-depth coverage of specific topics.

Reference Topics Covered
basics.md Game development introduction and anatomy
web-apis.md Canvas, WebGL, Web Audio, Gamepad, and other web APIs
techniques.md Collision detection, tilemaps, async scripts, audio
3d-web-games.md 3D theory, frameworks, shaders, WebXR
game-control-mechanisms.md Touch, keyboard, mouse, and gamepad controls
game-publishing.md Distribution, promotion, and monetization
algorithms.md Raycasting, collision, physics, vector math
terminology.md Game development glossary
game-engine-core-principles.md Core design principles for game engines

Troubleshooting

Issue Solution
Canvas is blank Check that you are calling drawing methods after getting the context and inside the game loop
Game runs at different speeds Use delta time in update calculations instead of fixed values
Collision detection is inconsistent Use continuous collision detection or reduce time steps for fast-moving objects
Audio does not play Browsers require user interaction before playing audio; trigger playback from a click handler
Performance is poor Profile with browser dev tools, reduce draw calls, use object pooling, and optimize asset sizes
Touch controls are unresponsive Prevent default touch behavior and handle touch events separately from mouse events
WebGL context lost Handle the webglcontextlost event and restore state on webglcontextrestored