fact @community/fact-motion-as-feedback

Motion As Feedback

Animation in production UI must communicate one of: (a) cause-and-effect (clicking here triggered that), (b) origin / continuity (this panel came from that button), (c) state change (saved, loading, errored), or (d) spat…

Skill
@community
Domain
com.kernary.aoe/frontend-design
Version
1.0.0
Quality
0.0
Edges
0 out · 0 in
Tokens
150/343/659
$ aoe install @community/fact-motion-as-feedback

Projection

Always in _index.xml · the agent never has to ask for this.

MotionAsFeedback [fact] v1.0.0

Effective UI motion communicates state changes and causality (something happened, something moved here from there) rather than serving as decoration. Motion divorced from state is overhead — perceived cost without functional return.

Animation in production UI must communicate one of: (a) cause-and-effect (clicking here triggered that), (b) origin / continuity (this panel came from that button), (c) state change (saved, loading, errored), or (d) spatial relationship (this is below, this opens upward) — animation that does none of these is decorative overhead.

Source

aoe-engine/examples/frontend-design/primes/compiled/@community/fact-motion-as-feedback/atom.yaml