Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Scroll Story Chapter Contract
The basic unit of scrollytelling is not an animation frame but a readable chapter: each chapter needs a question, text anchor, visual state, static fallback, and verifiable scroll behavior.
Scroll storytelling should break complex mechanisms into evidence chapters users can pause on, skip, and return to; motion connects chapters and states but should not become the only content layer.95%Interaction Responsive Motionmotion / reduced-motionMotion Accessibility and Performance Triage
Before shipping motion, classify purpose, trigger, disable path, performance properties, and verification evidence instead of accepting it because it looks smooth.
Good motion explains change; bad motion adds burden. Triage turns every animation into an explainable, reducible, testable, cleanup-safe interface behavior.95%Interaction Responsive Motionmotion / scrollAward Site Scroll Story Motion
Scroll motion should help users understand product state and narrative progress, not hide information inside uncontrolled spectacle.
Scroll motion in narrative pages must serve causality, hierarchy, and pacing: each motion segment should explain a state change or value proof.92%Interaction Responsive Motionportfolio / motionQuiet Motion in Portfolios
Portfolio motion should clarify selection, entry, comparison, and memory instead of making every element perform.
The interaction value of a portfolio is helping users judge craft: project selection, visual detail, case navigation, and contextual transitions matter more than decorative animation.90%Interaction Responsive Motionmotion / animationRestrained Motion With Purpose
Motion should explain state change, spatial relationship, or feedback instead of adding noise.
Excessive motion interrupts tasks, especially in dense tools.82%