Skill Wiki v0.1.0
rule @community/rule-page-transition-out-in-timing

Page Transition Out In Timing

Page transitions must use asymmetric timing: exit in 150-200ms (ease-in, accelerating out of view) and entrance in 250-400ms (ease-out, decelerating into position) — exits must complete before entrance begins in route-ba…

Skill
@community
Domain
frontend-design
Version
1.0.0
Quality
4.0
Edges
8 out · 1 in
Tokens
192/557/999
$ prime install @community/rule-page-transition-out-in-timing

Projection

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

PageTransitionOutInTiming [rule] v1.0.0

Exit is intentional — the user chose to leave. The animation should confirm the decision quickly (150ms) with an accelerating curve (ease-in) that reads as 'departing'. Entrance is discovery — the user is absorbing new content. It should decelerate into position (ease-out, 300ms) giving the eye time to orient. Symmetric timing (same duration for both) feels indecisive and makes the total transition 100ms longer than necessary.

Page transitions must use asymmetric timing: exit in 150-200ms (ease-in, accelerating out of view) and entrance in 250-400ms (ease-out, decelerating into position) — exits must complete before entrance begins in route-based systems, or overlap by ≤50ms via out-in mode.

Source

prime-system/examples/frontend-design/primes/compiled/@community/rule-page-transition-out-in-timing/atom.yaml

Compiled at 2026-05-07