UI Kit Architecture

features/ui-kit is an isolated feature, not a dumping ground. It owns reusable visual primitives and their implementation details; screens compose those primitives and own routing and game actions.

Ownership

• ui-kit may import only shared/ code and its own files. Never import a screen, router, game domain, combat system, or another vertical feature.
• A UI-kit component receives data and callbacks through props. It must not navigate, mutate gameplay state, or decide screen-specific copy.
• Export the usable component from features/ui-kit/index.ts; keep renderer, styling, Patch9 slices, and assets private to its component directory.
• Each screen assembles its UI from public UI-kit components. The screen owns route transitions, pause/combat callbacks, feature-specific labels, and its layout composition.