ux-design

To write a game UX spec aligned with your GDD, you need a context-first workflow that reads existing GDD UI requirements, player journey data, and game concepts. This approach grounds your UX specifications in actual project constraints, ensuring navigation flows and interaction states match intended player goals.

Designing a game HUD using interaction patterns requires mapping data requirements and events to a reusable pattern library. By applying a HUD design mode, you can generate structured documentation that defines navigation, states, and interaction maps based on established studio templates.

Yes, you can build an interaction pattern catalog for an existing project through retrofit detection. The system scans existing files and UX specs via glob and grep reads, allowing you to extract and document reusable interaction patterns already present in your game.

While not strictly mandatory, providing accessibility requirements and platform or input preferences is highly recommended. Including this context ensures the generated UX specifications account for specific input methods and accessibility constraints, producing more robust and compliant interactive UI design planning.

Structuring a player journey flow for a main menu involves guided section-by-section writing that connects screen states to player goals. By reading journey context and GDD requirements, the system incrementally drafts UX specs covering navigation, events, and interaction maps directly into your design outputs.