// the find
crafter-station/elements
Full-stack shadcn/ui blocks for auth, payments, AI, logos, and more
Elements is a shadcn registry of pre-built full-stack UI blocks targeting the Next.js/Vercel ecosystem — auth via Clerk, payments via Polar, AI chat components wired to Vercel AI SDK, 154 tech logos, and Claude Code automation hooks. It installs through the standard `npx shadcn` CLI, so blocks drop into your project as owned, editable source. Aimed at developers building AI-heavy SaaS apps who want a head start on the boilerplate UI.
- Registry-native distribution is genuinely smart — `npx shadcn@latest add @elements/clerk-sign-in` copies source into your project, so you own the code and aren't locked into a versioned package you can't modify.
- The AI elements category is the most useful part: streaming text, chain-of-thought display, tool call inspector, token counter — these are the components every AI app needs and nobody wants to write from scratch.
- The Claude Code hooks collection (guard-secrets, guard-destructive, notify-slack, session-summary) is a practical addition that has nothing to do with UI but fills a real gap; most teams are assembling these ad-hoc from shell scripts.
- 154 theme-adaptive tech logos solves a tedious problem — consistent brand assets that respect dark/light mode, available in one install command.
- Heavy vendor coupling is the core risk: Clerk, Polar, UploadThing, Upstash, Vercel AI SDK — if you're not already committed to that exact stack, most of the library is dead weight. There's no BetterAuth or Supabase auth equivalent.
- 504 stars and 30 forks for a project covering this much surface area is a signal that maintenance breadth might outpace contributors; the docs folder has files named FINAL_STATUS.md and FINAL_REGISTRY_SUMMARY.md, which is not confidence-inspiring for an active project.
- No server component story apparent — everything looks like client-side React components, which creates friction if your app is built around React Server Components and you want to avoid unnecessary client bundles.
- The Claude Code hooks are shell scripts in a UI component repo, which is an odd home for them; if you're using Elements for the hooks, you're pulling in a lot of Next.js and Tailwind setup you don't need.