canvas-performance-optimization
/canvas-performance-optimization
Use when an isometric Canvas game drops frames, to cut draw calls and allocations and hold a steady 60fps.
- Author
- 0xheycat ↗
- Repository
- isometric-game-skills ↗
- Licence
- MIT
- Last repository change
- 12.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when an isometric Canvas game drops frames, to cut draw calls and allocations and hold a steady 60fps.
Original author description
Use when an isometric Canvas game drops frames, to cut draw calls and allocations and hold a steady 60fps.
How it works
- Overview
- When to Use
- Process
- Rationalizations (Stop Lying to Yourself)
- Red Flags - STOP if you catch yourself:
- Verification
SKILL.md preview
--- name: canvas-performance-optimization description: Use when an isometric Canvas game drops frames, to cut draw calls and allocations and hold a steady 60fps. license: MIT --- # Canvas Performance Optimization ## Overview Isometric games die by a thousand draw calls. This skill profiles the frame, culls off-screen tiles, batches from the atlas, and removes per-frame allocations to hit a stable 60fps. ## When to Use - Frame rate drops or stutters. - Large maps lag when panning. - You suspect GC pauses or overdraw. ## Process 1. Profile first - measure where the frame time actually goes. 2. Cull: only draw tiles/objects inside the viewport. 3. Batch draws from one atlas to minimize texture binds. 4. Cache static layers (ground) to an offscreen canvas; redraw only when it changes. 5. Eliminate per-frame allocations (reuse arrays/objects). 6. Avoid sub-pixel blits; snap to integer pixels. 7. Re-profile to confirm the fix, do not assume. ```text Profile -> Cull -> Batch -> Cache static layer -> Kill allocations -> Re-profile ``` ## Rationalizations (Stop Lying to Yourself) | Excuse | Reality | |---|---| | "I know what is slow without profiling" | Guessing wastes hours on the wrong thing. Profile first. | | "Redrawing the ground every frame is fine" | Static ground should be cached. Redraw only on change. | ## Red Flags - STOP if you catch yourself: - Optimizing before profiling. - Redrawing static layers every frame. - Allocating inside the render loop. ## Verification You are NOT done until every box is checked: - [ ] Frame time was profiled before and after. - [ ] Off-screen content is culled and static layers cached. - [ ] No allocations occur inside the render loop; 60fps holds.
Versions
The database has no other skills named canvas-performance-optimization.
Database snapshot: 13.11.2026 · package version 8350c85597bd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100game-performance
Hold frame budgets through per-frame profiling, object pooling, draw-call batching, and allocation discipline. Use when a game stutters, drops frames, or needs optimization triage. - 100performance-optimization
Use to profile and improve game FPS, CPU/GPU cost, frame pacing, memory, Canvas or Three.js rendering without gameplay changes. - 90godot-performance-optimization
Expert blueprint for performance profiling and optimization (frame drops, memory leaks, draw calls) using Godot Profiler, object pooling, visibility culling, and bottleneck identification. Use when diagnosing lag, optimizing for target FPS, or reducing memory usage. Keywords… - 95reduce-draw-calls
Use when a PlayCanvas app has too many draw calls or is CPU-bound, before hand-merging meshes or writing custom renderers. - 100performance-optimization
Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets.… - 100performance-optimization
Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets.…