game-engine
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.
Best use case
game-engine is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using game-engine should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/game-engine/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How game-engine Compares
| Feature / Agent | game-engine | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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` |
Related Skills
Socratic Method: The Dialectic Engine
This skill transforms Claude into a Socratic agent — a cognitive partner who guides
vertex-engine-inspector
Inspect and validate Vertex AI Agent Engine deployments including Code Execution Sandbox, Memory Bank, A2A protocol compliance, and security posture. Generates production readiness scores. Use when asked to inspect, validate, or audit an Agent Engine deployment. Trigger with "inspect agent engine", "validate agent engine deployment", "check agent engine config", "audit agent engine security", "agent engine readiness check", "vertex engine health", or "reasoning engine status".
engineering-features-for-machine-learning
This skill empowers Claude to perform feature engineering tasks for machine learning. It creates, selects, and transforms features to improve model performance. Use this skill when the user requests feature creation, feature selection, feature transformation, or any request that involves improving the features used in a machine learning model. Trigger terms include "feature engineering", "feature selection", "feature transformation", "create features", "select features", "transform features", "improve model performance", and similar phrases related to feature manipulation.
feature-engineering-helper
Feature Engineering Helper - Auto-activating skill for ML Training. Triggers on: feature engineering helper, feature engineering helper Part of the ML Training skill category.
conducting-chaos-engineering
This skill enables Claude to design and execute chaos engineering experiments to test system resilience. It is used when the user requests help with failure injection, latency simulation, resource exhaustion testing, or resilience validation. The skill is triggered by discussions of chaos experiments (GameDays), failure injection strategies, resilience testing, and validation of recovery mechanisms like circuit breakers and retry logic. It leverages tools like Chaos Mesh, Gremlin, Toxiproxy, and AWS FIS to simulate real-world failures and assess system behavior.
adk-engineer
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.
ROS 2 Engineering Skills
A progressive-disclosure skill for ROS 2 development — from first workspace to
using-dbt-for-analytics-engineering
Builds and modifies dbt models, writes SQL transformations using ref() and source(), creates tests, and validates results with dbt show. Use when doing any dbt work - building or modifying models, debugging errors, exploring unfamiliar data sources, writing tests, or evaluating impact of changes.
../../../engineering-team/playwright-pro/skills/testrail/SKILL.md
No description provided.
../../../engineering/autoresearch-agent/skills/status/SKILL.md
No description provided.
../../../engineering/autoresearch-agent/skills/run/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/review/SKILL.md
No description provided.