What problem does it solve? Working with classic-wgl's platform layer requires understanding three divergent backends (native winit/glutin, web web-sys, headless EGL) plus subtle input, timing, and build quirks that are easy to get wrong when porting, debugging, or extending the engine. ## Core Features & Use Cases - Backend Reference: Explains the Platform trait and its three implementations — NativePlatform (winit + glutin), WebPlatform (web-sys + trunk), and HeadlessPlatform (EGL pbuffer) — including event loops and GL context setup. - Input & Timing Semantics: Details InputState fields, mouse wheel sign conventions and decay, frame timing (real delta, CLASSIC_FIXED_DT), and deterministic headless runs via CLASSIC_FRAMES. - Known Divergences: Documents non-functional or divergent behavior such as unimplemented native accessors, stale web resize closures, and frame_had_click persistence. - Use Case: When a golden test fails in CI, use this Skill to understand how CLASSIC_HEADLESS, CLASSIC_FRAMES, and CLASSIC_FIXED_DT interact to produce deterministic headless renders. ## Quick Start Ask the AI to explain how mouse wheel input differs between the native and web backends of classic-wgl and how the engine normalizes it.