feat(init): optional agent skills install at end of init by Railly · Pull Request #86 · clerk/cli

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly · 2026-03-31T22:14:00Z

Summary

At the end of clerk init, prompt the user to optionally install Clerk agent skills via npx skills add clerk/skills. This is opt-in by design — init finishes the SDK + scaffold flow first, then asks.

Runs after the scaffold/env-pull steps as the final stage
Auto-detects framework and resolves the matching skill set
Base skills always included: clerk, clerk-setup
Framework-specific patterns added on top
Opt-out: --no-skills skips the prompt entirely
-y auto-accepts the prompt for non-interactive flows
Graceful fallback if npx skills add fails

Framework → Skill mapping

Framework	Skill
Next.js	`clerk-nextjs-patterns`
React	`clerk-react-patterns`
React Router	`clerk-react-router-patterns`
Vue	`clerk-vue-patterns`
Nuxt	`clerk-nuxt-patterns`
Astro	`clerk-astro-patterns`
TanStack Start	`clerk-tanstack-patterns`
Expo	`clerk-expo-patterns`
Express/Fastify	`clerk-backend-api`

Tested locally on all 8 supported frameworks

Created a fresh scaffold for each framework in /tmp/clerk-dev-test/ and ran clerk-dev init. All flows: detection → SDK install → scaffold → skills opt-in prompt → install. Everything green.

Framework	Detection	Scaffold	Skills install
Next.js	✓	✓	✓
React (Vite)	✓	✓	✓
React Router	✓	✓	✓
Vue	✓	✓	✓
Nuxt	✓	✓	✓
Astro	✓	✓	✓
TanStack Start	✓	✓	✓
Expo	✓	n/a (scaffolding not yet supported, falls through cleanly)	✓

Closes AIE-728

Adds skills.ts with framework detection -> skill resolution mapping. Uses `npx skills add clerk/skills` under the hood to install the right Clerk skills for the detected framework (e.g. Next.js -> clerk-nextjs-patterns). Base skills (clerk, clerk-setup) are always included. Part of AIE-728

After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

…files-on-clerk-init Resolved conflicts in cli-program.ts and init/index.ts: - Adopted main's setExamples() format, added --no-skills example - Adopted main's new init flow (intro/outro/bar spinners, resolveAuth) - Skills install now runs at the end of init as an opt-in step, before outro("Done"), respects --no-skills flag Added @inquirer/core as direct dep to fix module resolution.

rafa-thayto

🚀 🚀 🚀

The skills install puts template files into skills/ that break tsc because framework templates reference auto-generated types (e.g. ./+types/root for React Router) that don't exist outside the real app/ directory. Skipping skills in test setup keeps the typecheck step focused on the actual scaffolded files.

* feat(init): install the clerk-expo setup skill for Expo projects The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(init): make framework skill arrays readonly Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as Record<string, readonly string[]> so immutability is declared at the source and getFrameworkSkills inherits it, instead of copying at runtime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Railly added 3 commits March 31, 2026 17:13

feat(init): hook skills installation into init flow
4973238
After scaffolding completes, clerk init now offers to install agent skills via npx skills add. Auto-detects framework and installs the matching skill set. Opt-out via --no-skills flag. Part of AIE-728

Railly changed the title ~~feat(init): auto-install agent skills on clerk init~~feat(init): optional agent skills install at end of initApr 7, 2026

Railly marked this pull request as ready for review April 7, 2026 00:05

Railly requested review from rafa-thayto and wyattjoh April 7, 2026 00:05

rafa-thayto approved these changes Apr 7, 2026
View reviewed changes

Railly merged commit 3961a31 into mainApr 7, 2026
5 checks passed

Railly deleted the railly/aie-728-auto-generate-agentsmd-skill-files-on-clerk-init branch April 7, 2026 01:03

Railly mentioned this pull request Apr 7, 2026
fix(init): delegate skills scope + agent picker to skills CLI #114
Merged

manovotny mentioned this pull request Jun 10, 2026
feat(init): install the clerk-expo setup skill for Expo projects #328
Merged