Skiper UI

Skiper UI is an "un-common components" library for shadcn/ui and Next.js projects, with shadcn CLI 3.0 usage, Tailwind, Motion, Figma, and Next.js as its visible stack. Source: Skiper UI homepage, https://skiper-ui.com/, accessed 2026-06-25

Routing Summary

Use Skiper through Component Library Sources and animated-component-libraries when a Next.js / shadcn UI needs an uncommon but editable component source. Do not use it as a generic style default; first load Frontend and Design Skills, Frontend and Design Skills, or design-engineering-polish, then decide whether a Skiper component accelerates the chosen direction.

Use When

Use Skiper when a project needs a more distinctive shadcn-based component than the generic registry default: unusual hero treatments, interactive sections, portfolio templates, motion-forward blocks, or a component starting point an agent can copy into the local codebase and retokenize. Source: Skiper UI homepage, accessed 2026-06-25

Skiper is a reference and component source, not a substitute for design direction. Agents should still load Frontend and Design Skills, Frontend and Design Skills, or design-engineering-polish first, then pull Skiper only when a copied component accelerates a concrete screen. Source: User request, 2026-06-25

Integration Rules

• Use project-local shadcn conventions and cn() utilities.
• Retokenize colors, radii, shadows, spacing, and motion to the local design system.
• Inspect dependencies before adding copied code.
• Do not stack several novelty effects in one viewport. One strong component is enough.

---

Timeline

• 2026-06-25 | Page created and routed into Component Library Sources and animated-component-libraries after Kevin asked to add Skiper UI to design skills. Source: User request, 2026-06-25; https://skiper-ui.com/