UI Library Router

Inspect the host before selecting anything: framework, package manager, installed dependency versions, React/Tailwind versions, current design system, components.json, theme tokens, chart/motion dependencies, accessibility constraints and asset rights. Classify each requested feature as base UI, product component, marketing enhancement, data visualization, creative effect, bespoke motion or interactive vector graphics.

Normalize this evidence into HostProfile and TaskProfile before formal selection. When the OrchestrUI MCP is available, call recommend_stack with those structured profiles and retain its role ownership, rejected candidates, rule IDs and evidence. Use task-text inference only when project evidence is genuinely unavailable; do not treat a legacy-text-inference result as equivalent to inspected structured routing.

Choose the smallest set with one owner per major role. Existing systems win unless migration is explicit. Review evidence-bearing candidate rankings for installed reuse, dependency/bundle cost, overlap and bounded version compatibility, but never use score to override a hard compatibility, conflict or asset-rights gate. Use Bklit for data visualization; daisyUI only as an intentional semantic Tailwind base; Kokonut for selective shadcn-compatible product polish; Magic UI for the primary marketing enhancement layer; React Bits for one or two signature creative effects; Anime.js only for bespoke timelines/SVG/scroll work; Rive only for meaningful state-machine graphics with recorded .riv rights.

Never select all seven by default. Do not add daisyUI beside a shadcn-derived base without an explicit isolation or migration strategy. Prefer CSS and component-native motion before Anime.js. Never silently use Pro material or vendor, mirror, bundle, sublicense or redistribute React Bits components from OrchestrUI.

Return: existing stack; selected libraries and role ownership; required components/effects; official retrieval method; rejected redundancies; compatibility/legal risks; and a validation plan. A valid recommendation may select no OrchestrUI library.

Read references/libraries.md when evaluating ecosystem-specific tradeoffs. Read references/selection-workflow.md when producing a formal routing plan.