Actionable Error Messages
Error and success messages must be actionable and tied to the specific context in which they appear — telling the user what happened AND what to do next.…
$ aoe install @community/rule-actionable-error-messagesProjection
Always in _index.xml · the agent never has to ask for this.
ActionableErrorMessages [rule] v1.0.0
Error and success messages must be actionable and tied to the specific context in which they appear — telling the user what happened AND what to do next. Generic messages ('Something went wrong', 'Success') are prohibited.
Loaded when retrieval picks the atom as adjacent / supporting.
ActionableErrorMessages [rule] v1.0.0
Error and success messages must be actionable and tied to the specific context in which they appear — telling the user what happened AND what to do next. Generic messages ('Something went wrong', 'Success') are prohibited.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Applies When
Writing or reviewing any error, validation, or success feedback in a UI.
Verify By
Confirm each message names the specific event and offers at least one next step. Reject messages that only describe state without direction.
Anti Pattern
Generic context-free messages force users to guess what went wrong and how to recover, increasing abandonment rates. Examples of banned messages: 'An error occurred', 'Operation failed', 'Done'.
Use Instead
- 'Email already in use — try signing in or use a different email'
- 'Payment failed — check your card number and expiry, then try again'
- 'Report saved — view it in your Reports dashboard'
Loaded when retrieval picks the atom as a focal / direct hit.
ActionableErrorMessages [rule] v1.0.0
Error and success messages must be actionable and tied to the specific context in which they appear — telling the user what happened AND what to do next. Generic messages ('Something went wrong', 'Success') are prohibited.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Applies When
Writing or reviewing any error, validation, or success feedback in a UI.
Verify By
Confirm each message names the specific event and offers at least one next step. Reject messages that only describe state without direction.
Anti Pattern
Generic context-free messages force users to guess what went wrong and how to recover, increasing abandonment rates. Examples of banned messages: 'An error occurred', 'Operation failed', 'Done'.
Use Instead
- 'Email already in use — try signing in or use a different email'
- 'Payment failed — check your card number and expiry, then try again'
- 'Report saved — view it in your Reports dashboard'
Relations
related: [@community/principle-nielsen-error-recovery, @community/anti-pattern-generic-error-text, @community/example-stripe-checkout]
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Severity
warning
Applies When
Writing or reviewing any error, validation, or success feedback in a UI.
Verify By
Confirm each message names the specific event and offers at least one next step. Reject messages that only describe state without direction.
Anti Pattern
Generic context-free messages force users to guess what went wrong and how to recover, increasing abandonment rates. Examples of banned messages: 'An error occurred', 'Operation failed', 'Done'.
Use Instead
- 'Email already in use — try signing in or use a different email'
- 'Payment failed — check your card number and expiry, then try again'
- 'Report saved — view it in your Reports dashboard'
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/rule-actionable-error-messages/atom.yaml