What problem does it solve?
Clerk authentication setup can be difficult because it varies across frameworks and requires correct middleware/proxy configuration plus secure environment variables.
Core Features & Use Cases
- Framework-aware setup: Detects the target framework from
package.json and pulls the correct Clerk quickstart instructions to configure the right packages and entry points.
- Next.js protection wiring: Guides creation of
proxy.ts (or middleware.ts for older Next versions) and ensures auth routes and matchers are configured correctly.
- Design system alignment: Detects shadcn/ui (
components.json) and applies the Clerk shadcn theme so auth UI matches the app.
- Migration planning: Helps transition from existing providers (e.g., NextAuth, Supabase Auth, Firebase, Auth0) by auditing auth touchpoints and proposing a migration strategy.
Quick Start
Set up Clerk authentication for my project in the folder by telling you to "Add Clerk authentication to my app at ./my-saas-app using the app router and Tailwind, and apply shadcn styling if components.json exists."