Add Analytics

**Judgement** A strong, production-viable GA4 integration skill for modern JavaScript web apps and static sites. It covers a wide range of frameworks, handles most boilerplate correctly, and offers useful extras like event helpers and consent-mode wiring. Best suited for front-end projects that match the listed frameworks and teams that want a fast, standardized GA4 setup. **Key strengths** - Good framework coverage with tailored code paths for Next.js (App/Pages router), Nuxt, Astro, SvelteKit, React/Vite, Vue/Vite, CRA, Angular, Gatsby, and plain HTML. - Opinionated, comprehensive implementation: script injection, env var setup, event helpers, consent utilities, debug hints, and TypeScript declarations. - Awareness of GA4 vs deprecated Universal Analytics, with validation and user guidance. - Provides a verification checklist and summary of changes, which improves correctness and maintainability. **Main risks / limitations** - **Framework detection heuristics:** Monorepos or atypical structures may confuse detection (e.g., multiple frameworks/configs present), leading to incorrect integration paths. - **Duplicate or conflicting analytics:** Existing GA/gtag snippets are only loosely checked for; the skill may introduce duplicate GA tags if a project already has partial analytics wiring. - **Evolving framework APIs:** Hard-coded integration patterns for frameworks like Next.js, Nuxt, or SvelteKit may drift out of date as those frameworks change, risking warnings or runtime issues in newer versions. - **Privacy and compliance:** While a consent-mode wrapper is available (`--consent`), it does not provide a full consent UI or jurisdiction-specific logic. Teams remain responsible for ensuring GDPR/CCPA compliance, cookie banner behavior, and data-processing agreements. - **JavaScript-centric scope:** Back-end frameworks, native apps, or non-JS front-ends are out of scope; integration there must still be done manually. **Recommended scenarios** - You maintain one or more modern JS front-end projects and want a consistent GA4 setup across them with minimal manual work. - You are upgrading from no analytics (or from UA) to GA4 on supported frameworks and want guidance plus generated boilerplate. - You need structured GA4 event helpers for common engagement, conversion, and error events without designing your own tracking library. - You want a starting point for consent-mode integration and plan to layer your own consent-banner UI and legal review on top. **Less ideal for** - Projects with custom or legacy build setups not matching the detection rules (e.g., heavily customized monorepos, non-standard directory layouts). - Teams with strict privacy/compliance requirements that need bespoke consent flows, data minimization strategies, or advanced tag management beyond GA4’s basic scripts. - Apps that already have a carefully tuned analytics/tag-management setup (e.g., via Google Tag Manager) where this skill might conflict with or duplicate existing configuration.