signal

Use this skill whenever introducing a new Go programming concept that needs to be explained visually to beginners. Triggers when the user asks to explain, illustrate, animate, or teach any Go concept — including but not limited to: variables, functions, packages, imports, structs, interfaces, goroutines, channels, error handling, maps, slices, pointers, closures, or methods. Also triggers when the user says things like "add a new scene", "introduce X concept", "animate how X works", or "show the next concept". Always use this skill before writing any animation code — it defines the entire design system, analogy model, and scene structure that all Go animations must follow.

How to write and extend beginner mode content — pre-level concept briefings for new players

How to add new game content (chapters, bosses, story) to SIGNAL

Audit engine output patterns for common Go pitfalls — ensures every step has targeted feedback for Printf/Println, whitespace, format mismatches, and other gotchas

How to write and tune AI system prompts for Maya's 3-tier LLM backend

How to write zen rules for new SIGNAL levels — idiomatic Go detection, jolts, suggestions, testing

How to build boss fight encounters in SIGNAL — combat loop, visual effects, jeopardy, and content authoring

How to write game logic in SIGNAL — pure functions, state management, persistence

How to paint scenes, characters, and animations for SIGNAL's 2D pixel art cinematics

How to build UI components that match SIGNAL's visual language and tech stack

How to write narrative content for SIGNAL — Maya's voice, event timing, story continuity

How to visually validate scenes, characters, and animations using the Playwright screenshot pipeline