ux-design

Improve user flows, navigation, onboarding, and interaction design for SaaS interfaces.

232|43|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill ux-design-whawkinsiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/whawkinsiv/solo-founder-skills/tree/main/skills/ux-design
Command: npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill ux-design-whawkinsiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps founders eliminate confusing navigation, clunky user flows, ineffective onboarding, and inaccessible interfaces so users can complete tasks with less friction.

Core Features & Use Cases

  • Information Architecture: Structure navigation, URLs, page hierarchies, and content around user goals.
  • Flow and Interaction Design: Reduce unnecessary steps, choose appropriate feedback and confirmation patterns, and apply progressive disclosure.
  • Onboarding and Accessibility: Design activation-focused onboarding, semantic interfaces, keyboard navigation, accessible forms, and resilient error states.
  • Use Case: Apply this Skill to redesign a SaaS dashboard so users can find projects quickly, recover from failed loads, complete onboarding, and navigate the core workflow using only a keyboard.

Quick Start

Use the ux-design skill to review my product flow and propose a simpler navigation structure, onboarding path, and accessible error-handling experience.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I reduce friction in my SaaS user flows and navigation?

To reduce friction in SaaS user flows, restructure navigation and page hierarchies around user goals, apply progressive disclosure, and eliminate unnecessary steps. This simplifies task flows and helps users complete actions without confusion.

What is progressive disclosure and when should I use it in interaction design?

Progressive disclosure is an interaction design pattern that reveals information or features only as the user needs them. Use it to simplify complex interfaces, reduce cognitive load, and guide users through multi-step task flows without overwhelming them.

How do I design accessible forms with keyboard navigation and semantic HTML?

Design accessible forms by using semantic HTML elements, ensuring full keyboard navigation support, and implementing accessible form validation. Provide clear feedback states and resilient error handling so users can recover from input errors easily.

What's the best way to structure onboarding for a SaaS dashboard?

The best way to structure SaaS onboarding is to focus on activation. Design a progressive onboarding path that guides users to their first key action, reduces unnecessary steps, and uses clear feedback to confirm progress through the core workflow.

How do I handle error states and failed loads in a web application?

Handle error states by implementing resilient retry and degradation behavior, clear feedback states, and appropriate confirmation patterns. This ensures users understand what went wrong and can recover from failed loads without losing their place in the task flow.

Does my product flow need semantic HTML to improve its information architecture?

Yes, semantic HTML is required to improve information architecture and accessibility. It supports keyboard navigation, accessible form validation, and clear content structure, ensuring users can navigate and complete tasks using only a keyboard.