hud-feedback · diff
git:20260912.9399f33 to git:20260913.c18e2d8
20 added, 6 removed. Audit A to A.
---
name: hud-feedback
- description: Generic HUD that reports state. No quest-arrow carpet.
+ description: Use when important gameplay state, action failure, danger, resource condition, objectives, or status changes are invisible, ambiguous, color-only, or buried behind menus.
---
- # HUD feedback
+ # HUD Feedback
- Ask: minimal | combat-full | sim-dials.
- Show why a press did nothing. Wear warn at ≤3 hits if durability is consume. Compass may mark player pins, not every quest.
- Colorblind pass: shape + text, not hue only.
+ This skill owns **player-facing state communication**, not the underlying gameplay state or thresholds.
- Accept: danger is readable without a menu.
+ ## Modes
+
+ | Mode | Information density |
+ |---|---|
+ | minimal | only project-defined critical state |
+ | combat-full | combat/resource/status state needed during action |
+ | sim-dials | denser simulation/management state |
+
+ Each HUD element names the authoritative source field/event and presentation priority. Thresholds such as low health, durability warning, ammo, heat or timer boundaries come from their owner (`durability-economy`, combat/resource systems, etc.); this skill does not hardcode them.
+
+ When an action fails, show an authored reason when useful: unavailable resource, cooldown, invalid target, blocked interaction, or another project state. Do not infer logic from animation alone.
+
+ Critical information is not encoded by color/hue alone when another distinguishable channel is required; use shape, icon, text, pattern, position, audio/haptic or another project-appropriate alternative. `a11y-controls` owns user preferences; `ui-hud-focus` owns interactive focus.
+
+ ## Acceptance
+
+ Test critical states at their real source boundaries with color-reduced/no-audio/reduced-flash settings that the project supports. A player can identify the state and reason without opening an unrelated menu. Log source event/value and rendered indicator state; a screenshot alone does not prove timing correctness.