product-design

Translate discovery insights into IA documents, user flows, wireframes, and prototype briefs.

Updated Nov 8, 2025
One-click install
npx skills add https://github.com/ivanyeors/product-agentic-templates --skill product-design-ivanyeors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-design
Source: https://github.com/ivanyeors/product-agentic-templates/tree/main/.cursor/skills/02-product-design
Command: npx skills add https://github.com/ivanyeors/product-agentic-templates --skill product-design-ivanyeors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates discovery insights into a clear, validated UX design ready for implementation, bridging gaps between research and execution.

Core Features & Use Cases

  • Information Architecture planning and site map creation
  • User flow design with edge-case coverage and recovery paths
  • Wireframing, interaction design, and accessibility planning
  • Prototype specification and HANDOFF to Frontend Design

Quick Start

From discovery artifacts, generate the IA document, user flows, wireframes, and a prototype brief to begin Frontend Design.

Frequently Asked Questions about product-design

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

FAQPage Schema
How do I translate user research into validated UX design?

To translate user research into validated UX design, process discovery insights to generate information architecture documents, user flows, wireframes, and prototype briefs. This enforces structure before style and ensures edge cases are covered before frontend handoff.

What is the best way to plan information architecture and user flows for a new product?

The best way to plan information architecture and user flows is to map discovery insights into structured IA documents and flow diagrams. This approach ensures edge-case coverage and defines recovery paths before moving into wireframing and interaction design.

How do I create wireframes and prototype specifications that include accessibility planning?

Creating wireframes and prototype specifications with accessibility planning involves generating structured design artifacts from user flows. This process integrates accessibility requirements directly into interaction design and prototype briefs for frontend handoff.

Can I use this UX design process for gate reviews across the product lifecycle?

Yes, you can use this UX design process for gate reviews across the product lifecycle. It systematically translates discovery insights into validated design artifacts, ensuring structure before style and covering accessibility requirements for review checkpoints.

Do I need discovery artifacts to start generating UX design documents?

Yes, discovery artifacts are required to start generating UX design documents. The process uses these insights to produce information architecture documents, user flows, wireframes, and prototype briefs to begin frontend design.

Why should I enforce structure before style in UX wireframing?

Enforcing structure before style in UX wireframing ensures that information architecture and user flows are validated before visual design begins. This approach covers edge cases and accessibility requirements, preventing structural rework during frontend handoff.