What problem does it solve? Choosing a frontend framework is often driven by habit rather than product requirements, leading to over-engineered stacks (like defaulting to Next.js) or architectures that break SEO or deployment constraints. This Skill replaces guesswork with a deterministic decision matrix and leaves an auditable record of why the stack was chosen. ## Core Features & Use Cases - Trigger-based decision matrix: Maps dominant signals (SEO needs, login-gated app, interactivity level, existing backend) to stacks including React+Next.js, Vite SPA, Astro, Svelte/SvelteKit, Vue/Nuxt, TanStack Start, and vanilla JS + Supabase + PWA. - ADR generation: Produces a short Architecture Decision Record with context, decision, rejected alternatives with reasons, and consequences. - Mandatory gates and guardrails: Refuses to decide before resolving the SEO vs. logged-in-app question, forbids assuming the backend contract, and requires a new ADR for any later stack change. - Use Case: A team with an existing Spring Boot REST API building an internal dashboard asks "Next or Vite?" — the Skill identifies the logged-in, no-SEO profile, recommends a Vite + React SPA, and writes the ADR justifying why SSR was rejected. ## Quick Start Ask the assistant to decide which frontend stack to use for a product, describing whether SEO matters, whether the app sits behind a login, and what backend already exists.
