prd-ux

Translate PRDs into UX foundations with six designer mindset passes.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/min-hinthar/mandalay-morning-star-delivery-app --skill prd-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-ux
Source: https://github.com/min-hinthar/mandalay-morning-star-delivery-app/tree/main/.claude/skills/prd-ux
Command: npx skills add https://github.com/min-hinthar/mandalay-morning-star-delivery-app --skill prd-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translate PRDs into actionable UX foundations to reduce design churn and misinterpretation.

Core Features & Use Cases

  • Enforces six designer mindset passes before visual specs
  • Produces IA-focused UX handoffs and documentation
  • Use Case: transform a PRD into a complete UX spec for a new feature, enabling design and engineering alignment.

Quick Start

Provide a PRD document and request a UX spec outline following the six passes.

Frequently Asked Questions about prd-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate PRDs into UX foundations for feature planning?

This Skill converts requirements into information architecture, flows, and handoff-ready documentation by enforcing six designer mindset passes before generating any visual specifications, ensuring proper UX foundations.

What is the six pass design process for UX specs?

The six pass process enforces six distinct designer mindset evaluations over a PRD before visual specs, mapping structured outputs back to original requirements to reduce design churn and misinterpretation across teams.

Can I use this to generate IA and flows from a product requirements document?

Yes, you generate information architecture and flows by providing a PRD document and requesting a UX spec outline, which produces IA-focused handoffs mapped directly to the original product requirements.

Does converting PRDs with this approach require existing design components?

No, converting PRDs does not require existing design components because the workflow operates solely on the references component, applying six mindset passes to requirements before any visual specification phase begins.

What is the best way to align product, design, and engineering teams on UX handoffs?

The best way to align teams on UX handoffs is exporting a structured UX spec file from the PRD that maps information architecture and flows directly to original requirements, ensuring cross-functional understanding.

Why do design teams experience churn when interpreting PRDs?

Design teams experience churn interpreting PRDs due to misalignment between requirements and visual specs, which this Skill mitigates by enforcing six mindset passes before design execution and mapping outputs to original requirements.