entering: / exiting: variantsIn use
Registered in motion.css. Before that, seven components wrote these classes and Tailwind emitted nothing for them, so no overlay animated at all.
Duration + easing tokensPartial
Consumed by NkPopover (and therefore NkSelect, NkComboBox, NkMultiSelect, NkDropdownMenu), NkBottomSheet, NkSplitPane, NkOtpInput, NkToggleGroup, NkUsageBar and — since this row last said otherwise — the whole dialog family: NkDialog.tsx:56,58,91,94 is token-driven and NkModal / NkAlertDialog import the same two strings from it. NkDrawer.tsx:87,88,115,116 is the one holdout, with literal duration-200 / duration-300.
Travel tokensIn use
--nk-lift: NkOtpInput, NkCardHover. --nk-rise: NkDialog.tsx:90,93 (as --tw-enter-translate-y), enter-variant.ts — so NkEnter and NkScrollReveal — plus NkTextStagger, NkCardHover and @keyframes nk-cadence, which is where the typing indicator’s dots get their bob. --nk-shift: enter-variant.ts and NkMagneticButton, whose lean is capped at it.
Scale floorsIn use
--nk-scale-in: NkDialog.tsx:89 (zoom-in-[var(--nk-scale-in)], not the old literal zoom-in-95), NkSteps.tsx:299, and enter-variant.ts’s scale variant. --nk-scale-out: NkDialog.tsx:92. There is exactly one scale floor and NkEnter declines amicro’s second one (zoom) rather than adding a second answer to a question the library already answered.
Loop periodsIn use
All three are consumed on the day they were declared, which is the point of declaring them: --nk-period-pulse by NkTypingIndicator, the caret in NkTextTyping and NkTerminalLoader, and NkLoadingSpinner’s dots/pulse variants; --nk-period-sweep by NkTextShimmer, NkSkeleton, NkRadarSweep and the spinner’s rail; --nk-period-wave by NkWaveform and the spinner’s bars. The rail’s own comment used to say its 1.5s had no token.
Amplitude tokensIn use
--nk-stagger-step: NkTextStagger, NkTextTyping (as its per-character cadence), NkTypingIndicator, NkWaveform, NkSkeleton’s lines, NkLoadingSpinner and useStagger. --nk-blur-in: NkTextBlur via @keyframes nk-blur-in. --nk-wave-floor: @keyframes nk-wave. Each one exists so the reduced-motion block has something to collapse — that is what makes a loop able to keep its cadence while losing its movement.
The keyframe layerIn use
Nine named keyframes in motion.css, reached through Tailwind’s stock animate-[…] group rather than through a new @utility — so the manifest is unchanged at 20 channels, 15 utilities, 2 variants. Before this, NkLoadingSpinner rendered a <style> element containing @keyframes as a CHILD OF ITSELF, so a view with four spinners injected the same keyframe four times, on every render, into the document the browser was animating. apps/hub/src/components/ui/LoadingView.tsx still does the same thing through dangerouslySetInnerHTML.
Reduced-motion policyPartial
The motion.css media block is global, so it reaches everything written as a class or a token. Two documented gaps remain, both by construction rather than by oversight: an INLINE transition is out of its reach (which is why the pointer family is gated in JavaScript instead), and one component opts out by hand — see the motion-reduce:animate-none tripwire.