メニュー
Use when building or reviewing Air Jam controller surfaces so touch controls stay simple, readable, and game-appropriate instead of drifting into dense web-app UI patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | controller-ui |
| description | Use when building or reviewing Air Jam controller surfaces so touch controls stay simple, readable, and game-appropriate instead of drifting into dense web-app UI patterns. |
Use this skill for controller gameplay and lobby surfaces.
docs/generated/controller-ui.mddocs/visual-system.mddocs/iconography.mddocs/composition-shell-contract.md when the controller needs lobby/status/lifecycle shell workinset-0 rootFor controller shell work:
RuntimeShellHeader, LifecycleActionGroup, useControllerShellStatus, useControllerLifecyclePermissions, and useControllerLifecycleIntents for the default composition pathPrefer:
@tabler/icons-react for general UI and system actionsreact-icons Gi* exports for gameplay-specific concepts such as abilities, status effects, pickups, and damage typesDo not mix icon packs casually throughout the tree.
Prefer local wrapper modules so icon usage stays curated and replaceable.
If the project uses react-icons Gi* icons, remember that the underlying Game Icons set has its own attribution requirements.
Downstream teams remain responsible for how they satisfy those requirements.
Use when building or reviewing the Air Jam host shell so the active game surface stays full-frame, overlays stay modular, and host UI does not interfere with gameplay layout.
Use when creating or refactoring gameplay code in an Air Jam project and you need guidance on host vs controller vs domain boundaries, modular structure, and when to refactor before implementing.
Use when creating reusable gameplay objects or scene presets so prefabs stay declarative, configurable, and ready for future tooling such as previews and scanned catalogs.
Use when debugging or validating an Air Jam project so diagnostics, logging, and tests stay intentional, structured, and aligned with the project architecture.
Use when an Air Jam task needs canonical guidance and you need to know which local docs to read, when hosted docs are appropriate, and how to avoid reading the whole docs tree unnecessarily.
Use when building or reviewing a 2D Air Jam game with canvas so simulation, rendering, SVG/sprite assets, scaling, and collision stay clean instead of collapsing into DOM-heavy ad hoc logic.