Feedback & Recovery Patterns | LlamaPress Pattern Catalog

Decision guide · Demo Confirmation vs Undo Whether an action should ask "are you sure" or just happen with a way back. The answer is decided by reversibility and blast radius, not by how dangerous the verb sounds. Act & DecideFeedback & Recovery

Pattern · Demo Empty State What a screen shows when it has nothing to show — which is either someone's first impression of the feature, or proof that their work is done. OrientFeedback & Recovery

Pattern · Demo Loading Skeleton Grey placeholder shapes in the layout the real content will occupy, so a slow screen shows what is coming instead of a spinner or a blank. Feedback & RecoveryOrient

Pattern · Demo Notifications Telling someone that something needs them — with a strict rule about what earns an interruption, because the cost of a wrong one is that all of them get ignored. CoordinateFeedback & Recovery

Pattern · Demo Optimistic Update Show the result of an action immediately, send it in the background, and reconcile honestly if it fails — so a fast action feels instant instead of waiting on a network round trip. Edit & ManipulateAct & DecideFeedback & Recovery

Pattern · Demo Unsaved Changes Guard The screen knows whether it holds work that is not saved, says so continuously, and intercepts anything that would throw it away. Edit & ManipulateFeedback & Recovery

Pattern · Demo Validation Errors Tell someone a value is wrong next to that value, at the moment it can be fixed, in words that say what to do — and never take away what they typed. Create & CaptureEdit & ManipulateFeedback & Recovery

Pattern · Demo Version History Previous states of a record kept, listed and restorable — so an edit is never the destruction of what came before. Edit & ManipulateFeedback & Recovery

Exemplar What Gmail Figured Out That when an action is frequent and reversible, undo beats confirmation — and that changing an action's reversibility is better than adding friction to it. Act & DecideFeedback & Recovery