What problem does it solve? Designing and reviewing Portal UI flows without a shared, verifiable standard leads to inconsistent screens and degraded UX commitments. This Skill provides the six committed UX patterns (progressive disclosure, predictive insight cards, tool-call visibility, real streaming with stop, role-based workspaces, shared dashboard-chat state) with textual acceptance criteria so every screen, component, and UX deliverable (A2-A5) can be checked against a traceable QA gate. ## Core Features & Use Cases - Pattern Reference with Acceptance Criteria: Each of the six patterns includes a verifiable criterion (e.g., 3 depth levels with <=2 clicks, TTFT p50 < 700 ms, method label on every prediction card) backed by a cited research paper. - Traceability Table and QA Checklist: A pattern-to-paper-to-QA-gate table plus a checklist for reviewing any UI change, ensuring no pattern is degraded without a documented team decision. - UX Deliverable Guidance (A2-A5): Rules for journey maps, competitive analysis, high-fidelity prototypes (including empty, loading, error, and no-permission states), and SUS usability tasks derived from the verifiable criteria. - Use Case: When reviewing a new dashboard card, check it against the Predictive Insight Cards pattern to confirm it carries an honest method label such as "Liquidity risk +12% next month - linear projection on synthetic data" before it passes QA. ## Quick Start Review my new dashboard component against the six committed Portal UX patterns and tell me which acceptance criteria it fails.
