We start from how the overlay is actually read - primary actions, secondary noise, and how the layout holds at common aspect ratios - then lock that into a system before widgets are restyled.
Smaller engagements are a directed pass on a menu you already ship: spacing, type scale, palette, and matching hover and active states. Larger engagements are a complete overlay language: window chrome, tabs, sliders, pickers, notifications, and a reference layout for whoever writes the source.
The aim is a restrained, consistent interface that still belongs to the product. Controls that do not earn their place are removed.
This is for you if
- You have a working menu that needs a coherent visual system.
- You need art direction before source work begins.
- You want dark-surface rules that remain readable in motion.
Included
- Layout and hierarchy for one overlay or menu set
- Color, type, and spacing notes a coder can follow without guessing
- Hover, active, disabled, and focus states
- A reference frame for the primary window
- One revision round on the agreed direction
Notes
- Source implementation is ImGui Source, quoted separately.
- We work from screenshots, a running build, or a written spec.