Design Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Scroll Container Ownership Contract
Long pages, libraries, and workbenches must define one primary scroll owner; declare scroll ownership before combining nested `height: 100vh`, `overflow: hidden/auto`, and sticky panels.
Scrolling is not incidental browser behavior; it is a layout contract. Decide who owns page scroll, who owns local scroll, which panels are sticky, and how mobile reflows before implementation.97%Interaction Responsive Motionscroll / horizontalHorizontal Scroll Portfolio Boundary
Horizontal scrolling works for bounded portfolios, galleries, and project sequences, but not for long prose, documentation, or core task flows.
Horizontal scroll must be an explicit content format: users can see the next item, operate it with keyboard and touch, reflow on narrow screens, and read core text without hunting on the horizontal axis.95%Interaction Responsive Motionmotion / scrollScroll 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%Frontend Implementationscroll / motionScroll-linked Motion Implementation Boundaries
Scroll motion must distinguish CSS scroll timelines, GSAP ScrollTrigger, Lenis smooth scroll, and native scrolling; immersion must not break reading, anchors, keyboard behavior, or mobile feel.
Scroll is user-controlled reading rhythm, not the animator's timeline. Implementation should preserve native scroll semantics first, then bind lightweight motion to sections where it adds value.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 Motionpagination / scrollInfinite Scroll vs Pagination
Infinite Scroll vs Pagination turns a frequent interface judgment into an executable constraint before generation.
Browse lists can scroll continuously; task lists usually need position, selection, return, and count awareness.84%