Loading State Feedback
The UI must acknowledge every user-initiated action within 100ms — either by showing the completed result immediately (optimistic update) or by entering a visible loading state that persists until completion.
$ aoe install @community/rule-loading-state-feedbackProjection
Always in _index.xml · the agent never has to ask for this.
LoadingStateFeedback [rule] v1.0.0
The UI must acknowledge every user-initiated action within 100ms — either by showing the completed result immediately (optimistic update) or by entering a visible loading state that persists until completion.
Loaded when retrieval picks the atom as adjacent / supporting.
LoadingStateFeedback [rule] v1.0.0
The UI must acknowledge every user-initiated action within 100ms — either by showing the completed result immediately (optimistic update) or by entering a visible loading state that persists until completion.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Threshold
100ms — the Doherty Threshold below which response feels instantaneous; above 1000ms a spinner or progress indicator is required.
Severity
high
Patterns
- 0–100ms: optimistic update — show result immediately, revert on failure
- 100–1000ms: button enters loading state (inline spinner, aria-busy='true')
- 1000ms+: progress bar or skeleton replacing the affected content region
- On completion: brief success state (200ms) before returning to default
Loaded when retrieval picks the atom as a focal / direct hit.
LoadingStateFeedback [rule] v1.0.0
The UI must acknowledge every user-initiated action within 100ms — either by showing the completed result immediately (optimistic update) or by entering a visible loading state that persists until completion.
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Threshold
100ms — the Doherty Threshold below which response feels instantaneous; above 1000ms a spinner or progress indicator is required.
Severity
high
Patterns
- 0–100ms: optimistic update — show result immediately, revert on failure
- 100–1000ms: button enters loading state (inline spinner, aria-busy='true')
- 1000ms+: progress bar or skeleton replacing the affected content region
- On completion: brief success state (200ms) before returning to default
Relations
related: [@community/anti-pattern-no-loading-state, @community/rule-inline-loader-placement, @community/counter-example-button-no-loading, @community/example-stripe-payment-success, @community/example-vercel-analytics, @community/principle-nielsen-visibility]
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Threshold
100ms — the Doherty Threshold below which response feels instantaneous; above 1000ms a spinner or progress indicator is required.
Severity
high
Patterns
- 0–100ms: optimistic update — show result immediately, revert on failure
- 100–1000ms: button enters loading state (inline spinner, aria-busy='true')
- 1000ms+: progress bar or skeleton replacing the affected content region
- On completion: brief success state (200ms) before returning to default
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/rule-loading-state-feedback/atom.yaml