designing-ui-ux-prd

To convert a draft PRD into a UI/UX design document, ingest the draft from a specified path to extract core features, user types, and MVP scope, then generate page-by-page layouts, button mappings, and interaction definitions to lock the frontend direction.

The best way to define MVP frontend interactions from a product requirements document is to iterate with one-question-at-a-time clarifications, validating each UI/UX decision before proceeding to generate the final structured PRD.

Generating a UI/UX PRD does require specifying page-by-page layouts, button mappings, glyph suggestions, and interaction definitions to ensure a single, concrete frontend direction is fully locked for the MVP.

You can use this method to ingest existing draft PRDs from selected locations to automatically extract core features, user types, MVP scope, and constraints before structuring the final UI/UX interactions.

The one-question-at-a-time clarification process works by asking targeted UI/UX questions sequentially, ensuring each design decision is explicitly confirmed by the user before proceeding to the final PRD generation.

You should output the final structured UI/UX PRD to the /frontend directory, which consolidates the validated page layouts, button mappings, and interaction definitions into a single frontend direction.