When should I use an undo action instead of a confirmation dialog?

Use undo for reversible actions to maintain user flow. Only use confirmation dialogs for truly irreversible and destructive actions to avoid 'confirmation fatigue'.

What are the three essential components of a good error message?

Every error message should answer: What happened?, Why did it happen?, and What can the user do now to recover?

How does the Peak-End Rule affect user experience?

Users judge experiences by the most intense moment and the end. A graceful recovery from an error can actually leave a more positive lasting impression than a bug-free but mediocre experience.

What is an Optimistic UI pattern?

It is a pattern where the UI updates immediately as if an action succeeded, while the server request processes in the background, with a rollback mechanism if the request fails.

Trust & Recovery UX Guide

Name: Trust & Recovery UX Guide
Author: bfmcneill

bybfmcneill

0•

Design Tools

Implements research-backed UI patterns for error handling, undo functionality, and graceful recovery to build and maintain user confidence.

The Trust and Recovery skill provides a specialized framework for designing resilient user experiences based on behavioral psychology and established UX heuristics. It helps developers apply principles like the Peak-End Rule and Loss Aversion to software interactions, offering specific guidance on when to use undo actions versus confirmation dialogs. By following these patterns, you can ensure your application handles failures gracefully, preserves user data aggressively, and maintains transparency through clear system status indicators, ultimately turning potential points of frustration into trust-building moments.

Key Features

01Actionable templates for recognition-focused error messages

02Optimistic UI patterns with built-in rollback mechanisms

03Strategies for graceful degradation and isolating system failures

04Evidence-based guidance on undo vs. confirmation dialog logic

05Patterns for data preservation and aggressive auto-saving

060 GitHub stars

Use Cases

01Refactoring generic system error messages into helpful recovery paths

02Implementing a non-disruptive undo pattern for content management tools

03Designing a high-stakes data entry system where preventing loss is critical

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add bfmcneill/agi-marketplace trust-and-recovery

For use in Claude.ai and ChatGPT

Download Skill