aibdd-uiux-discovery-lite

To generate a UI brief without overdesigning, extract a happy-path visual scope from feature artifacts by selecting only feature-mentioned screens and primary component states, preventing state explosion and wasted iteration.

A happy-path UI/UX visual scope is a minimal boundary-aware design brief covering only primary canonical states and feature-mentioned screens, needed when drafting UI workflows where error, empty, and loading states must be excluded.

Extract canonical component states by compressing a component catalog and frame compositions from feature evidence into primary states only, avoiding full UX matrices and excluding error, empty, and loading state coverage.

Yes, you can derive a visual scope from discovery feature artifacts by selecting explicit screens first or using happy-scenario fallbacks, enforcing lite invariants to ensure only primary or canonical states are included in the output.

Generating a minimal UI design brief emits uiux-prompt.md and style-profile.yml files alongside a lite scope audit in the package design folder, serving as downstream-compatible deliverables for UI drawing workflows.

UI scope extraction excludes error and loading states because it applies lite invariants to enforce happy-path-only coverage, selecting primary canonical component states to prevent overdraw and state explosion during UI drafting.