tech-stack-recommendationslisted

Opinionated technology stack guidance for new projects and migrations. **You MUST use this skill whenever the user is starting a new project, picking a runtime (Bun/Deno/Node), choosing a frontend framework, database, auth provider, hosting platform, styling system, mobile stack, i18n library, or AI-agent framework that the project doesn't yet have, setting up a monorepo, or migrating between stacks.** Do not assume a stack decision is too obvious to need this skill — consult it before recommending any specific technology. Does NOT trigger on: debugging existing code, maintaining or extending the current stack's existing components, library-version or package-manager migrations within the same stack, configuring tools already installed, or 'how do I do X in [framework I already use]' questions.
sorawit-w/agent-skills · ★ 1 · Web & Frontend · score 75

Install: claude install-skill sorawit-w/agent-skills

# Tech Stack Recommendations Complete guide for choosing opinionated technology stacks for new projects and migrations. **Read this first to pick your runtime, then load the appropriate reference guides below.** --- ## When to Use This Skill - **New projects:** Starting from scratch and need stack guidance - **Stack migrations:** Moving from Node → Bun, rewriting in Deno, etc. - **Framework selection:** Choosing between SvelteKit, Next.js, Angular, Nuxt, etc. - **Architecture decisions:** Building monorepos, multi-platform apps, or complex systems - **Infrastructure choices:** Selecting databases, auth, hosting, styling, mobile frameworks **NOT for:** Existing projects with established stacks (unless actively migrating). --- ## This Skill Has a Shelf Life Framework ecosystems drift fast. The specific names in this skill (Bun, SvelteKit, Elysia, Neon, Drizzle, Clerk, etc.) reflect 2026-era tooling and *will* age. Before recommending any named tool: - If the user's request is recent and the skill hasn't been updated in a while, flag the age — e.g., "this was written against 2026 tooling; double-check pricing/status for [vendor] before committing." - For syntax or API details, defer to the project's current docs, not a snippet pasted from here. - If a named framework is clearly deprecated or superseded, say so instead of recommending it. The *shape* of the advice (pick one runtime, name the override factors, prefer what the team can debug) ages more slowly than the spe