magnus919_agent-skills/product-design-and-ux

Product Design and UX - Behavior-Ready Product Handoffs

Turn approved product scope into user-facing behavior that engineers can implement and people can recover from when things go wrong.

Why Install This Skill

Teams often agree on a feature but leave its navigation, permissions, failure recovery, interrupted work, and completion evidence implicit. That ambiguity becomes late rework, inaccessible paths, or a polished happy path that breaks in normal conditions.

This skill helps an agent turn validated evidence and a chosen scope into traceable outcomes, task and state models, interaction contracts, usability evidence, and an engineering handoff. It stays portable: no design application, component library, CSS, or proprietary workflow is required.

What You Get

Path	What it provides
SKILL.md	Compact workflow, routing, and completion rules.
references/	Detailed guidance for IA, content and cognitive demand, flows, contracts, patterns, usability, handoff, sources, and scenario probes.
templates/	Fillable traceability, flow/state, inventory, contract, usability, and handoff artifacts.

Quick Start

Give your agent validated evidence and an approved scope, then ask for a behavior handoff:

Define the task flow, recovery states, interface contract, and observable acceptance criteria for the approved invoice-dispute feature. Link each decision to the supplied evidence.

Triggers

• Product design, UX design, interaction design, information architecture, or navigation model.
• Task flows, user flows, state models, recovery paths, or interface behavior.
• Interaction contracts, responsive/reflow behavior, usability-study plans, or UX engineering handoffs.

Requirements

• Validated evidence and an approved product scope; use product-discovery or product-methodology when these are absent.
• No software dependencies, API keys, design tools, or frontend framework.
• Use web-accessibility for WCAG/ARIA conformance and accessibility-testing depth.