Where these belong
Read firstFour of the five name the Hub as off-limits in their own headers, each for a specific stated cost rather than out of general caution. This table is those headers, and it is the first thing on the page on purpose.
NkCardHoverAnywhere, Hub includedThe one member of the family that is safe on a dense surface: 2px of travel, no listener, no state, no per-frame work, and nothing about it is pointer-position driven. It is a hover affordance, and a tile that answers the cursor is how a grid tells you its cells are reachable. It is also the only one on
@nkapp/lib/isomorphic— no hook, no react-aria, so it can BE a React Server Component rather than merely be rendered by one.NkMagneticButtonMarketing surfaces onlyA landing hero, a pricing call-to-action — a page with one or two primary actions where the cursor’s arrival is worth acknowledging. Not the Hub’s dense views. A toolbar of eight magnetic buttons is eight window listeners leaning in different directions, and a control that moves as you approach it is a worse target to hit — which matters when hitting it is the whole job. Rule of thumb: one per viewport.
NkTiltCardMarketing surfaces onlyA feature card, a testimonial, a screenshot. Not the Hub’s dense views, and never around a table. A grid of tilting cards is a grid of elements that are no longer axis-aligned with each other, which makes a scan comparison harder rather than easier; and a tilted plate mis-aims every hit target on it by a few pixels — a real cost for a row of controls and no cost at all for a paragraph.
NkSpotlightMarketing surfaces onlyLarge feature panels — a pricing table, a hero card, a documentation tile. Not the Hub’s dense views. The glow is a repaint of the gradient layer on every frame the cursor moves: on a 400px card that is cheap and confined, and on a full-page container behind a long table it is a full-viewport repaint per frame. Scope it to a panel, never to a scroll region or a data grid.
NkCursorTrailOne per site, or not at allNever in the Hub, never on a data grid, never on any surface whose job is to be read or operated. It is the showiest thing in the library and the least discriminating: mounted once, it then decorates the cursor everywhere — including over a table the user is trying to scan and a form they are trying to fill. It conveys nothing, it cannot be made to convey anything, and its entire value is atmosphere.
The effect is decoration and never state: it encodes nothing, it is never the only way to perceive anything, and removing it leaves a fully operable surface. That is the test for whether an effect like this may exist at all — and it is also why the reduced-motion answer is to remove it entirely rather than to make it faster.