What problem does it solve? Setting up Tailwind CSS v4 and complete SEO infrastructure in a Next.js 16 App Router project involves many scattered configuration steps — CSS-first theme tokens, per-page metadata, JSON-LD schemas, sitemaps, and canonical URLs — that are easy to get wrong or miss entirely. ## Core Features & Use Cases - Tailwind CSS 4.3 Setup: CSS-first configuration with @theme design tokens, @tailwindcss/postcss, and Google Fonts via next/font mapped to CSS variables. - SEO Metadata & Structured Data: generateMetadata() templates with canonical URLs, hreflang alternates, Open Graph/Twitter cards, and reusable JSON-LD components for LocalBusiness and WebSite schemas. - Sitemap & Robots: Built-in app/sitemap.ts and app/robots.ts with locale-aware URLs, plus legacy next-sitemap guidance for existing projects. - Use Case: You are building a localized marketing site on Next.js 16 and need Tailwind v4 tokens, per-locale metadata, JSON-LD for a local business, and a working sitemap.xml — this Skill walks through each step with copy-ready templates and a completion checklist. ## Quick Start Set up Tailwind CSS 4.3 with custom brand colors and add generateMetadata with canonical URLs and JSON-LD to my Next.js 16 App Router project.