What problem does it solve? When building game screens (Views) with the flix_game_engine, developers tend to reinvent rendering techniques or fall back to plain rectangles, producing flat visuals. This Skill provides a decision checklist and a translation dictionary that maps familiar web/Canvas/Shadertoy techniques (glow, gradients, particles, vignette, dithering) onto the engine's actual components. ## Core Features & Use Cases - Art-direction checklist: Forces you to pick a subject, three colors, and one constraint before writing code, then verify five minimum visual qualities (gradation, separation, layering, motion, readable shapes). - Technique translation table: Maps web techniques to engine parts such as Render.glowAt, Render.lightAt/darkAt, Render.vgrad, ShaderDoc fbm/worley, PxSprite/PxShade, Fx particles, and CameraRig shake, with verified quirks per engine version. - Reference library: Includes recipes showing four different art styles satisfying the same quality floor, a catalog of implemented-but-unused engine parts, and a workflow for rendering perfectly looping GIFs and converting them to WebP. - Use Case: When asked to "make this screen look better" or "give it a neon feel", consult the dictionary to select engine components (e.g., Add-blend glow plus a dark vignette) instead of hand-rolling effects. ## Quick Start Use the visual-dict skill to design the background and character visuals for my new game view before writing any rendering code.
