Agent skill · magnus919
product-design-and-ux
Define user-facing product behavior from validated evidence and approved scope. Use for information architecture, task flows, state and recovery models, interface contracts, usability-study plans, interaction-pattern tradeoffs, or engineering UX handoffs. Use after product discovery and product decisions; route WCAG/ARIA conformance work to web-accessibility and formal software specifications to spec-driven-development.
What it needs
About 2k tokens when loaded.
What this skill does
Product Design and UX Turn validated evidence and chosen scope into observable behavior people can complete and recover from. Design the interaction, not the brand, pixels, CSS, component implementation, or a particular tool. Entry Check Confirm the approved scope, outcome, users or roles, evidence links, constraints, measurable experience goals, and open product decisions. Record missing inputs rather than inventing them. Need stakeholder evidence, validation, or raw research? Use product-discovery. Need prioritization, scope, or why a feature is being built? Use product-methodology. Need WCAG, ARIA, native semantics, or accessibility testing depth? Use web-accessibility. Need an approved interaction contract translated into a software specification and delivery gates? Use spec-driven-development. Workflow 1. Trace each outcome and design decision to evidence with templates/outcomes-to-design.md. Optional personas or jobs must change a decision and cite evidence; do not create decorative demographics. 2. Establish information architecture from goals, content objects, terminology, permissions, findability, and service context. Read references/information-architecture.md. 3. Define consequential labels, instructions, status, errors, and completion content; review the task's memory, choice, switching, interruption, and recovery demands. Use heuristics to generate testable questions, not verdicts. Read references/content-and-cognitive-demand.md. 4. Model important tasks, including forces that create decisions, alternatives, interruption, re-entry, cancellation, recovery, irreversible actions, side effects, permission changes, and completion evidence. Read references/task-flows-and-state-models.md and use templates/task-flow-state-model.md. 5. Inventory only states forced by the flow, data, permissions, connectivity, and risk. Record risky omissions. Use templates/screen-state-inventory.md. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/product-design-and-ux