Purpose

Make every important UI state intentional, testable and accessible.

When to use

• Designing or reviewing loading, empty, content, error, offline or permission states.
• Creating a screen state model before implementing Compose UI.
• Improving AI-generated UI that only handles the happy path.
• Connecting UI copy, affordances and tests to repository, network, Room, DataStore or Firebase behavior.

Inputs to inspect

• Gate result from design-test-gate.
• ViewModel state model and events.
• Repository/network/local/Firebase result types.
• Existing previews and tests.
• Error, permission, offline, auth and sync behavior.
• Accessibility labels and recovery actions.