ux

Review user-facing flows against LobeHub design values and interaction checklists.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ux-opensourceagi
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: ux
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/apps/qwk-in-lobe/.agents/skills/ux
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill ux-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve? Building or reviewing user-facing flows often misses recurring interaction failures — permanent skeletons on failed fetches, lost drafts, dead-end actions, and inconsistent list behavior. This Skill provides LobeHub's design values and per-module execution checklists so designers and engineers catch these gaps systematically. ## Core Features & Use Cases - Design values framework: Applies the four LobeHub values (Natural, Meaningful, Certainty, Growth) with conflict-priority guidance before any flow design. - Modular checklists: Five reference modules — Read, Edit, Act, Feedback, Grow — each with concrete rules, real codebase examples, and tagged checklist items. - Interaction principles: Rules for surface contracts, semantic consistency, layout roles, and composing canonical components like NavItem and Accordion instead of hand-rolled markup. - Use Case: When implementing a settings list with search and bulk actions, walk the Read and Act checklists to verify empty/error states, server-side filtering, one primary button, and full entity lifecycle coverage. ## Quick Start Use the ux skill to review this new settings page flow against the Read, Edit, and Act checklists before I ship it.

Frequently Asked Questions about ux

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

FAQPage Schema
How do I review a UI flow for UX issues before shipping?ā–¼

Walk the quick review checklist in SKILL.md, then open the matching module — Read for lists and data views, Edit for input surfaces, Act for operations and buttons, Feedback for loading states, Grow for discoverability. Each item links to full rules with real code examples.

What are the LobeHub design values?ā–¼

LobeHub follows four values adapted from Ant Design: Natural, Meaningful, Certainty, and Growth. When they conflict in moment-to-moment decisions, the priority is Meaningful then Natural then Certainty; Growth guides longer-horizon feature discovery.

When should I use this skill versus DESIGN.md?ā–¼

Use DESIGN.md for the static design system — theme tokens, components, and voice. Use this ux skill for dynamic behavior over time: empty, loading, and error states, draft safety, action flow, and progressive disclosure.

Why does a failed fetch show a permanent skeleton in React?ā–¼

The usual cause is gating the ready state on a success-only flag, such as checking data presence in a map populated only on success. Branch the fetch error before the loading gate, or release the gate on settled state covering data, null, and error.

What are the limitations of this UX checklist approach?ā–¼

The checklists target interaction behavior, not visual styling or component implementation, which belong to DESIGN.md and the react skill. Cross-surface gaps like stale sibling views have no single file location, so they must be checked explicitly.