Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
3 published principles / 192 in library
Frontend Implementationcopy-in / motion
Copy-in Motion Component Localization and Accessibility
After copying an external motion component, Lottie/Rive player, Motion/GSAP example, or registry block, localize copy, states, direction, duration, reduced motion, pause/stop/hide behavior, keyboard paths, and license source.
Once a motion component is copied into the repository, it is no longer a demo fragment. It becomes a local interaction asset that must satisfy brand voice, language direction, accessible fallbacks, performance budget, and source licensing.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%Frontend Implementationview-transition / navigationView Transition Route Continuity
The View Transition API can make route, filter, and detail changes feel continuous, but it must preserve URL, focus, scroll, reduced-motion, and progressive enhancement boundaries.
Page transitions are not spectacle; they help users understand continuity of the same object across lists, details, filters, and state changes.94%