stack-recommender

Use when recommending a technology stack for a new project based on requirements. Maps project needs to specific technologies with trade-off analysis and rationale. Also use when a user wants to change or evaluate their current stack choices.

Model	Source
opus	pack: fresh-project

Full Reference

┏━ 🔧 stack-recommender ━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Use when recommending a technology stack for a… ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Stack Recommender

Decision framework that maps project requirements to specific technology picks across 7 layers — framework, styling, backend, database, ORM, auth, and deploy — with honest trade-off analysis for each choice. Reads PROJECT.md if present, then produces a populated stack.json with rationale and named trade-offs.

Quick Reference

Key	Value
Covers	Framework, styling, backend API, database, ORM, auth, deploy, DX tooling
Decision trigger	Project type + MAU target + budget + team size + deadline pressure
Output format	stack.json with all 7 layers populated + named trade-offs per pick
Default picks	Next.js · Tailwind v4 + shadcn/ui · Drizzle · Supabase · Clerk · Vercel · pnpm

Reference Index

I want to…	Reference File
Choose a frontend framework (Next.js vs Astro vs SvelteKit vs React+Vite)	reference/framework-selection.md
Choose a database (Supabase vs Neon vs MongoDB vs Turso + when to add Redis)	reference/database-selection.md
Choose an auth provider (Clerk vs Auth.js vs Supabase Auth)	reference/auth-selection.md
Choose a deployment platform (Vercel vs Cloudflare vs Railway vs Docker)	reference/deploy-selection.md
Choose an ORM (Drizzle vs Prisma) and API pattern (REST vs tRPC vs GraphQL)	reference/orm-and-backend-patterns.md
Get a complete stack.json template, avoid anti-patterns, or trigger on-demand skill generation	reference/stack-combinations.md

Usage: Read the reference file matching your current task from the index above. Each file is self-contained with code examples and inline gotchas.