UI/UX Content and Interaction

Purpose

Make the interface communicate what is happening, what the user can do, and what will happen next. Content and interaction are part of the product logic, not polish added after layout.

Procedure

Read content-interaction-checklist.md when the surface has meaningful copy, forms, feedback, accessibility semantics, or failure states. If an informal element name could select a different semantic/state model, read ui-vocabulary.md. If an action is delayed, side-effecting, or can be re-triggered, read action-execution-posture.md. If the product itself lets a user direct an AI agent or automation, read agent-action-surface.md. Use interaction-contract.md as a starting format for a bounded interaction decision; omit irrelevant rows.