Skip to content

Create professional demos and 3D mockups in seconds, directly in your browser

Remove SEO audit evaluations and references; update skills-lock.json to reflect changes.

CristianOlivera18811711a7c2f
diff --git a/.agents/skills/nextjs-developer/SKILL.md b/.agents/skills/nextjs-developer/SKILL.md
new file mode 100644
index 0000000..eafe4b4
--- /dev/null
+++ b/.agents/skills/nextjs-developer/SKILL.md
@@ -0,0 +1,145 @@
+---
+name: nextjs-developer
+description: "Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance."
+license: MIT
+metadata:
+ author: https://github.com/Jeffallan
+ version: "1.1.0"
+ domain: frontend
+ triggers: Next.js, Next.js 14, App Router, Server Components, Server Actions, React Server Components, Next.js deployment, Vercel, Next.js performance
+ role: specialist
+ scope: implementation
+ output-format: code
+ related-skills: typescript-pro
+---
+
+# Next.js Developer
+
+Senior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.
+
+## Core Workflow
+
+1. **Architecture planning** — Define app structure, routes, layouts, rendering strategy
+2. **Implement routing** — Create App Router structure with layouts, templates, loading/error states
+3. **Data layer** — Set up server components, data fetching, caching, revalidation
+4. **Optimize** — Images, fonts, bundles, streaming, edge runtime
+5. **Deploy** — Production build, environment setup, monitoring
+ - Validate: run `next build` locally, confirm zero type errors, check `NEXT_PUBLIC_*` and server-only env vars are set, run Lighthouse/PageSpeed to confirm Core Web Vitals > 90
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| App Router | `references/app-router.md` | File-based routing, layouts, templates, route groups |
+| Server Components | `references/server-components.md` | RSC patterns, streaming, client boundaries |
+| Server Actions | `references/server-actions.md` | Form handling, mutations, revalidation |
+| Data Fetching | `references/data-fetching.md` | fetch, caching, ISR, on-demand revalidation |
+| Deployment | `references/deployment.md` | Vercel, self-hosting, Docker, optimization |
+
+## Constraints
+
+### MUST DO (Next.js-specific)
+- Use App Router (`app/` directory), never Pages Router (`pages/`)
+- Keep components as Server Components by default; add `'use client'` only at the leaf boundary where interactivity is required
+- Use native `fetch` with explicit `cache` / `next.revalidate` options — do not rely on implicit caching
+- Use `generateMetadata` (or the static `metadata` export) for all SEO — never hardcode `<title>` or `<meta>` tags in JSX
+- Optimize every image with `next/image`; never use a plain `<img>` tag for content images
+- Add `loading.tsx` and `error.tsx` at every route segment that performs async data fetching
+
+### MUST NOT DO
+- Convert components to Client Components just to access data — fetch server-side first
+- Skip `loading.tsx`/`error.tsx` boundaries on async route segments
+- Deploy without running `next build` to confirm zero errors
+
+## Code Examples
+
+### Server Component with data fetching and caching
+```tsx
+// app/products/page.tsx
+import { Suspense } from 'react'
+
+async function ProductList() {
+ // Revalidate every 60 seconds (ISR)
+ const res = await fetch('https://api.example.com/products', {
+ next: { revalidate: 60 },
+ })
+ if (!res.ok) throw new Error('Failed to fetch products')
+ const products: Product[] = await res.json()
+
+ return (
+ <ul>
+ {products.map((p) => (
+ <li key={p.id}>{p.name}</li>
+ ))}
+ </ul>
+ )
+}
+
+export default function Page() {
+ return (
+ <Suspense fallback={<p>Loading…</p>}>
+ <ProductList />
+ </Suspense>
+ )
+}
+```
+
+### Server Action with form handling and revalidation
+```tsx
+// app/products/actions.ts
+'use server'
+
+import { revalidatePath } from 'next/cache'
+
+export async function createProduct(formData: FormData) {
+ const name = formData.get('name') as string
+ await db.product.create({ data: { name } })
+ revalidatePath('/products')
+}
+
+// app/products/new/page.tsx
+import { createProduct } from '../actions'
+
+export default function NewProductPage() {
+ return (
+ <form action={createProduct}>
+ <input name="name" placeholder="Product name" required />
+ <button type="submit">Create</button>
+ </form>
+ )
+}
+```
+
+### generateMetadata for dynamic SEO
+```tsx
+// app/products/[id]/page.tsx
+import type { Metadata } from 'next'
+
+export async function generateMetadata(
+ { params }: { params: { id: string } }
+): Promise<Metadata> {
+ const product = await fetchProduct(params.id)
+ return {
+ title: product.name,
+ description: product.description,
+ openGraph: { title: product.name, images: [product.imageUrl] },
+ }
+}
+```
+
+## Output Templates
+
+When implementing Next.js features, provide:
+1. App structure (route organization)
+2. Layout/page components with proper data fetching
+3. Server actions if mutations needed
+4. Configuration (`next.config.js`, TypeScript)
+5. Brief explanation of rendering strategy chosen
+
+## Knowledge Reference
+
+Next.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next/image, next/font, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment
+
+[Documentation](https://jeffallan.github.io/claude-skills/skills/frontend/nextjs-developer/)
diff --git a/.agents/skills/nextjs-developer/references/app-router.md b/.agents/skills/nextjs-developer/references/app-router.md
new file mode 100644
index 0000000..e0a4f69
--- /dev/null
+++ b/.agents/skills/nextjs-developer/references/app-router.md
@@ -0,0 +1,311 @@
+# App Router Architecture
+
+## File-Based Routing
+
+```
+app/
+├── layout.tsx # Root layout (required)
+├── page.tsx # Home page (/)
+├── loading.tsx # Loading UI
+├── error.tsx # Error boundary
+├── not-found.tsx # 404 page
+├── template.tsx # Re-mounted layout
+│
+├── (marketing)/ # Route group (no URL segment)
+│ ├── layout.tsx
+│ ├── about/
+│ │ └── page.tsx # /about
+│ └── contact/
+│ └── page.tsx # /contact
+│
+├── dashboard/
+│ ├── layout.tsx # Shared dashboard layout
+│ ├── page.tsx # /dashboard
+│ ├── settings/
+│ │ └── page.tsx # /dashboard/settings
+│ └── @analytics/ # Parallel route (slot)
+│ └── page.tsx
+│
+├── blog/
+│ ├── [slug]/
+│ │ └── page.tsx # /blog/my-post (dynamic)
+│ └── [...slug]/
+│ └── page.tsx # /blog/a/b/c (catch-all)
+│
+└── api/
+ └── users/
+ └── route.ts # API route handler
+```
+
+## Root Layout (Required)
+
+```tsx
+// app/layout.tsx
+import type { Metadata } from 'next'
+import { Inter } from 'next/font/google'
+import './globals.css'
+
+const inter = Inter({ subsets: ['latin'] })
+
+export const metadata: Metadata = {
+ title: {
+ default: 'My App',
+ template: '%s | My App'
+ },
+ description: 'Next.js 14 application',
+}
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html lang="en">
+ <body className={inter.className}>
+ {children}
+ </body>
+ </html>
+ )
+}
+```
+
+## Nested Layouts
+
+```tsx
+// app/dashboard/layout.tsx
+import { Sidebar } from '@/components/sidebar'
+import { auth } from '@/lib/auth'
+import { redirect } from 'next/navigation'
+
+export default async function DashboardLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ const session = await auth()
+
+ if (!session) {
+ redirect('/login')
+ }
+
+ return (
+ <div className="flex">
+ <Sidebar />
+ <main className="flex-1">{children}</main>
+ </div>
+ )
+}
+```
+
+## Templates (Re-mount on Navigation)
+
+```tsx
+// app/template.tsx
+'use client'
+
+import { useEffect } from 'react'
+
+export default function Template({ children }: { children: React.ReactNode }) {
+ useEffect(() => {
+ // Runs on every navigation
+ console.log('Template mounted')
+ }, [])
+
+ return <div>{children}</div>
+}
+```
+
+## Loading States
+
+```tsx
+// app/dashboard/loading.tsx
+export default function Loading() {
+ return (
+ <div className="flex items-center justify-center h-screen">
+ <div className="animate-spin rounded-full h-32 w-32 border-b-2" />
+ </div>
+ )
+}
+```
+
+## Error Boundaries
+
+```tsx
+// app/error.tsx
+'use client'
+
+export default function Error({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string }
+ reset: () => void
+}) {
+ return (
+ <div>
+ <h2>Something went wrong!</h2>
+ <button onClick={() => reset()}>Try again</button>
+ </div>
+ )
+}
+```
+
+## Route Groups
+
+```tsx
+// (marketing) and (shop) share the same URL level
+app/
+├── (marketing)/
+│ ├── layout.tsx # Marketing layout
+│ └── about/
+│ └── page.tsx # /about
+└── (shop)/
+ ├── layout.tsx # Shop layout
+ └── products/
+ └── page.tsx # /products
+```
+
+## Parallel Routes
+
+```tsx
+// app/dashboard/layout.tsx
+export default function Layout({
+ children,
+ analytics,
+ team,
+}: {
+ children: React.ReactNode
+ analytics: React.ReactNode
+ team: React.ReactNode
+}) {
+ return (
+ <>
+ {children}
+ {analytics}
+ {team}
+ </>
+ )
+}
+
+// app/dashboard/@analytics/page.tsx
+export default function Analytics() {
+ return <div>Analytics Dashboard</div>
+}
+```
+
+## Intercepting Routes
+
+```tsx
+// Show modal when navigating from same app
+// but show full page on direct navigation
+
+// app/photos/[id]/page.tsx (full page)
+export default function PhotoPage({ params }: { params: { id: string } }) {
+ return <div>Photo {params.id} - Full Page</div>
+}
+
+// app/@modal/(.)photos/[id]/page.tsx (modal)
+export default function PhotoModal({ params }: { params: { id: string } }) {
+ return <div>Photo {params.id} - Modal</div>
+}
+```
+
+## Dynamic Routes
+
+```tsx
+// app/blog/[slug]/page.tsx
+export default function BlogPost({ params }: { params: { slug: string } }) {
+ return <h1>Post: {params.slug}</h1>
+}
+
+// Generate static params at build time
+export async function generateStaticParams() {
+ const posts = await fetch('https://api.example.com/posts').then(res => res.json())
+
+ return posts.map((post: { slug: string }) => ({
+ slug: post.slug,
+ }))
+}
+
+// Opt out of static generation
+export const dynamic = 'force-dynamic'
+
+// Revalidate every 60 seconds
+export const revalidate = 60
+```
+
+## Catch-All Routes
+
+```tsx
+// app/docs/[...slug]/page.tsx
+// Matches: /docs/a, /docs/a/b, /docs/a/b/c
+export default function Docs({ params }: { params: { slug: string[] } }) {
+ return <div>Docs: {params.slug.join('/')}</div>
+}
+
+// Optional catch-all: [[...slug]]
+// Also matches: /docs
+```
+
+## Route Handlers (API Routes)
+
+```tsx
+// app/api/users/route.ts
+import { NextRequest, NextResponse } from 'next/server'
+
+export async function GET(request: NextRequest) {
+ const users = await db.user.findMany()
+ return NextResponse.json(users)
+}
+
+export async function POST(request: NextRequest) {
+ const body = await request.json()
+ const user = await db.user.create({ data: body })
+ return NextResponse.json(user, { status: 201 })
+}
+
+// Dynamic routes: app/api/users/[id]/route.ts
+export async function GET(
+ request: NextRequest,
+ { params }: { params: { id: string } }
+) {
+ const user = await db.user.findUnique({ where: { id: params.id } })
+ return NextResponse.json(user)
+}
+```
+
+## Metadata API
+
+```tsx
+// app/blog/[slug]/page.tsx
+import type { Metadata } from 'next'
+
+export async function generateMetadata(
+ { params }: { params: { slug: string } }
+): Promise<Metadata> {
+ const post = await fetchPost(params.slug)
+
+ return {
+ title: post.title,
+ description: post.excerpt,
+ openGraph: {
+ title: post.title,
+ description: post.excerpt,
+ images: [{ url: post.coverImage }],
+ },
+ }
+}
+```
+
+## Quick Reference
+
+| File | Purpose | Use Case |
+|------|---------|----------|
+| `layout.tsx` | Persistent UI across routes | Shared navigation, auth wrapper |
+| `page.tsx` | Route UI | Actual page content |
+| `loading.tsx` | Loading fallback | Automatic Suspense boundary |
+| `error.tsx` | Error boundary | Handle errors gracefully |
+| `template.tsx` | Re-mounted layout | Analytics, animations |
+| `not-found.tsx` | 404 page | Custom not found UI |
+| `route.ts` | API handler | Backend API endpoints |
diff --git a/.agents/skills/nextjs-developer/references/data-fetching.md b/.agents/skills/nextjs-developer/references/data-fetching.md
new file mode 100644
index 0000000..df9ac2f
--- /dev/null
+++ b/.agents/skills/nextjs-developer/references/data-fetching.md
@@ -0,0 +1,482 @@
+# Data Fetching & Caching
+
+## Extended fetch API
+
+Next.js extends the native fetch with caching and revalidation options:
+
+```tsx
+// app/page.tsx
+async function getData() {
+ const res = await fetch('https://api.example.com/posts', {
+ cache: 'force-cache', // Default: cache forever (SSG)
+ })
+
+ if (!res.ok) {
+ throw new Error('Failed to fetch data')
+ }
+
+ return res.json()
+}
+
+export default async function Page() {
+ const data = await getData()
+ return <div>{/* render data */}</div>
+}
+```
+
+## Cache Options
+
+```tsx
+// 1. Force cache (Static Site Generation)
+fetch('https://api.example.com/data', {
+ cache: 'force-cache' // Default behavior
+})
+
+// 2. No cache (Server-Side Rendering)
+fetch('https://api.example.com/data', {
+ cache: 'no-store' // Always fetch fresh data
+})
+
+// 3. Revalidate (Incremental Static Regeneration)
+fetch('https://api.example.com/data', {
+ next: { revalidate: 3600 } // Revalidate every hour
+})
+
+// 4. Revalidate with tags
+fetch('https://api.example.com/data', {
+ next: { tags: ['posts'] }
+})
+```
+
+## Revalidation Methods
+
+### Time-based Revalidation (ISR)
+
+```tsx
+// Revalidate every 60 seconds
+async function getPosts() {
+ const res = await fetch('https://api.example.com/posts', {
+ next: { revalidate: 60 }
+ })
+ return res.json()
+}
+
+// Route segment config
+export const revalidate = 60 // seconds
+
+export default async function Page() {
+ const posts = await getPosts()
+ return <div>{/* render */}</div>
+}
+```
+
+### On-Demand Revalidation
+
+```tsx
+// app/api/revalidate/route.ts
+import { revalidatePath, revalidateTag } from 'next/cache'
+import { NextRequest } from 'next/server'
+
+export async function POST(request: NextRequest) {
+ const path = request.nextUrl.searchParams.get('path')
+
+ if (path) {
+ revalidatePath(path)
+ return Response.json({ revalidated: true, now: Date.now() })
+ }
+
+ return Response.json({ revalidated: false })
+}
+
+// Usage in Server Action
+'use server'
+
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(data: FormData) {
+ await db.post.create({ data })
+
+ // Revalidate specific path
+ revalidatePath('/posts')
+
+ // Revalidate entire layout
+ revalidatePath('/posts', 'layout')
+}
+```
+
+### Tag-based Revalidation
+
+```tsx
+// Fetch with tags
+async function getPosts() {
+ const res = await fetch('https://api.example.com/posts', {
+ next: { tags: ['posts'] }
+ })
+ return res.json()
+}
+
+async function getAuthors() {
+ const res = await fetch('https://api.example.com/authors', {
+ next: { tags: ['authors'] }
+ })
+ return res.json()
+}
+
+// Revalidate by tag
+import { revalidateTag } from 'next/cache'
+
+export async function createPost() {
+ // Revalidate all fetches tagged with 'posts'
+ revalidateTag('posts')
+}
+```
+
+## Route Segment Config
+
+```tsx
+// app/posts/page.tsx
+
+// Force dynamic rendering
+export const dynamic = 'force-dynamic' // 'auto' | 'force-dynamic' | 'error' | 'force-static'
+
+// Revalidation interval
+export const revalidate = 3600 // false | 0 | number (seconds)
+
+// Fetch cache
+export const fetchCache = 'auto' // 'auto' | 'default-cache' | 'only-cache' | 'force-cache' | 'force-no-store' | 'default-no-store' | 'only-no-store'
+
+// Runtime
+export const runtime = 'nodejs' // 'nodejs' | 'edge'
+
+// Preferred region
+export const preferredRegion = 'auto' // 'auto' | 'home' | 'edge' | string | string[]
+
+export default async function Page() {
+ return <div>Posts</div>
+}
+```
+
+## Parallel Data Fetching
+
+```tsx
+async function getUser() {
+ return fetch('https://api.example.com/user')
+}
+
+async function getPosts() {
+ return fetch('https://api.example.com/posts')
+}
+
+async function getComments() {
+ return fetch('https://api.example.com/comments')
+}
+
+export default async function Page() {
+ // Fetch in parallel with Promise.all
+ const [user, posts, comments] = await Promise.all([
+ getUser(),
+ getPosts(),
+ getComments(),
+ ])
+
+ return (
+ <div>
+ <UserInfo user={user} />
+ <Posts posts={posts} />
+ <Comments comments={comments} />
+ </div>
+ )
+}
+```
+
+## Sequential Data Fetching
+
+```tsx
+// When one fetch depends on another
+export default async function Page({ params }: { params: { id: string } }) {
+ // First fetch
+ const user = await fetch(`https://api.example.com/users/${params.id}`)
+ .then(res => res.json())
+
+ // Second fetch depends on first
+ const posts = await fetch(`https://api.example.com/users/${user.id}/posts`)
+ .then(res => res.json())
+
+ return (
+ <div>
+ <h1>{user.name}</h1>
+ <Posts posts={posts} />
+ </div>
+ )
+}
+```
+
+## Streaming with Suspense
+
+```tsx
+// app/page.tsx
+import { Suspense } from 'react'
+
+async function Posts() {
+ const posts = await fetch('https://api.example.com/posts', {
+ cache: 'no-store'
+ }).then(res => res.json())
+
+ return (
+ <ul>
+ {posts.map((post: Post) => (
+ <li key={post.id}>{post.title}</li>
+ ))}
+ </ul>
+ )
+}
+
+export default function Page() {
+ return (
+ <div>
+ <h1>Posts</h1>
+ <Suspense fallback={<div>Loading posts...</div>}>
+ <Posts />
+ </Suspense>
+ </div>
+ )
+}
+```
+
+## React cache for Deduplication
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const getUser = cache(async (id: string) => {
+ const res = await fetch(`https://api.example.com/users/${id}`)
+ return res.json()
+})
+
+// components/user-profile.tsx
+export async function UserProfile({ userId }: { userId: string }) {
+ const user = await getUser(userId) // Cached
+ return <div>{user.name}</div>
+}
+
+// components/user-posts.tsx
+export async function UserPosts({ userId }: { userId: string }) {
+ const user = await getUser(userId) // Uses cached result
+ return <div>{user.posts.length} posts</div>
+}
+
+// app/page.tsx
+export default function Page() {
+ return (
+ <>
+ <UserProfile userId="123" />
+ <UserPosts userId="123" /> {/* Same fetch, deduplicated */}
+ </>
+ )
+}
+```
+
+## Database Queries
+
+```tsx
+// lib/db.ts
+import { PrismaClient } from '@prisma/client'
+
+const globalForPrisma = global as unknown as { prisma: PrismaClient }
+
+export const db = globalForPrisma.prisma || new PrismaClient()
+
+if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = db
+
+// app/posts/page.tsx
+import { db } from '@/lib/db'
+
+export const revalidate = 60 // Revalidate every 60 seconds
+
+export default async function PostsPage() {
+ const posts = await db.post.findMany({
+ include: { author: true },
+ orderBy: { createdAt: 'desc' },
+ })
+
+ return (
+ <div>
+ {posts.map(post => (
+ <article key={post.id}>
+ <h2>{post.title}</h2>
+ <p>By {post.author.name}</p>
+ </article>
+ ))}
+ </div>
+ )
+}
+```
+
+## Error Handling
+
+```tsx
+async function getData() {
+ const res = await fetch('https://api.example.com/data')
+
+ if (!res.ok) {
+ // This will activate the closest error.tsx
+ throw new Error('Failed to fetch data')
+ }
+
+ return res.json()
+}
+
+export default async function Page() {
+ const data = await getData()
+ return <div>{data.title}</div>
+}
+
+// app/error.tsx
+'use client'
+
+export default function Error({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string }
+ reset: () => void
+}) {
+ return (
+ <div>
+ <h2>Something went wrong!</h2>
+ <button onClick={() => reset()}>Try again</button>
+ </div>
+ )
+}
+```
+
+## Loading States
+
+```tsx
+// app/posts/loading.tsx
+export default function Loading() {
+ return <div>Loading posts...</div>
+}
+
+// app/posts/page.tsx
+export default async function PostsPage() {
+ const posts = await fetch('https://api.example.com/posts')
+ .then(res => res.json())
+
+ return <div>{/* render posts */}</div>
+}
+```
+
+## Client-Side Data Fetching
+
+```tsx
+// When you need client-side fetching
+'use client'
+
+import useSWR from 'swr'
+
+const fetcher = (url: string) => fetch(url).then(res => res.json())
+
+export function Posts() {
+ const { data, error, isLoading } = useSWR('/api/posts', fetcher, {
+ refreshInterval: 3000, // Refresh every 3 seconds
+ })
+
+ if (error) return <div>Failed to load</div>
+ if (isLoading) return <div>Loading...</div>
+
+ return (
+ <ul>
+ {data.map((post: Post) => (
+ <li key={post.id}>{post.title}</li>
+ ))}
+ </ul>
+ )
+}
+```
+
+## Preloading Data
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const preload = (id: string) => {
+ void getUser(id) // Trigger fetch without awaiting
+}
+
+export const getUser = cache(async (id: string) => {
+ return fetch(`https://api.example.com/users/${id}`)
+ .then(res => res.json())
+})
+
+// components/user.tsx
+import { getUser, preload } from '@/lib/data'
+
+export async function User({ id }: { id: string }) {
+ const user = await getUser(id)
+ return <div>{user.name}</div>
+}
+
+// app/page.tsx
+import { User } from '@/components/user'
+import { preload } from '@/lib/data'
+
+export default async function Page() {
+ preload('123') // Start loading immediately
+ return <User id="123" />
+}
+```
+
+## Static Generation with Dynamic Routes
+
+```tsx
+// app/posts/[slug]/page.tsx
+type Post = {
+ slug: string
+ title: string
+ content: string
+}
+
+export async function generateStaticParams() {
+ const posts = await fetch('https://api.example.com/posts')
+ .then(res => res.json())
+
+ return posts.map((post: Post) => ({
+ slug: post.slug,
+ }))
+}
+
+export default async function Post({ params }: { params: { slug: string } }) {
+ const post = await fetch(`https://api.example.com/posts/${params.slug}`)
+ .then(res => res.json())
+
+ return (
+ <article>
+ <h1>{post.title}</h1>
+ <div>{post.content}</div>
+ </article>
+ )
+}
+```
+
+## Quick Reference
+
+| Strategy | Config | Use Case |
+|----------|--------|----------|
+| **SSG** | `cache: 'force-cache'` | Static content |
+| **SSR** | `cache: 'no-store'` | Always fresh data |
+| **ISR** | `next: { revalidate: 60 }` | Periodic updates |
+| **Tag-based** | `next: { tags: ['posts'] }` | On-demand revalidation |
+| **Dynamic** | `export const dynamic = 'force-dynamic'` | Per-request data |
+
+## Best Practices
+
+1. **Default to caching** - Use force-cache for static content
+2. **Use ISR** - Revalidate periodically for semi-dynamic content
+3. **Parallel fetching** - Use Promise.all for independent requests
+4. **Deduplicate** - Use React cache() for repeated calls
+5. **Stream with Suspense** - Show content progressively
+6. **Tag your fetches** - Enable granular revalidation
+7. **Handle errors** - Use error.tsx for graceful degradation
diff --git a/.agents/skills/nextjs-developer/references/deployment.md b/.agents/skills/nextjs-developer/references/deployment.md
new file mode 100644
index 0000000..9bad909
--- /dev/null
+++ b/.agents/skills/nextjs-developer/references/deployment.md
@@ -0,0 +1,545 @@
+# Deployment & Production
+
+## Vercel Deployment (Recommended)
+
+### Quick Deploy
+
+```bash
+# Install Vercel CLI
+npm i -g vercel
+
+# Deploy
+vercel
+
+# Production deployment
+vercel --prod
+```
+
+### vercel.json Configuration
+
+```json
+{
+ "buildCommand": "next build",
+ "devCommand": "next dev",
+ "installCommand": "npm install",
+ "framework": "nextjs",
+ "regions": ["iad1"],
+ "env": {
+ "DATABASE_URL": "@database-url",
+ "NEXT_PUBLIC_API_URL": "https://api.example.com"
+ },
+ "headers": [
+ {
+ "source": "/api/(.*)",
+ "headers": [
+ { "key": "Access-Control-Allow-Origin", "value": "*" },
+ { "key": "Access-Control-Allow-Methods", "value": "GET,POST,PUT,DELETE" }
+ ]
+ }
+ ],
+ "redirects": [
+ {
+ "source": "/old-blog/:slug",
+ "destination": "/blog/:slug",
+ "permanent": true
+ }
+ ],
+ "rewrites": [
+ {
+ "source": "/api/:path*",
+ "destination": "https://api.example.com/:path*"
+ }
+ ]
+}
+```
+
+### Environment Variables
+
+```bash
+# .env.local (not committed)
+DATABASE_URL="postgresql://user:pass@localhost:5432/db"
+NEXTAUTH_SECRET="your-secret"
+
+# .env.production (committed, public vars only)
+NEXT_PUBLIC_API_URL="https://api.example.com"
+```
+
+```tsx
+// Access in Server Components
+const dbUrl = process.env.DATABASE_URL
+
+// Access in Client Components (must be prefixed with NEXT_PUBLIC_)
+const apiUrl = process.env.NEXT_PUBLIC_API_URL
+```
+
+## Self-Hosting
+
+### Standalone Output
+
+```js
+// next.config.js
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+ output: 'standalone',
+}
+
+module.exports = nextConfig
+```
+
+```bash
+# Build
+npm run build
+
+# The standalone folder contains everything needed
+# Copy these to your server:
+# - .next/standalone/
+# - .next/static/
+# - public/
+
+# Run on server
+node .next/standalone/server.js
+```
+
+### Node.js Server
+
+```bash
+# Build
+npm run build
+
+# Start production server
+npm start
+
+# With PM2 for process management
+pm2 start npm --name "nextjs" -- start
+pm2 startup
+pm2 save
+```
+
+## Docker Deployment
+
+### Dockerfile (Multi-stage)
+
+```dockerfile
+# Stage 1: Dependencies
+FROM node:20-alpine AS deps
+RUN apk add --no-cache libc6-compat
+WORKDIR /app
+
+COPY package.json package-lock.json ./
+RUN npm ci
+
+# Stage 2: Builder
+FROM node:20-alpine AS builder
+WORKDIR /app
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+
+ENV NEXT_TELEMETRY_DISABLED 1
+
+RUN npm run build
+
+# Stage 3: Runner
+FROM node:20-alpine AS runner
+WORKDIR /app
+
+ENV NODE_ENV production
+ENV NEXT_TELEMETRY_DISABLED 1
+
+RUN addgroup --system --gid 1001 nodejs
+RUN adduser --system --uid 1001 nextjs
+
+COPY --from=builder /app/public ./public
+COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
+COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
+
+USER nextjs
+
+EXPOSE 3000
+
+ENV PORT 3000
+ENV HOSTNAME "0.0.0.0"
+
+CMD ["node", "server.js"]
+```
+
+### docker-compose.yml
+
+```yaml
+version: '3.8'
+
+services:
+ nextjs:
+ build:
+ context: .
+ dockerfile: Dockerfile
+ ports:
+ - "3000:3000"
+ environment:
+ - DATABASE_URL=postgresql://postgres:postgres@db:5432/myapp
+ - NEXTAUTH_URL=http://localhost:3000
+ - NEXTAUTH_SECRET=your-secret
+ depends_on:
+ - db
+ restart: unless-stopped
+
+ db:
+ image: postgres:16-alpine
+ environment:
+ - POSTGRES_USER=postgres
+ - POSTGRES_PASSWORD=postgres
+ - POSTGRES_DB=myapp
+ volumes:
+ - postgres_data:/var/lib/postgresql/data
+ restart: unless-stopped
+
+volumes:
+ postgres_data:
+```
+
+```bash
+# Build and run
+docker-compose up -d
+
+# View logs
+docker-compose logs -f nextjs
+
+# Rebuild
+docker-compose up -d --build
+```
+
+## Production Optimization
+
+### next.config.js
+
+```js
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+ // Standalone for self-hosting
+ output: 'standalone',
+
+ // Image optimization
+ images: {
+ formats: ['image/avif', 'image/webp'],
+ remotePatterns: [
+ {
+ protocol: 'https',
+ hostname: 'cdn.example.com',
+ pathname: '/images/**',
+ },
+ ],
+ deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
+ imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
+ },
+
+ // Compression
+ compress: true,
+
+ // Security headers
+ async headers() {
+ return [
+ {
+ source: '/:path*',
+ headers: [
+ {
+ key: 'X-DNS-Prefetch-Control',
+ value: 'on'
+ },
+ {
+ key: 'Strict-Transport-Security',
+ value: 'max-age=63072000; includeSubDomains; preload'
+ },
+ {
+ key: 'X-Frame-Options',
+ value: 'SAMEORIGIN'
+ },
+ {
+ key: 'X-Content-Type-Options',
+ value: 'nosniff'
+ },
+ {
+ key: 'X-XSS-Protection',
+ value: '1; mode=block'
+ },
+ {
+ key: 'Referrer-Policy',
+ value: 'origin-when-cross-origin'
+ },
+ ],
+ },
+ ]
+ },
+
+ // Experimental features
+ experimental: {
+ optimizePackageImports: ['@mui/material', 'lodash'],
+ },
+
+ // Bundle analyzer
+ webpack: (config, { isServer }) => {
+ if (process.env.ANALYZE === 'true') {
+ const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
+ config.plugins.push(
+ new BundleAnalyzerPlugin({
+ analyzerMode: 'static',
+ reportFilename: isServer
+ ? '../analyze/server.html'
+ : './analyze/client.html',
+ })
+ )
+ }
+ return config
+ },
+}
+
+module.exports = nextConfig
+```
+
+### Bundle Analysis
+
+```bash
+# Install analyzer
+npm install -D @next/bundle-analyzer
+
+# Analyze
+ANALYZE=true npm run build
+
+# Or use built-in
+npm run build -- --experimental-build-mode=compile
+```
+
+### Performance Monitoring
+
+```tsx
+// app/layout.tsx
+import { SpeedInsights } from '@vercel/speed-insights/next'
+import { Analytics } from '@vercel/analytics/react'
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html>
+ <body>
+ {children}
+ <SpeedInsights />
+ <Analytics />
+ </body>
+ </html>
+ )
+}
+```
+
+## CDN & Edge
+
+### Static Asset CDN
+
+```js
+// next.config.js
+const nextConfig = {
+ assetPrefix: process.env.NODE_ENV === 'production'
+ ? 'https://cdn.example.com'
+ : '',
+}
+```
+
+### Edge Runtime
+
+```tsx
+// app/api/edge/route.ts
+export const runtime = 'edge'
+
+export async function GET(request: Request) {
+ return new Response('Hello from Edge!', {
+ status: 200,
+ headers: {
+ 'content-type': 'text/plain',
+ },
+ })
+}
+
+// app/page.tsx
+export const runtime = 'edge'
+
+export default async function Page() {
+ return <div>Edge-rendered page</div>
+}
+```
+
+## Caching Strategy
+
+### ISR (Incremental Static Regeneration)
+
+```tsx
+// app/blog/[slug]/page.tsx
+export const revalidate = 3600 // Revalidate every hour
+
+export default async function BlogPost({ params }: { params: { slug: string } }) {
+ const post = await fetchPost(params.slug)
+ return <article>{post.content}</article>
+}
+```
+
+### On-Demand Revalidation
+
+```tsx
+// app/api/revalidate/route.ts
+import { revalidatePath } from 'next/cache'
+import { NextRequest } from 'next/server'
+
+export async function POST(request: NextRequest) {
+ const secret = request.nextUrl.searchParams.get('secret')
+
+ if (secret !== process.env.REVALIDATE_SECRET) {
+ return Response.json({ message: 'Invalid secret' }, { status: 401 })
+ }
+
+ const path = request.nextUrl.searchParams.get('path') || '/'
+
+ revalidatePath(path)
+
+ return Response.json({ revalidated: true, now: Date.now() })
+}
+```
+
+## Database Connection Pooling
+
+```ts
+// lib/db.ts
+import { PrismaClient } from '@prisma/client'
+
+const globalForPrisma = global as unknown as {
+ prisma: PrismaClient | undefined
+}
+
+export const db =
+ globalForPrisma.prisma ??
+ new PrismaClient({
+ log: process.env.NODE_ENV === 'development' ? ['query', 'error', 'warn'] : ['error'],
+ })
+
+if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = db
+```
+
+## Health Check Endpoint
+
+```tsx
+// app/api/health/route.ts
+import { db } from '@/lib/db'
+
+export async function GET() {
+ try {
+ // Check database connection
+ await db.$queryRaw`SELECT 1`
+
+ return Response.json({
+ status: 'ok',
+ timestamp: new Date().toISOString(),
+ uptime: process.uptime(),
+ })
+ } catch (error) {
+ return Response.json(
+ {
+ status: 'error',
+ message: 'Database connection failed',
+ },
+ { status: 503 }
+ )
+ }
+}
+```
+
+## CI/CD with GitHub Actions
+
+```yaml
+# .github/workflows/deploy.yml
+name: Deploy to Production
+
+on:
+ push:
+ branches: [main]
+
+jobs:
+ deploy:
+ runs-on: ubuntu-latest
+
+ steps:
+ - uses: actions/checkout@v3
+
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
+ with:
+ node-version: '20'
+ cache: 'npm'
+
+ - name: Install dependencies
+ run: npm ci
+
+ - name: Run tests
+ run: npm test
+
+ - name: Build
+ run: npm run build
+ env:
+ DATABASE_URL: ${{ secrets.DATABASE_URL }}
+ NEXTAUTH_SECRET: ${{ secrets.NEXTAUTH_SECRET }}
+
+ - name: Deploy to Vercel
+ uses: amondnet/vercel-action@v25
+ with:
+ vercel-token: ${{ secrets.VERCEL_TOKEN }}
+ vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
+ vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
+ vercel-args: '--prod'
+```
+
+## Monitoring & Logging
+
+```tsx
+// app/error.tsx
+'use client'
+
+import * as Sentry from '@sentry/nextjs'
+import { useEffect } from 'react'
+
+export default function Error({
+ error,
+}: {
+ error: Error & { digest?: string }
+}) {
+ useEffect(() => {
+ Sentry.captureException(error)
+ }, [error])
+
+ return <div>Something went wrong!</div>
+}
+```
+
+## Quick Reference
+
+| Platform | Best For | Effort |
+|----------|----------|--------|
+| **Vercel** | Zero-config, optimal performance | Low |
+| **Netlify** | Alternative to Vercel | Low |
+| **Railway** | Simple hosting with databases | Medium |
+| **AWS/GCP** | Enterprise, custom needs | High |
+| **Docker** | Self-hosting, full control | High |
+
+## Production Checklist
+
+- [ ] Enable TypeScript strict mode
+- [ ] Configure CSP headers
+- [ ] Setup error monitoring (Sentry)
+- [ ] Configure analytics (Vercel/GA)
+- [ ] Optimize images (next/image)
+- [ ] Enable compression
+- [ ] Setup CDN for static assets
+- [ ] Configure database connection pooling
+- [ ] Add health check endpoint
+- [ ] Setup CI/CD pipeline
+- [ ] Configure environment variables
+- [ ] Enable ISR/SSG where possible
+- [ ] Test Core Web Vitals
+- [ ] Setup logging (Datadog/LogRocket)
+- [ ] Configure backup strategy
diff --git a/.agents/skills/nextjs-developer/references/server-actions.md b/.agents/skills/nextjs-developer/references/server-actions.md
new file mode 100644
index 0000000..6d1f08a
--- /dev/null
+++ b/.agents/skills/nextjs-developer/references/server-actions.md
@@ -0,0 +1,462 @@
+# Server Actions
+
+## Basic Server Action
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { db } from '@/lib/db'
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(formData: FormData) {
+ const title = formData.get('title') as string
+ const content = formData.get('content') as string
+
+ await db.post.create({
+ data: { title, content }
+ })
+
+ revalidatePath('/posts')
+}
+```
+
+## Form with Server Action
+
+```tsx
+// app/posts/new/page.tsx
+import { createPost } from '@/app/actions'
+
+export default function NewPost() {
+ return (
+ <form action={createPost}>
+ <input name="title" required />
+ <textarea name="content" required />
+ <button type="submit">Create Post</button>
+ </form>
+ )
+}
+```
+
+## Server Action with Validation
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { z } from 'zod'
+import { revalidatePath } from 'next/cache'
+
+const CreatePostSchema = z.object({
+ title: z.string().min(3).max(100),
+ content: z.string().min(10),
+})
+
+export async function createPost(formData: FormData) {
+ const validatedFields = CreatePostSchema.safeParse({
+ title: formData.get('title'),
+ content: formData.get('content'),
+ })
+
+ if (!validatedFields.success) {
+ return {
+ errors: validatedFields.error.flatten().fieldErrors,
+ }
+ }
+
+ const { title, content } = validatedFields.data
+
+ await db.post.create({
+ data: { title, content }
+ })
+
+ revalidatePath('/posts')
+ return { success: true }
+}
+```
+
+## Client Component with Server Action
+
+```tsx
+// components/create-post-form.tsx
+'use client'
+
+import { createPost } from '@/app/actions'
+import { useFormState, useFormStatus } from 'react-dom'
+
+const initialState = {
+ errors: {},
+}
+
+function SubmitButton() {
+ const { pending } = useFormStatus()
+
+ return (
+ <button type="submit" disabled={pending}>
+ {pending ? 'Creating...' : 'Create Post'}
+ </button>
+ )
+}
+
+export function CreatePostForm() {
+ const [state, formAction] = useFormState(createPost, initialState)
+
+ return (
+ <form action={formAction}>
+ <div>
+ <input name="title" />
+ {state.errors?.title && <p>{state.errors.title[0]}</p>}
+ </div>
+
+ <div>
+ <textarea name="content" />
+ {state.errors?.content && <p>{state.errors.content[0]}</p>}
+ </div>
+
+ <SubmitButton />
+ </form>
+ )
+}
+```
+
+## Server Action with Redirect
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { redirect } from 'next/navigation'
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(formData: FormData) {
+ const post = await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ }
+ })
+
+ revalidatePath('/posts')
+ redirect(`/posts/${post.id}`)
+}
+```
+
+## Optimistic Updates
+
+```tsx
+// components/todo-list.tsx
+'use client'
+
+import { experimental_useOptimistic as useOptimistic } from 'react'
+import { toggleTodo } from '@/app/actions'
+
+export function TodoList({ todos }: { todos: Todo[] }) {
+ const [optimisticTodos, addOptimisticTodo] = useOptimistic(
+ todos,
+ (state, newTodo: Todo) => [...state, newTodo]
+ )
+
+ async function handleSubmit(formData: FormData) {
+ const title = formData.get('title') as string
+ const newTodo = { id: crypto.randomUUID(), title, completed: false }
+
+ // Optimistically update UI
+ addOptimisticTodo(newTodo)
+
+ // Send to server
+ await createTodo(formData)
+ }
+
+ return (
+ <div>
+ <ul>
+ {optimisticTodos.map(todo => (
+ <li key={todo.id}>{todo.title}</li>
+ ))}
+ </ul>
+
+ <form action={handleSubmit}>
+ <input name="title" />
+ <button type="submit">Add</button>
+ </form>
+ </div>
+ )
+}
+```
+
+## Server Action with Authentication
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { auth } from '@/lib/auth'
+import { redirect } from 'next/navigation'
+
+export async function createPost(formData: FormData) {
+ const session = await auth()
+
+ if (!session) {
+ redirect('/login')
+ }
+
+ await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ authorId: session.user.id,
+ }
+ })
+
+ revalidatePath('/posts')
+}
+```
+
+## Inline Server Action
+
+```tsx
+// app/posts/page.tsx
+import { db } from '@/lib/db'
+import { revalidatePath } from 'next/cache'
+
+export default async function Posts() {
+ const posts = await db.post.findMany()
+
+ async function deletePost(formData: FormData) {
+ 'use server'
+
+ const id = formData.get('id') as string
+ await db.post.delete({ where: { id } })
+ revalidatePath('/posts')
+ }
+
+ return (
+ <ul>
+ {posts.map(post => (
+ <li key={post.id}>
+ {post.title}
+ <form action={deletePost}>
+ <input type="hidden" name="id" value={post.id} />
+ <button type="submit">Delete</button>
+ </form>
+ </li>
+ ))}
+ </ul>
+ )
+}
+```
+
+## Programmatic Server Action Call
+
+```tsx
+// components/delete-button.tsx
+'use client'
+
+import { deletePost } from '@/app/actions'
+
+export function DeleteButton({ postId }: { postId: string }) {
+ async function handleDelete() {
+ if (confirm('Are you sure?')) {
+ await deletePost(postId)
+ }
+ }
+
+ return (
+ <button onClick={handleDelete}>
+ Delete
+ </button>
+ )
+}
+
+// app/actions.ts
+'use server'
+
+export async function deletePost(postId: string) {
+ await db.post.delete({ where: { id: postId } })
+ revalidatePath('/posts')
+}
+```
+
+## Revalidation Strategies
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { revalidatePath, revalidateTag } from 'next/cache'
+
+export async function updatePost(id: string, data: UpdatePostData) {
+ await db.post.update({ where: { id }, data })
+
+ // Revalidate specific path
+ revalidatePath('/posts')
+ revalidatePath(`/posts/${id}`)
+
+ // Revalidate all paths in a layout
+ revalidatePath('/posts', 'layout')
+
+ // Revalidate by cache tag
+ revalidateTag('posts')
+}
+```
+
+## Server Action with File Upload
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { writeFile } from 'fs/promises'
+import { join } from 'path'
+
+export async function uploadAvatar(formData: FormData) {
+ const file = formData.get('avatar') as File
+
+ if (!file) {
+ return { error: 'No file uploaded' }
+ }
+
+ const bytes = await file.arrayBuffer()
+ const buffer = Buffer.from(bytes)
+
+ const path = join(process.cwd(), 'public', 'uploads', file.name)
+ await writeFile(path, buffer)
+
+ return { success: true, path: `/uploads/${file.name}` }
+}
+
+// components/upload-form.tsx
+'use client'
+
+import { uploadAvatar } from '@/app/actions'
+
+export function UploadForm() {
+ async function handleSubmit(formData: FormData) {
+ const result = await uploadAvatar(formData)
+ if (result.success) {
+ console.log('Uploaded to:', result.path)
+ }
+ }
+
+ return (
+ <form action={handleSubmit}>
+ <input type="file" name="avatar" accept="image/*" />
+ <button type="submit">Upload</button>
+ </form>
+ )
+}
+```
+
+## Error Handling
+
+```tsx
+// app/actions.ts
+'use server'
+
+export async function createPost(formData: FormData) {
+ try {
+ await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ }
+ })
+
+ revalidatePath('/posts')
+ return { success: true }
+ } catch (error) {
+ console.error('Failed to create post:', error)
+ return { error: 'Failed to create post' }
+ }
+}
+
+// components/form.tsx
+'use client'
+
+export function CreatePostForm() {
+ const [error, setError] = useState<string | null>(null)
+
+ async function handleSubmit(formData: FormData) {
+ const result = await createPost(formData)
+
+ if (result.error) {
+ setError(result.error)
+ } else {
+ // Success
+ router.push('/posts')
+ }
+ }
+
+ return (
+ <form action={handleSubmit}>
+ {error && <div className="error">{error}</div>}
+ {/* form fields */}
+ </form>
+ )
+}
+```
+
+## Server Action with Cookies
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { cookies } from 'next/headers'
+
+export async function setTheme(theme: 'light' | 'dark') {
+ cookies().set('theme', theme, {
+ httpOnly: true,
+ secure: process.env.NODE_ENV === 'production',
+ maxAge: 60 * 60 * 24 * 365, // 1 year
+ path: '/',
+ })
+}
+
+export async function getTheme() {
+ return cookies().get('theme')?.value ?? 'light'
+}
+```
+
+## Rate Limiting
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { ratelimit } from '@/lib/redis'
+
+export async function createPost(formData: FormData) {
+ const session = await auth()
+ const { success } = await ratelimit.limit(session.user.id)
+
+ if (!success) {
+ return { error: 'Rate limit exceeded' }
+ }
+
+ // Create post...
+}
+```
+
+## Quick Reference
+
+| Capability | Usage |
+|------------|-------|
+| **Define** | Add 'use server' at top of file or function |
+| **Form** | Pass action to `<form action={serverAction}>` |
+| **Programmatic** | Call directly: `await serverAction(data)` |
+| **Validation** | Use Zod/TypeBox before mutations |
+| **Revalidate** | `revalidatePath()` or `revalidateTag()` |
+| **Redirect** | `redirect()` after mutation |
+| **Errors** | Return error objects, handle in client |
+| **Files** | Access via `formData.get()` as File |
+
+## Best Practices
+
+1. **Always validate** - Use Zod/TypeBox for type-safe validation
+2. **Revalidate** - Call revalidatePath() after mutations
+3. **Handle errors** - Return error objects instead of throwing
+4. **Auth checks** - Verify session before mutations
+5. **Rate limiting** - Protect against abuse
+6. **Type safety** - Define input/output types
+7. **Optimistic updates** - Use useOptimistic for better UX
diff --git a/.agents/skills/nextjs-developer/references/server-components.md b/.agents/skills/nextjs-developer/references/server-components.md
new file mode 100644
index 0000000..7d681a1
--- /dev/null
+++ b/.agents/skills/nextjs-developer/references/server-components.md
@@ -0,0 +1,384 @@
+# React Server Components
+
+## Server Components (Default)
+
+```tsx
+// app/page.tsx - Server Component by default
+import { db } from '@/lib/db'
+
+export default async function Page() {
+ // Data fetching in Server Component
+ const users = await db.user.findMany()
+
+ return (
+ <div>
+ <h1>Users</h1>
+ <ul>
+ {users.map(user => (
+ <li key={user.id}>{user.name}</li>
+ ))}
+ </ul>
+ </div>
+ )
+}
+```
+
+## Benefits of Server Components
+
+- **Zero bundle size** - Server Components don't add JavaScript to client bundle
+- **Direct backend access** - Query databases, read files, use secrets
+- **Automatic code splitting** - Only Client Components add to bundle
+- **Streaming** - Send UI progressively as data loads
+- **No client-side waterfalls** - Fetch all data in parallel on server
+
+## Client Components
+
+```tsx
+// components/counter.tsx
+'use client' // Required directive
+
+import { useState } from 'react'
+
+export function Counter() {
+ const [count, setCount] = useState(0)
+
+ return (
+ <button onClick={() => setCount(count + 1)}>
+ Count: {count}
+ </button>
+ )
+}
+```
+
+## When to Use Client Components
+
+Use `'use client'` when you need:
+- **Interactivity** - onClick, onChange, event handlers
+- **State** - useState, useReducer
+- **Effects** - useEffect, useLayoutEffect
+- **Browser APIs** - localStorage, window, document
+- **Custom hooks** - Any hook using client-only features
+- **Class components** - Component lifecycle methods
+
+## Composition Pattern
+
+```tsx
+// app/page.tsx - Server Component
+import { ClientWrapper } from './client-wrapper'
+import { db } from '@/lib/db'
+
+export default async function Page() {
+ const data = await db.query()
+
+ return (
+ <div>
+ {/* Server Component content */}
+ <h1>Server Content</h1>
+
+ {/* Pass data to Client Component */}
+ <ClientWrapper initialData={data}>
+ {/* Server Component as children */}
+ <ServerSidebar />
+ </ClientWrapper>
+ </div>
+ )
+}
+
+// components/client-wrapper.tsx
+'use client'
+
+export function ClientWrapper({
+ children,
+ initialData,
+}: {
+ children: React.ReactNode
+ initialData: Data
+}) {
+ const [data, setData] = useState(initialData)
+
+ return (
+ <div>
+ {/* Client Component UI */}
+ <button onClick={() => refresh()}>Refresh</button>
+ {/* Server Component children */}
+ {children}
+ </div>
+ )
+}
+```
+
+## Streaming with Suspense
+
+```tsx
+// app/page.tsx
+import { Suspense } from 'react'
+import { SlowComponent } from './slow-component'
+import { FastComponent } from './fast-component'
+
+export default function Page() {
+ return (
+ <div>
+ {/* Renders immediately */}
+ <FastComponent />
+
+ {/* Shows fallback while loading */}
+ <Suspense fallback={<div>Loading...</div>}>
+ <SlowComponent />
+ </Suspense>
+ </div>
+ )
+}
+
+// components/slow-component.tsx
+async function getData() {
+ await new Promise(resolve => setTimeout(resolve, 3000))
+ return { data: 'Loaded!' }
+}
+
+export async function SlowComponent() {
+ const data = await getData()
+ return <div>{data.data}</div>
+}
+```
+
+## Parallel Data Fetching
+
+```tsx
+// app/dashboard/page.tsx
+async function getUser() {
+ return fetch('https://api.example.com/user')
+}
+
+async function getPosts() {
+ return fetch('https://api.example.com/posts')
+}
+
+export default async function Dashboard() {
+ // Fetch in parallel
+ const [user, posts] = await Promise.all([
+ getUser(),
+ getPosts(),
+ ])
+
+ return (
+ <div>
+ <UserProfile user={user} />
+ <PostsList posts={posts} />
+ </div>
+ )
+}
+```
+
+## Sequential Data Fetching
+
+```tsx
+// app/artist/[id]/page.tsx
+async function getArtist(id: string) {
+ return fetch(`https://api.example.com/artists/${id}`)
+}
+
+async function getAlbums(artistId: string) {
+ return fetch(`https://api.example.com/artists/${artistId}/albums`)
+}
+
+export default async function ArtistPage({ params }: { params: { id: string } }) {
+ // Sequential: albums depends on artist
+ const artist = await getArtist(params.id)
+ const albums = await getAlbums(artist.id)
+
+ return (
+ <div>
+ <h1>{artist.name}</h1>
+ <Albums albums={albums} />
+ </div>
+ )
+}
+```
+
+## Preloading Data
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const getUser = cache(async (id: string) => {
+ return db.user.findUnique({ where: { id } })
+})
+
+// components/user-profile.tsx
+export async function UserProfile({ userId }: { userId: string }) {
+ const user = await getUser(userId)
+ return <div>{user.name}</div>
+}
+
+// app/page.tsx
+import { getUser } from '@/lib/data'
+import { UserProfile } from '@/components/user-profile'
+
+export default async function Page() {
+ // Preload
+ getUser('123')
+
+ return (
+ <div>
+ {/* This will use cached result */}
+ <UserProfile userId="123" />
+ </div>
+ )
+}
+```
+
+## Server Component Patterns
+
+### Pattern: Layout with Data Fetching
+
+```tsx
+// app/dashboard/layout.tsx
+import { auth } from '@/lib/auth'
+import { db } from '@/lib/db'
+
+export default async function DashboardLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ const session = await auth()
+ const user = await db.user.findUnique({ where: { id: session.userId } })
+
+ return (
+ <div>
+ <Sidebar user={user} />
+ <main>{children}</main>
+ </div>
+ )
+}
+```
+
+### Pattern: Conditional Client Components
+
+```tsx
+// app/page.tsx
+import { ClientComponent } from './client-component'
+
+export default async function Page() {
+ const data = await fetchData()
+
+ // Only render Client Component when needed
+ if (data.requiresInteractivity) {
+ return <ClientComponent data={data} />
+ }
+
+ return <div>{data.content}</div>
+}
+```
+
+### Pattern: Server Component with Client Island
+
+```tsx
+// app/blog/[slug]/page.tsx
+import { LikeButton } from './like-button'
+
+export default async function BlogPost({ params }: { params: { slug: string } }) {
+ const post = await getPost(params.slug)
+
+ return (
+ <article>
+ {/* Server-rendered content */}
+ <h1>{post.title}</h1>
+ <div dangerouslySetInnerHTML={{ __html: post.content }} />
+
+ {/* Client island for interactivity */}
+ <LikeButton postId={post.id} initialLikes={post.likes} />
+ </article>
+ )
+}
+```
+
+## Context in Server/Client Components
+
+```tsx
+// app/providers.tsx
+'use client'
+
+import { ThemeProvider } from 'next-themes'
+
+export function Providers({ children }: { children: React.ReactNode }) {
+ return <ThemeProvider>{children}</ThemeProvider>
+}
+
+// app/layout.tsx
+import { Providers } from './providers'
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html>
+ <body>
+ <Providers>{children}</Providers>
+ </body>
+ </html>
+ )
+}
+```
+
+## Third-Party Components
+
+```tsx
+// components/carousel-wrapper.tsx
+'use client'
+
+import { Carousel } from 'third-party-carousel'
+
+export function CarouselWrapper({ items }: { items: Item[] }) {
+ return <Carousel items={items} />
+}
+
+// app/page.tsx
+import { CarouselWrapper } from '@/components/carousel-wrapper'
+
+export default async function Page() {
+ const items = await fetchItems()
+ return <CarouselWrapper items={items} />
+}
+```
+
+## Edge Runtime
+
+```tsx
+// app/api/route.ts
+export const runtime = 'edge'
+
+export async function GET() {
+ return new Response('Hello from Edge!')
+}
+
+// app/page.tsx
+export const runtime = 'edge'
+
+export default async function Page() {
+ return <div>Edge-rendered page</div>
+}
+```
+
+## Quick Reference
+
+| Capability | Server Component | Client Component |
+|------------|------------------|------------------|
+| Data fetching | ✅ Yes | ⚠️ Use SWR/React Query |
+| Backend access | ✅ Yes (DB, files) | ❌ No |
+| Event handlers | ❌ No | ✅ Yes |
+| State/Effects | ❌ No | ✅ Yes |
+| Browser APIs | ❌ No | ✅ Yes |
+| Bundle size | 0 KB | Adds to bundle |
+| Streaming | ✅ Yes | ❌ No |
+
+## Best Practices
+
+1. **Default to Server Components** - Only use 'use client' when needed
+2. **Move Client Components down** - Push them to leaves of component tree
+3. **Pass data down** - Fetch in Server Components, pass to Client Components
+4. **Use composition** - Nest Server Components inside Client Components via children
+5. **Cache expensive operations** - Use React cache() for deduplication
diff --git a/.agents/skills/seo-audit/SKILL.md b/.agents/skills/seo-audit/SKILL.md
deleted file mode 100644
index c525957..0000000
--- a/.agents/skills/seo-audit/SKILL.md
+++ /dev/null
@@ -1,497 +0,0 @@
----
-name: seo-audit
-description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
-metadata:
- version: 2.0.0
----
-
-# SEO Audit
-
-You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before auditing, understand:
-
-1. **Site Context**
- - What type of site? (SaaS, e-commerce, blog, etc.)
- - What's the primary business goal for SEO?
- - What keywords/topics are priorities?
-
-2. **Current State**
- - Any known issues or concerns?
- - Current organic traffic level?
- - Recent changes or migrations?
-
-3. **Scope**
- - Full site audit or specific pages?
- - Technical + on-page, or one focus area?
- - Access to Search Console / analytics?
-
----
-
-## Audit Framework
-
-### Schema Markup Detection Limitation
-
-**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**
-
-Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `<script>` tags during conversion).
-
-**To accurately check for schema markup, use one of these methods:**
-1. **Browser tool** — render the page and run: `document.querySelectorAll('script[type="application/ld+json"]')`
-2. **Google Rich Results Test** — https://search.google.com/test/rich-results
-3. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)
-
-Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false audit findings — these tools can't see JS-injected schema.
-
-### Priority Order
-1. **Crawlability & Indexation** (can Google find and index it?)
-2. **Technical Foundations** (is the site fast and functional?)
-3. **On-Page Optimization** (is content optimized?)
-4. **Content Quality** (does it deserve to rank?)
-5. **Authority & Links** (does it have credibility?)
-
----
-
-## Technical SEO Audit
-
-### Crawlability
-
-**Robots.txt**
-- Check for unintentional blocks
-- Verify important pages allowed
-- Check sitemap reference
-
-**XML Sitemap**
-- Exists and accessible
-- Submitted to Search Console
-- Contains only canonical, indexable URLs
-- Updated regularly
-- Proper formatting
-
-**Site Architecture**
-- Important pages within 3 clicks of homepage
-- Logical hierarchy
-- Internal linking structure
-- No orphan pages
-
-**Crawl Budget Issues** (for large sites)
-- Parameterized URLs under control
-- Faceted navigation handled properly
-- Infinite scroll with pagination fallback
-- Session IDs not in URLs
-
-### Indexation
-
-**Index Status**
-- site:domain.com check
-- Search Console coverage report
-- Compare indexed vs. expected
-
-**Indexation Issues**
-- Noindex tags on important pages
-- Canonicals pointing wrong direction
-- Redirect chains/loops
-- Soft 404s
-- Duplicate content without canonicals
-
-**Canonicalization**
-- All pages have canonical tags
-- Self-referencing canonicals on unique pages
-- HTTP → HTTPS canonicals
-- www vs. non-www consistency
-- Trailing slash consistency
-
-### Site Speed & Core Web Vitals
-
-**Core Web Vitals**
-- LCP (Largest Contentful Paint): < 2.5s
-- INP (Interaction to Next Paint): < 200ms
-- CLS (Cumulative Layout Shift): < 0.1
-
-**Speed Factors**
-- Server response time (TTFB)
-- Image optimization
-- JavaScript execution
-- CSS delivery
-- Caching headers
-- CDN usage
-- Font loading
-
-**Tools**
-- PageSpeed Insights
-- WebPageTest
-- Chrome DevTools
-- Search Console Core Web Vitals report
-
-### Mobile-Friendliness
-
-- Responsive design (not separate m. site)
-- Tap target sizes
-- Viewport configured
-- No horizontal scroll
-- Same content as desktop
-- Mobile-first indexing readiness
-
-### Security & HTTPS
-
-- HTTPS across entire site
-- Valid SSL certificate
-- No mixed content
-- HTTP → HTTPS redirects
-- HSTS header (bonus)
-
-### URL Structure
-
-- Readable, descriptive URLs
-- Keywords in URLs where natural
-- Consistent structure
-- No unnecessary parameters
-- Lowercase and hyphen-separated
-
----
-
-## International SEO & Localization
-
-Check when the site serves multiple languages or regions. Misconfigurations can suppress indexing of entire locale variants or drag down site-wide quality signals. See [International SEO reference](references/international-seo.md) for evidence and source URLs.
-
-### Hreflang
-
-Three equivalent placement methods: HTML `<link>` in `<head>`, HTTP `Link` headers, XML sitemap `<xhtml:link>`. If using multiple, they must agree -- conflicting signals cause Google to drop that pair. For 10+ locales, prefer sitemap-based (no page weight, no per-request cost).
-
-**Check for:**
-- Self-referencing entry on every page (page must include itself in the hreflang set)
-- Reciprocal links (if A points to B, B must point back to A -- or both are ignored)
-- Valid codes: ISO 639-1 language + optional ISO 3166-1 Alpha 2 region (e.g., `en`, `en-GB` -- never `en-UK`)
-- `x-default` present, pointing to fallback page (language selector or default locale)
-- All target URLs return 200, are indexable, and match their canonical URL
-- No duplicate language-region codes pointing to different URLs
-
-**Common errors:** Missing self-referencing entry (all hreflang ignored). No return tag / one-directional (pair dropped). Invalid codes like `en-UK` (use `en-GB`). Hreflang target is non-canonical, 404, or blocked (cluster discarded). HTML and sitemap annotations disagree (conflicting pair dropped).
-
-**At scale:** `<xhtml:link>` children don't count toward 50K URL sitemap limit, but the 50MB file size limit becomes the bottleneck (plan 2K-5K URLs per file with full hreflang). Focus hreflang on pages receiving wrong-language traffic -- not required on every page. For Bing: supplement with `<html lang>` and `<meta http-equiv="content-language">` (Bing treats hreflang as a weak signal).
-
-### Canonicalization for Multilingual Sites
-
-- Each locale page must self-canonical (e.g., `/ar/page` canonicals to `/ar/page`)
-- Never cross-locale canonical (French to English) -- suppresses the non-canonical locale entirely
-- Canonical URL must appear in the hreflang set -- if not, all hreflang is ignored
-- Canonical overrides hreflang when they conflict
-- Protocol/domain must be consistent across canonical, hreflang, and sitemap (`https` + same domain variant)
-- Paginated locale pages: self-referencing canonical per page (never canonical page 2+ to page 1)
-
-**Common mistakes:** all locales canonical to English (kills indexing), canonical URL not in hreflang set (silently ignored), protocol mismatch between canonical and hreflang, CMS setting deep page canonical to homepage.
-
-### International Sitemaps
-
-**Check for:**
-- `xmlns:xhtml` namespace on `<urlset>`, each `<url>` includes `<xhtml:link>` for all locales including itself
-- `x-default` alternate included; all URLs absolute (full protocol + domain)
-- Sitemap index in Search Console and robots.txt; split by content type, not by locale
-
-**Next.js caveat:** `alternates.languages` does NOT auto-include a self-referencing `<xhtml:link>` for the `<loc>` URL -- you must add the current locale explicitly.
-
-### Locale URL Structure
-
-**Recommended:** Subdirectories (`/en/`, `/ar/`). **Acceptable:** Subdomains or ccTLDs. **Not recommended:** URL parameters (`?lang=en`).
-
-**Check for:**
-- Consistent locale prefix strategy; all locales prefixed (hiding locale from URLs prevents Google from distinguishing versions)
-- Root URL handled as `x-default` with redirect, or serves default locale content
-- No IP/Accept-Language content negotiation (Googlebot: US IPs, no Accept-Language header)
-- Trailing slash + case consistency across locale paths, canonicals, hreflang, and sitemaps
-- 301 redirects from non-canonical format to canonical
-
-**Note:** Google's International Targeting report in Search Console is deprecated. Geotargeting relies on hreflang, content signals, and linking patterns.
-
-### Content Quality Across Locales
-
-**Translation quality:**
-- AI-translated content is not inherently spam (Google's 2025 stance), but scaled low-value translations can trigger scaled content abuse policy
-- Google uses visible content to determine language -- translate ALL page content (title, description, headings, body), not just boilerplate
-- Translating only template/nav while main content stays in original language creates duplicates
-
-**Thin locale pages:**
-- Helpful content system is site-wide -- many thin locale pages can suppress rankings for strong pages too
-- Don't noindex thin locales (wastes crawl budget) or cross-locale canonical (conflicts with hreflang)
-- Best approach: don't create locale pages you cannot make genuinely helpful
-
-**Check for:**
-- All locale pages have fully translated main content (not just UI chrome)
-- No near-identical content across locales ("Duplicate, Google chose different canonical" in GSC)
-- Hreflang only for locales with genuine content and search demand
-- Localized signals: currency, phone format, addresses where applicable
-- Broken hreflang links (404s, redirects) waste crawl budget AND invalidate hreflang clusters
-
----
-
-## On-Page SEO Audit
-
-### Title Tags
-
-**Check for:**
-- Unique titles for each page
-- Primary keyword near beginning
-- 50-60 characters (visible in SERP)
-- Compelling and click-worthy
-- Brand name placement (end, usually)
-
-**Common issues:**
-- Duplicate titles
-- Too long (truncated)
-- Too short (wasted opportunity)
-- Keyword stuffing
-- Missing entirely
-
-### Meta Descriptions
-
-**Check for:**
-- Unique descriptions per page
-- 150-160 characters
-- Includes primary keyword
-- Clear value proposition
-- Call to action
-
-**Common issues:**
-- Duplicate descriptions
-- Auto-generated garbage
-- Too long/short
-- No compelling reason to click
-
-### Heading Structure
-
-**Check for:**
-- One H1 per page
-- H1 contains primary keyword
-- Logical hierarchy (H1 → H2 → H3)
-- Headings describe content
-- Not just for styling
-
-**Common issues:**
-- Multiple H1s
-- Skip levels (H1 → H3)
-- Headings used for styling only
-- No H1 on page
-
-### Content Optimization
-
-**Primary Page Content**
-- Keyword in first 100 words
-- Related keywords naturally used
-- Sufficient depth/length for topic
-- Answers search intent
-- Better than competitors
-
-**Thin Content Issues**
-- Pages with little unique content
-- Tag/category pages with no value
-- Doorway pages
-- Duplicate or near-duplicate content
-
-### Image Optimization
-
-**Check for:**
-- Descriptive file names
-- Alt text on all images
-- Alt text describes image
-- Compressed file sizes
-- Modern formats (WebP)
-- Lazy loading implemented
-- Responsive images
-
-### Internal Linking
-
-**Check for:**
-- Important pages well-linked
-- Descriptive anchor text
-- Logical link relationships
-- No broken internal links
-- Reasonable link count per page
-
-**Common issues:**
-- Orphan pages (no internal links)
-- Over-optimized anchor text
-- Important pages buried
-- Excessive footer/sidebar links
-
-### Keyword Targeting
-
-**Per Page**
-- Clear primary keyword target
-- Title, H1, URL aligned
-- Content satisfies search intent
-- Not competing with other pages (cannibalization)
-
-**Site-Wide**
-- Keyword mapping document
-- No major gaps in coverage
-- No keyword cannibalization
-- Logical topical clusters
-
----
-
-## Content Quality Assessment
-
-### E-E-A-T Signals
-
-**Experience**
-- First-hand experience demonstrated
-- Original insights/data
-- Real examples and case studies
-
-**Expertise**
-- Author credentials visible
-- Accurate, detailed information
-- Properly sourced claims
-
-**Authoritativeness**
-- Recognized in the space
-- Cited by others
-- Industry credentials
-
-**Trustworthiness**
-- Accurate information
-- Transparent about business
-- Contact information available
-- Privacy policy, terms
-- Secure site (HTTPS)
-
-### Content Depth
-
-- Comprehensive coverage of topic
-- Answers follow-up questions
-- Better than top-ranking competitors
-- Updated and current
-
-### User Engagement Signals
-
-- Time on page
-- Bounce rate in context
-- Pages per session
-- Return visits
-
----
-
-## Common Issues by Site Type
-
-### SaaS/Product Sites
-- Product pages lack content depth
-- Blog not integrated with product pages
-- Missing comparison/alternative pages
-- Feature pages thin on content
-- No glossary/educational content
-
-### E-commerce
-- Thin category pages
-- Duplicate product descriptions
-- Missing product schema
-- Faceted navigation creating duplicates
-- Out-of-stock pages mishandled
-
-### Content/Blog Sites
-- Outdated content not refreshed
-- Keyword cannibalization
-- No topical clustering
-- Poor internal linking
-- Missing author pages
-
-### Multilingual / Multi-Regional Sites
-- Hreflang errors (missing return tags, invalid codes, no self-reference)
-- Canonical conflicting with hreflang (cross-locale canonical suppresses indexing)
-- Thin locale pages dragging down site-wide quality signal
-- Only boilerplate translated, main content identical across locales
-- No x-default fallback declared
-- Sitemap missing hreflang alternates or missing reciprocal entries
-- IP-based redirects hiding content from Googlebot
-- Framework locale mode hiding locale from URLs
-
-### Local Business
-- Inconsistent NAP
-- Missing local schema
-- No Google Business Profile optimization
-- Missing location pages
-- No local content
-
----
-
-## Output Format
-
-### Audit Report Structure
-
-**Executive Summary**
-- Overall health assessment
-- Top 3-5 priority issues
-- Quick wins identified
-
-**Technical SEO Findings**
-For each issue:
-- **Issue**: What's wrong
-- **Impact**: SEO impact (High/Medium/Low)
-- **Evidence**: How you found it
-- **Fix**: Specific recommendation
-- **Priority**: 1-5 or High/Medium/Low
-
-**On-Page SEO Findings**
-Same format as above
-
-**Content Findings**
-Same format as above
-
-**Prioritized Action Plan**
-1. Critical fixes (blocking indexation/ranking)
-2. High-impact improvements
-3. Quick wins (easy, immediate benefit)
-4. Long-term recommendations
-
----
-
-## References
-
-- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
-- [International SEO](references/international-seo.md): Evidence and sources for hreflang, canonical + i18n, sitemaps, URL structure, and content quality across locales
-- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **ai-seo** skill
-
----
-
-## Tools Referenced
-
-**Free Tools**
-- Google Search Console (essential)
-- Google PageSpeed Insights
-- Bing Webmaster Tools
-- Rich Results Test (**use this for schema validation — it renders JavaScript**)
-- Mobile-Friendly Test
-- Schema Validator
-
-> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Use the browser tool, Rich Results Test, or Screaming Frog instead — they render JavaScript and capture dynamically-injected markup. See the Schema Markup Detection Limitation section above.
-
-**Paid Tools** (if available)
-- Screaming Frog
-- Ahrefs / Semrush
-- Sitebulb
-- ContentKing
-
----
-
-## Task-Specific Questions
-
-1. What pages/keywords matter most?
-2. Do you have Search Console access?
-3. Any recent changes or migrations?
-4. Who are your top organic competitors?
-5. What's your current organic traffic baseline?
-
----
-
-## Related Skills
-
-- **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
-- **programmatic-seo**: For building SEO pages at scale
-- **site-architecture**: For page hierarchy, navigation design, and URL structure
-- **schema**: For implementing structured data
-- **cro**: For optimizing pages for conversion (not just ranking)
-- **analytics**: For measuring SEO performance
diff --git a/.agents/skills/seo-audit/evals/evals.json b/.agents/skills/seo-audit/evals/evals.json
deleted file mode 100644
index e3415c5..0000000
--- a/.agents/skills/seo-audit/evals/evals.json
+++ /dev/null
@@ -1,136 +0,0 @@
-{
- "skill_name": "seo-audit",
- "evals": [
- {
- "id": 1,
- "prompt": "Can you do an SEO audit of our SaaS website? We're getting about 2,000 organic visits/month but feel like we should be getting more. URL: https://example.com",
- "expected_output": "Should check for product-marketing.md first. Should ask clarifying questions about priority keywords, Search Console access, recent changes, and competitors. Should follow the audit framework priority order: Crawlability & Indexation, Technical Foundations, On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure, and content optimization. Should NOT report on schema markup based solely on web_fetch (must note the detection limitation). Output should follow the Audit Report Structure: Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and Prioritized Action Plan.",
- "assertions": [
- "Checks for product-marketing.md",
- "Asks clarifying questions about keywords, Search Console, recent changes",
- "Follows audit priority order: crawlability first, then technical, on-page, content, authority",
- "Checks robots.txt and XML sitemap",
- "Evaluates title tags, meta descriptions, heading structure",
- "Does NOT claim 'no schema found' based on web_fetch alone",
- "Notes schema markup detection limitation",
- "Output has Executive Summary",
- "Output has Prioritized Action Plan",
- "Each finding has Issue, Impact, Evidence, Fix, and Priority"
- ],
- "files": []
- },
- {
- "id": 2,
- "prompt": "Why am I not ranking for 'project management software'? We have a page targeting that keyword but it's stuck on page 3.",
- "expected_output": "Should trigger on the casual 'why am I not ranking' phrasing. Should investigate both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword; evaluate content depth vs competitors; check for keyword cannibalization. Technical: check indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals, content depth, user engagement. Should provide specific, actionable fixes organized by priority. Should mention competitive analysis against current top-ranking pages.",
- "assertions": [
- "Triggers on casual 'why am I not ranking' phrasing",
- "Checks title tag, H1, URL alignment with target keyword",
- "Evaluates content depth vs competitors",
- "Checks for keyword cannibalization",
- "Checks indexation status and canonical tags",
- "Assesses E-E-A-T signals",
- "Mentions competitive analysis against top-ranking pages",
- "Provides actionable fixes organized by priority"
- ],
- "files": []
- },
- {
- "id": 3,
- "prompt": "We just migrated from WordPress to Next.js and our organic traffic dropped 40% in the last month. Help!",
- "expected_output": "Should treat this as an urgent migration diagnostic. Should immediately check: redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should check for common migration issues: redirect chains/loops, soft 404s, lost internal links, changed URL structures without redirects. Should reference Search Console coverage report for indexation issues. Should provide a prioritized recovery plan with critical fixes first. Should mention monitoring timeline expectations (recovery can take weeks).",
- "assertions": [
- "Treats as urgent migration diagnostic",
- "Checks redirect mapping (301s)",
- "Checks canonical tags on new pages",
- "Checks robots.txt not blocking crawlers",
- "Checks XML sitemap updated and submitted",
- "Checks for redirect chains or loops",
- "Checks for soft 404s",
- "References Search Console coverage report",
- "Provides prioritized recovery plan",
- "Mentions recovery timeline expectations"
- ],
- "files": []
- },
- {
- "id": 4,
- "prompt": "Review the technical SEO of our e-commerce site. We have about 50,000 products and use faceted navigation.",
- "expected_output": "Should focus on e-commerce-specific technical issues: faceted navigation creating duplicate content, crawl budget management for large product catalog, parameterized URLs, product schema markup (with the caveat about detection limitations). Should check for thin category pages, duplicate product descriptions, out-of-stock page handling. Should address crawl budget issues: pagination, infinite scroll handling, session IDs in URLs. Should provide structured findings with Impact ratings and specific fixes.",
- "assertions": [
- "Addresses faceted navigation duplicate content",
- "Addresses crawl budget for large catalog",
- "Checks for parameterized URL issues",
- "Mentions product schema with detection limitation caveat",
- "Checks for thin category pages",
- "Checks for duplicate product descriptions",
- "Addresses out-of-stock page handling",
- "Addresses pagination and infinite scroll",
- "Findings include Impact ratings and specific fixes"
- ],
- "files": []
- },
- {
- "id": 5,
- "prompt": "Can you check our blog posts for on-page SEO issues? We publish 4 posts per week but traffic has been flat for 6 months.",
- "expected_output": "Should apply the Content/Blog Sites framework: check for outdated content not refreshed, keyword cannibalization, missing topical clustering, poor internal linking, missing author pages. Should audit on-page elements: title tags, meta descriptions, heading structure, keyword targeting per post. Should assess E-E-A-T signals for blog content. Should check for content depth issues and whether posts answer search intent. Should recommend a content audit process and provide a prioritized action plan for the existing content library.",
- "assertions": [
- "Applies Content/Blog Sites framework",
- "Checks for outdated content",
- "Checks for keyword cannibalization",
- "Checks for topical clustering",
- "Checks for internal linking quality",
- "Checks for author pages and E-E-A-T signals",
- "Audits title tags, meta descriptions, heading structure",
- "Assesses whether content answers search intent",
- "Recommends content audit process",
- "Provides prioritized action plan"
- ],
- "files": []
- },
- {
- "id": 6,
- "prompt": "I run a local plumbing business with 3 locations. My website barely shows up when people search for 'plumber near me' in our areas. What's wrong?",
- "expected_output": "Should apply the Local Business site-type framework. Should check for: inconsistent NAP (Name, Address, Phone) across the site, missing local schema markup (with detection limitation caveat), Google Business Profile optimization, missing individual location pages for each of the 3 locations, and missing local content. Should also check standard technical and on-page factors. Should recommend local-specific fixes: location-specific pages with unique content, local schema on each, GBP optimization, citation consistency.",
- "assertions": [
- "Applies Local Business framework",
- "Checks NAP consistency",
- "Checks for local schema markup with detection caveat",
- "Addresses Google Business Profile optimization",
- "Recommends individual location pages for each location",
- "Recommends local content strategy",
- "Checks standard technical SEO factors too",
- "Provides prioritized local SEO action plan"
- ],
- "files": []
- },
- {
- "id": 7,
- "prompt": "Our site loads really slowly, especially on mobile. Pages take 5-6 seconds to load. Is this hurting our SEO?",
- "expected_output": "Should focus on Site Speed and Core Web Vitals. Should explain CWV thresholds: LCP < 2.5s, INP < 200ms, CLS < 0.1, and that 5-6s load time is well above acceptable. Should investigate speed factors: server response time (TTFB), image optimization, JavaScript execution, CSS delivery, caching headers, CDN usage, font loading. Should recommend specific tools: PageSpeed Insights, WebPageTest, Chrome DevTools, Search Console CWV report. Should explain that yes, page speed is a ranking factor and directly impacts SEO. Should provide prioritized fixes.",
- "assertions": [
- "Focuses on Core Web Vitals",
- "Explains CWV thresholds (LCP, INP, CLS)",
- "Identifies 5-6s as well above acceptable",
- "Investigates specific speed factors",
- "Recommends specific diagnostic tools",
- "Confirms page speed impacts SEO rankings",
- "Provides prioritized speed fixes",
- "Addresses mobile-specific performance"
- ],
- "files": []
- },
- {
- "id": 8,
- "prompt": "I want to add FAQ schema to my product pages. Can you help me set that up?",
- "expected_output": "Should recognize this is a schema markup implementation task, not an SEO audit. Should defer to or cross-reference the schema skill, which specifically handles structured data implementation including FAQ schema. May briefly mention that FAQ schema can enable rich results, but should make clear that schema is the right skill for implementation.",
- "assertions": [
- "Recognizes this as schema markup implementation",
- "References or defers to schema skill",
- "Does not attempt a full SEO audit",
- "May briefly mention FAQ schema benefits"
- ],
- "files": []
- }
- ]
-}
diff --git a/.agents/skills/seo-audit/references/ai-writing-detection.md b/.agents/skills/seo-audit/references/ai-writing-detection.md
deleted file mode 100644
index cb67ece..0000000
--- a/.agents/skills/seo-audit/references/ai-writing-detection.md
+++ /dev/null
@@ -1,200 +0,0 @@
-# AI Writing Detection
-
-Words, phrases, and punctuation patterns commonly associated with AI-generated text. Avoid these to ensure writing sounds natural and human.
-
-Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Walter Writes (2025), Textero (2025), Plagiarism Today (2025), Rolling Stone (2025), MDPI Blog (2025)
-
----
-
-## Contents
-- Em Dashes: The Primary AI Tell
-- Overused Verbs
-- Overused Adjectives
-- Overused Transitions and Connectors
-- Phrases That Signal AI Writing (Opening Phrases, Transitional Phrases, Concluding Phrases, Structural Patterns)
-- Filler Words and Empty Intensifiers
-- Academic-Specific AI Tells
-- How to Self-Check
-
-## Em Dashes: The Primary AI Tell
-
-**The em dash (—) has become one of the most reliable markers of AI-generated content.**
-
-Em dashes are longer than hyphens (-) and are used for emphasis, interruptions, or parenthetical information. While they have legitimate uses in writing, AI models drastically overuse them.
-
-### Why Em Dashes Signal AI Writing
-- AI models were trained on edited books, academic papers, and style guides where em dashes appear frequently
-- AI uses em dashes as a shortcut for sentence variety instead of commas, colons, or parentheses
-- Most human writers rarely use em dashes because they don't exist as a standard keyboard key
-- The overuse is so consistent that it has become the unofficial signature of ChatGPT writing
-
-### What To Do Instead
-| Instead of | Use |
-|------------|-----|
-| The results—which were surprising—showed... | The results, which were surprising, showed... |
-| This approach—unlike traditional methods—allows... | This approach, unlike traditional methods, allows... |
-| The study found—as expected—that... | The study found, as expected, that... |
-| Communication skills—both written and verbal—are essential | Communication skills (both written and verbal) are essential |
-
-### Guidelines
-- Use commas for most parenthetical information
-- Use colons to introduce explanations or lists
-- Use parentheses for supplementary information
-- Reserve em dashes for rare, deliberate emphasis only
-- If you find yourself using more than one em dash per page, revise
-
----
-
-## Overused Verbs
-
-| Avoid | Use Instead |
-|-------|-------------|
-| delve (into) | explore, examine, investigate, look at |
-| leverage | use, apply, draw on |
-| optimise | improve, refine, enhance |
-| utilise | use |
-| facilitate | help, enable, support |
-| foster | encourage, support, develop, nurture |
-| bolster | strengthen, support, reinforce |
-| underscore | emphasise, highlight, stress |
-| unveil | reveal, show, introduce, present |
-| navigate | manage, handle, work through |
-| streamline | simplify, make more efficient |
-| enhance | improve, strengthen |
-| endeavour | try, attempt, effort |
-| ascertain | find out, determine, establish |
-| elucidate | explain, clarify, make clear |
-
----
-
-## Overused Adjectives
-
-| Avoid | Use Instead |
-|-------|-------------|
-| robust | strong, reliable, thorough, solid |
-| comprehensive | complete, thorough, full, detailed |
-| pivotal | key, critical, central, important |
-| crucial | important, key, essential, critical |
-| vital | important, essential, necessary |
-| transformative | significant, important, major |
-| cutting-edge | new, advanced, recent, modern |
-| groundbreaking | new, original, significant |
-| innovative | new, original, creative |
-| seamless | smooth, easy, effortless |
-| intricate | complex, detailed, complicated |
-| nuanced | subtle, complex, detailed |
-| multifaceted | complex, varied, diverse |
-| holistic | complete, whole, comprehensive |
-
----
-
-## Overused Transitions and Connectors
-
-| Avoid | Use Instead |
-|-------|-------------|
-| furthermore | also, in addition, and |
-| moreover | also, and, besides |
-| notwithstanding | despite, even so, still |
-| that being said | however, but, still |
-| at its core | essentially, fundamentally, basically |
-| to put it simply | in short, simply put |
-| it is worth noting that | note that, importantly |
-| in the realm of | in, within, regarding |
-| in the landscape of | in, within |
-| in today's [anything] | currently, now, today |
-
----
-
-## Phrases That Signal AI Writing
-
-### Opening Phrases to Avoid
-- "In today's fast-paced world..."
-- "In today's digital age..."
-- "In an era of..."
-- "In the ever-evolving landscape of..."
-- "In the realm of..."
-- "It's important to note that..."
-- "Let's delve into..."
-- "Imagine a world where..."
-
-### Transitional Phrases to Avoid
-- "That being said..."
-- "With that in mind..."
-- "It's worth mentioning that..."
-- "At its core..."
-- "To put it simply..."
-- "In essence..."
-- "This begs the question..."
-
-### Concluding Phrases to Avoid
-- "In conclusion..."
-- "To sum up..."
-- "By [doing X], you can [achieve Y]..."
-- "In the final analysis..."
-- "All things considered..."
-- "At the end of the day..."
-
-### Structural Patterns to Avoid
-- "Whether you're a [X], [Y], or [Z]..." (listing three examples after "whether")
-- "It's not just [X], it's also [Y]..."
-- "Think of [X] as [elaborate metaphor]..."
-- Starting sentences with "By" followed by a gerund: "By understanding X, you can Y..."
-
----
-
-## Filler Words and Empty Intensifiers
-
-These words often add nothing to meaning. Remove them or find specific alternatives:
-
-- absolutely
-- actually
-- basically
-- certainly
-- clearly
-- definitely
-- essentially
-- extremely
-- fundamentally
-- incredibly
-- interestingly
-- naturally
-- obviously
-- quite
-- really
-- significantly
-- simply
-- surely
-- truly
-- ultimately
-- undoubtedly
-- very
-
----
-
-## Academic-Specific AI Tells
-
-| Avoid | Use Instead |
-|-------|-------------|
-| shed light on | clarify, explain, reveal |
-| pave the way for | enable, allow, make possible |
-| a myriad of | many, numerous, various |
-| a plethora of | many, numerous, several |
-| paramount | very important, essential, critical |
-| pertaining to | about, regarding, concerning |
-| prior to | before |
-| subsequent to | after |
-| in light of | because of, given, considering |
-| with respect to | about, regarding, for |
-| in terms of | regarding, for, about |
-| the fact that | that (or rewrite sentence) |
-
----
-
-## How to Self-Check
-
-1. Read your text aloud. If phrases sound unnatural in speech, revise them
-2. Ask: "Would I say this in a conversation with a colleague?"
-3. Check for repetitive sentence structures
-4. Look for clusters of the words listed above
-5. Ensure varied sentence lengths (not all similar length)
-6. Verify each intensifier adds genuine meaning
diff --git a/.agents/skills/seo-audit/references/international-seo.md b/.agents/skills/seo-audit/references/international-seo.md
deleted file mode 100644
index d2a2d1e..0000000
--- a/.agents/skills/seo-audit/references/international-seo.md
+++ /dev/null
@@ -1,230 +0,0 @@
-# International SEO: Evidence & Sources
-
-Detailed evidence backing the International SEO & Localization section of the SEO Audit skill. Organized by topic with source URLs and key quotes.
-
----
-
-## Hreflang
-
-### Placement Methods
-
-Google supports three equivalent methods: HTML `<link>` in `<head>`, HTTP `Link` headers, and XML sitemap `<xhtml:link>` elements. Google confirmed no method is prioritized over another.
-
-Google combines signals from both HTML and sitemaps. If the same language-region pair points to different URLs across methods, Google drops that pair rather than guessing.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [SEJ: Google Combines Hreflang Signals](https://www.searchenginejournal.com/google-combines-hreflang-signals-from-html-sitemaps/389219/)
-
-### Reciprocal Requirement
-
-Google's docs: "If page X links to page Y, page Y must link back to page X. If not, those annotations may be ignored or not interpreted correctly."
-
-Every page must include itself (self-referencing) in the hreflang set. Missing self-referencing is the #1 error found by Semrush audits. A study of 374,756 domains found 67% of hreflang implementations had issues.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Semrush: 9 Common Hreflang Errors](https://www.semrush.com/blog/hreflang-errors/)
-- [SE Land: 31% of International Websites Contain Hreflang Errors](https://searchengineland.com/study-31-of-international-websites-contain-hreflang-errors-395161)
-
-### x-default
-
-Introduced April 2013. Designates the fallback page for users whose language/region matches no declared variant. Can point to the same URL as one of the language-specific alternates. Must be included in the complete set of annotations on every variant page.
-
-- [Google Blog: x-default hreflang](https://developers.google.com/search/blog/2013/04/x-default-hreflang-for-international-pages)
-- [Google Blog: How x-default can help you (2023)](https://developers.google.com/search/blog/2023/05/x-default)
-
-### Language & Region Codes
-
-Language: ISO 639-1 (2-letter). Region: ISO 3166-1 Alpha 2 (2-letter). Format: `language[-script][-region]`.
-
-You cannot specify a region code alone. Common mistakes: `en-UK` (should be `en-GB`), `es-419` (not ISO 3166-1). A study found 8.9% of sites using hreflang contain invalid language codes.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [SE Land: 31% Study](https://searchengineland.com/study-31-of-international-websites-contain-hreflang-errors-395161)
-
-### Hreflang at Scale (20+ locales)
-
-With 20 locales, HTML `<head>` hreflang adds ~1.5KB per page for zero user benefit. Sitemap-based hreflang has zero runtime performance impact. `<xhtml:link>` child elements do NOT count toward the 50,000 URL sitemap limit (only `<loc>` elements count).
-
-John Mueller recommends focusing hreflang on pages receiving wrong-language traffic, not every page: "I wouldn't do it for any of the other pages of the site because it's so complex & hard to manage."
-
-- [SERoundtable: Child Elements Don't Count](https://www.seroundtable.com/google-child-elements-dont-count-towards-sitemap-url-limit-34377.html)
-- [SERoundtable: Where To Focus Hreflang](https://www.seroundtable.com/using-hreflang-34127.html)
-- [Yoast: hreflang Ultimate Guide](https://yoast.com/hreflang-ultimate-guide/)
-
-### Google vs Bing
-
-Bing treats hreflang as a "weak signal." Bing relies on `content-language` meta tag, HTML `lang` attribute, ccTLDs, and server location. Yandex supports hreflang like Google.
-
-For both engines: implement hreflang (Google/Yandex) + `<html lang="...">` + `<meta http-equiv="content-language">` (Bing).
-
-- [Digital Ready Marketing: Bing Doesn't Use Hreflang](https://digitalreadymarketing.com/bing-doesnt-use-hreflang-annotation-what-does-it-use/)
-- [Yoast: hreflang Ultimate Guide](https://yoast.com/hreflang-ultimate-guide/)
-
----
-
-## Canonicalization & i18n
-
-### Self-Referencing Canonicals
-
-Each locale page must canonical to itself. John Mueller: "Don't use a rel=canonical across languages/countries, only use it on a per-country/language basis."
-
-Google's docs: "Specify a canonical page in the same language, or the best possible substitute language if a canonical doesn't exist for the same language."
-
-- [John Mueller: hreflang canonical](https://johnmu.com/hreflang-canonical/)
-- [Google: Consolidate Duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
-
-### Canonical Overrides Hreflang
-
-Mueller: "If your canonical is pointing somewhere else, Google will follow that and ignore your hreflang annotation." The canonical URL must be one of the URLs in the hreflang set, or all hreflang markup is ignored.
-
-Google also states: "Google prefers URLs that are part of hreflang clusters for canonicalization" -- when signals align, hreflang strengthens canonical selection.
-
-- [John Mueller: hreflang canonical](https://johnmu.com/hreflang-canonical/)
-- [SEJ: Hreflang Tags Are Hints](https://www.searchenginejournal.com/google-reminds-that-hreflang-tags-are-hints-not-directives/546428/)
-- [Google: Consolidate Duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
-
-### Near-Duplicate Regional Variants
-
-Mueller (2023 Office Hours): "If the content is completely the same, and we can't tell any difference, then for simplicity and user experience we may just show one version -- even if hreflang is present."
-
-Google's duplicate detection runs BEFORE hreflang evaluation. To keep both versions indexed, you need substantive content differences beyond currency symbols.
-
-- [International Web Mastery: Same-Language Duplicate Pages](https://internationalwebmastery.com/blog/how-google-handles-canonicalization-of-same-language-duplicate-near-duplicate-pages/)
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Pagination Across Locales
-
-Google: "Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL." Each paginated page in each locale gets self-referencing canonical. `rel="next/prev"` deprecated March 2019.
-
-- [Google: Pagination Best Practices](https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading)
-
----
-
-## International Sitemaps
-
-### Structure
-
-Each `<url>` entry includes `<xhtml:link>` alternates for every locale. Requires `xmlns:xhtml="http://www.w3.org/1999/xhtml"` namespace.
-
-Split sitemaps by content type, not by locale. Splitting by locale creates maintenance problems because every locale sitemap must reference every other locale (reciprocal requirement).
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Lumar: How Google Handles Hreflang](https://www.lumar.io/office-hours/hreflang/)
-
-### Size Limits
-
-50,000 URLs / 50MB uncompressed per sitemap. Only `<loc>` elements count toward the 50K limit. But with 20 hreflang alternates per entry, the 50MB file size limit becomes the bottleneck. Plan for 2,000-5,000 URLs per sitemap when using full hreflang.
-
-- [Google: Build and Submit a Sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)
-- [SERoundtable: Sitemap 50,000 Limit](https://www.seroundtable.com/google-sitemap-50-000-limit-based-on-location-urls-not-alternative-urls-33843.html)
-
-### Submission
-
-Submit the sitemap index in Search Console AND reference it in robots.txt. Individual child sitemaps can be submitted separately for per-sitemap reporting.
-
-- [Google: Build and Submit a Sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)
-
-### Next.js Caveat
-
-Next.js `alternates.languages` does NOT automatically include a self-referencing `<xhtml:link>` for the `<loc>` URL. You must explicitly include the `<loc>` URL's own language in the `languages` object.
-
-- [Next.js Docs: sitemap.xml](https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap)
-
----
-
-## URL Structure
-
-### Strategies Compared
-
-Google treats subdirectories and subdomains equivalently. Mueller: "From our point of view...they say subdomains and subdirectories are essentially equivalent."
-
-URL parameters (`?lang=en`) are explicitly "Not recommended" per Google docs.
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Default Language
-
-Mueller recommends: set `/` as x-default, put each language in its own prefix. Without marking `/` as x-default, "to Google it can look like '/' is a separate page from the others."
-
-- [Google Blog: x-default](https://developers.google.com/search/blog/2023/05/x-default)
-- [Google Blog: Creating the Right Homepage](https://developers.google.com/search/blog/2014/05/creating-right-homepage-for-your)
-
-### Content Negotiation / IP Redirects
-
-Google strongly advises against locale-adaptive pages. Googlebot crawls from US IPs and does not send Accept-Language headers. Separate URLs + hreflang are required.
-
-- [Google: Locale-Adaptive Pages](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages)
-
-### Trailing Slash Consistency
-
-Mueller: trailing slash is "a significant part of the URL and will change the URL if it's there or not." Pick one format for all locale paths, internal links, canonicals, hreflang, and sitemaps.
-
-Mueller (2025): "Consistency is the biggest technical SEO factor."
-
-- [SERoundtable: Consistency Is The Biggest Technical SEO Factor](https://www.seroundtable.com/google-consistency-seo-40427.html)
-
-### Search Console Geotargeting
-
-The International Targeting report is deprecated. Google now relies entirely on hreflang, content language analysis, and linking patterns. You can add subdirectory properties for per-locale reporting.
-
-- [Google Support: International Targeting Deprecated](https://support.google.com/webmasters/answer/12474899?hl=en)
-
-### Framework Locale Modes
-
-Use `localePrefix: 'always'` (next-intl) or equivalent. Never hide locale from URLs -- Google needs unique URLs per language. Using `'never'` mode disables alternate links entirely.
-
-- [next-intl: Routing Configuration](https://next-intl.dev/docs/routing/configuration)
-- [Next.js Discussion #18419](https://github.com/vercel/next.js/discussions/18419)
-
----
-
-## Content Quality Across Locales
-
-### Auto-Translated Content (2025 Stance)
-
-Google removed longstanding guidance advising against auto-translated content in mid-2025. Current stance: "Our policies do not strictly define content that has been translated by AI as spam." The scaled content abuse policy mentions translation as a possible vector, but does not ban it.
-
-Reddit scaled AI translations to 35+ languages with Google's knowledge. The key distinction is intent and quality, not the method.
-
-- [Google Spam Policies](https://developers.google.com/search/docs/essentials/spam-policies)
-- [Glenn Gabe: Auto-Translating Content](https://www.gsqi.com/marketing-blog/auto-translating-content-google-scaled-content-abuse/)
-- [SE Land: Reddit AI Translations](https://searchengineland.com/google-comments-on-reddits-use-of-ai-to-translate-its-pages-456908)
-
-### Thin Locale Pages
-
-Google: "Localized versions of a page are only considered duplicates if the main content of the page remains untranslated." Pages with only translated boilerplate get clustered as duplicates.
-
-Do NOT use noindex for unwanted locale pages (wastes crawl budget). Do NOT canonical cross-locale (conflicts with hreflang). Best approach: don't create locale pages you can't make genuinely helpful.
-
-- [Google: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Google: Crawl Budget Management](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget)
-
-### Helpful Content System Impact
-
-Merged into core ranking March 2024. Site-wide signal: "any content -- not just unhelpful content -- on sites determined to have relatively high amounts of unhelpful content overall is less likely to perform well in Search."
-
-Low-quality translated pages can drag down the entire site. This is the strongest argument against creating locale pages that aren't genuinely helpful.
-
-- [Google Blog: Helpful Content Update](https://developers.google.com/search/blog/2022/08/helpful-content-update)
-- [Amsive: What Changed in 2024](https://www.amsive.com/insights/seo/googles-helpful-content-update-ranking-system-what-happened-and-what-changed-in-2024/)
-
-### Partial Translation
-
-Google: "Translating only the boilerplate text of your pages while keeping the bulk of your content in a single language...can create a bad user experience." Google uses visible content (not lang attribute) to determine page language.
-
-Translate ALL content on a page if you create a locale version. Untranslated metadata (title, description) in the wrong language reduces CTR.
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Crawl Budget
-
-Only a concern for 1M+ pages or 10K+ pages changing daily. But alternate URLs (hreflang targets) do consume crawl budget. Broken hreflang links waste budget AND invalidate signals.
-
-- [Google: Crawl Budget Management](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget)
-- [Google Blog: Crawl Budget](https://developers.google.com/search/blog/2017/01/what-crawl-budget-means-for-googlebot)
-
-### Locale-Specific Signals
-
-Google identifies audience via: "local addresses and phone numbers on the pages, the use of local language and currency, links from other local sites, or signals from your Business Profile."
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
diff --git a/.claude/skills/nextjs-developer/SKILL.md b/.claude/skills/nextjs-developer/SKILL.md
new file mode 100644
index 0000000..eafe4b4
--- /dev/null
+++ b/.claude/skills/nextjs-developer/SKILL.md
@@ -0,0 +1,145 @@
+---
+name: nextjs-developer
+description: "Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance."
+license: MIT
+metadata:
+ author: https://github.com/Jeffallan
+ version: "1.1.0"
+ domain: frontend
+ triggers: Next.js, Next.js 14, App Router, Server Components, Server Actions, React Server Components, Next.js deployment, Vercel, Next.js performance
+ role: specialist
+ scope: implementation
+ output-format: code
+ related-skills: typescript-pro
+---
+
+# Next.js Developer
+
+Senior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.
+
+## Core Workflow
+
+1. **Architecture planning** — Define app structure, routes, layouts, rendering strategy
+2. **Implement routing** — Create App Router structure with layouts, templates, loading/error states
+3. **Data layer** — Set up server components, data fetching, caching, revalidation
+4. **Optimize** — Images, fonts, bundles, streaming, edge runtime
+5. **Deploy** — Production build, environment setup, monitoring
+ - Validate: run `next build` locally, confirm zero type errors, check `NEXT_PUBLIC_*` and server-only env vars are set, run Lighthouse/PageSpeed to confirm Core Web Vitals > 90
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| App Router | `references/app-router.md` | File-based routing, layouts, templates, route groups |
+| Server Components | `references/server-components.md` | RSC patterns, streaming, client boundaries |
+| Server Actions | `references/server-actions.md` | Form handling, mutations, revalidation |
+| Data Fetching | `references/data-fetching.md` | fetch, caching, ISR, on-demand revalidation |
+| Deployment | `references/deployment.md` | Vercel, self-hosting, Docker, optimization |
+
+## Constraints
+
+### MUST DO (Next.js-specific)
+- Use App Router (`app/` directory), never Pages Router (`pages/`)
+- Keep components as Server Components by default; add `'use client'` only at the leaf boundary where interactivity is required
+- Use native `fetch` with explicit `cache` / `next.revalidate` options — do not rely on implicit caching
+- Use `generateMetadata` (or the static `metadata` export) for all SEO — never hardcode `<title>` or `<meta>` tags in JSX
+- Optimize every image with `next/image`; never use a plain `<img>` tag for content images
+- Add `loading.tsx` and `error.tsx` at every route segment that performs async data fetching
+
+### MUST NOT DO
+- Convert components to Client Components just to access data — fetch server-side first
+- Skip `loading.tsx`/`error.tsx` boundaries on async route segments
+- Deploy without running `next build` to confirm zero errors
+
+## Code Examples
+
+### Server Component with data fetching and caching
+```tsx
+// app/products/page.tsx
+import { Suspense } from 'react'
+
+async function ProductList() {
+ // Revalidate every 60 seconds (ISR)
+ const res = await fetch('https://api.example.com/products', {
+ next: { revalidate: 60 },
+ })
+ if (!res.ok) throw new Error('Failed to fetch products')
+ const products: Product[] = await res.json()
+
+ return (
+ <ul>
+ {products.map((p) => (
+ <li key={p.id}>{p.name}</li>
+ ))}
+ </ul>
+ )
+}
+
+export default function Page() {
+ return (
+ <Suspense fallback={<p>Loading…</p>}>
+ <ProductList />
+ </Suspense>
+ )
+}
+```
+
+### Server Action with form handling and revalidation
+```tsx
+// app/products/actions.ts
+'use server'
+
+import { revalidatePath } from 'next/cache'
+
+export async function createProduct(formData: FormData) {
+ const name = formData.get('name') as string
+ await db.product.create({ data: { name } })
+ revalidatePath('/products')
+}
+
+// app/products/new/page.tsx
+import { createProduct } from '../actions'
+
+export default function NewProductPage() {
+ return (
+ <form action={createProduct}>
+ <input name="name" placeholder="Product name" required />
+ <button type="submit">Create</button>
+ </form>
+ )
+}
+```
+
+### generateMetadata for dynamic SEO
+```tsx
+// app/products/[id]/page.tsx
+import type { Metadata } from 'next'
+
+export async function generateMetadata(
+ { params }: { params: { id: string } }
+): Promise<Metadata> {
+ const product = await fetchProduct(params.id)
+ return {
+ title: product.name,
+ description: product.description,
+ openGraph: { title: product.name, images: [product.imageUrl] },
+ }
+}
+```
+
+## Output Templates
+
+When implementing Next.js features, provide:
+1. App structure (route organization)
+2. Layout/page components with proper data fetching
+3. Server actions if mutations needed
+4. Configuration (`next.config.js`, TypeScript)
+5. Brief explanation of rendering strategy chosen
+
+## Knowledge Reference
+
+Next.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next/image, next/font, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment
+
+[Documentation](https://jeffallan.github.io/claude-skills/skills/frontend/nextjs-developer/)
diff --git a/.claude/skills/nextjs-developer/references/app-router.md b/.claude/skills/nextjs-developer/references/app-router.md
new file mode 100644
index 0000000..e0a4f69
--- /dev/null
+++ b/.claude/skills/nextjs-developer/references/app-router.md
@@ -0,0 +1,311 @@
+# App Router Architecture
+
+## File-Based Routing
+
+```
+app/
+├── layout.tsx # Root layout (required)
+├── page.tsx # Home page (/)
+├── loading.tsx # Loading UI
+├── error.tsx # Error boundary
+├── not-found.tsx # 404 page
+├── template.tsx # Re-mounted layout
+│
+├── (marketing)/ # Route group (no URL segment)
+│ ├── layout.tsx
+│ ├── about/
+│ │ └── page.tsx # /about
+│ └── contact/
+│ └── page.tsx # /contact
+│
+├── dashboard/
+│ ├── layout.tsx # Shared dashboard layout
+│ ├── page.tsx # /dashboard
+│ ├── settings/
+│ │ └── page.tsx # /dashboard/settings
+│ └── @analytics/ # Parallel route (slot)
+│ └── page.tsx
+│
+├── blog/
+│ ├── [slug]/
+│ │ └── page.tsx # /blog/my-post (dynamic)
+│ └── [...slug]/
+│ └── page.tsx # /blog/a/b/c (catch-all)
+│
+└── api/
+ └── users/
+ └── route.ts # API route handler
+```
+
+## Root Layout (Required)
+
+```tsx
+// app/layout.tsx
+import type { Metadata } from 'next'
+import { Inter } from 'next/font/google'
+import './globals.css'
+
+const inter = Inter({ subsets: ['latin'] })
+
+export const metadata: Metadata = {
+ title: {
+ default: 'My App',
+ template: '%s | My App'
+ },
+ description: 'Next.js 14 application',
+}
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html lang="en">
+ <body className={inter.className}>
+ {children}
+ </body>
+ </html>
+ )
+}
+```
+
+## Nested Layouts
+
+```tsx
+// app/dashboard/layout.tsx
+import { Sidebar } from '@/components/sidebar'
+import { auth } from '@/lib/auth'
+import { redirect } from 'next/navigation'
+
+export default async function DashboardLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ const session = await auth()
+
+ if (!session) {
+ redirect('/login')
+ }
+
+ return (
+ <div className="flex">
+ <Sidebar />
+ <main className="flex-1">{children}</main>
+ </div>
+ )
+}
+```
+
+## Templates (Re-mount on Navigation)
+
+```tsx
+// app/template.tsx
+'use client'
+
+import { useEffect } from 'react'
+
+export default function Template({ children }: { children: React.ReactNode }) {
+ useEffect(() => {
+ // Runs on every navigation
+ console.log('Template mounted')
+ }, [])
+
+ return <div>{children}</div>
+}
+```
+
+## Loading States
+
+```tsx
+// app/dashboard/loading.tsx
+export default function Loading() {
+ return (
+ <div className="flex items-center justify-center h-screen">
+ <div className="animate-spin rounded-full h-32 w-32 border-b-2" />
+ </div>
+ )
+}
+```
+
+## Error Boundaries
+
+```tsx
+// app/error.tsx
+'use client'
+
+export default function Error({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string }
+ reset: () => void
+}) {
+ return (
+ <div>
+ <h2>Something went wrong!</h2>
+ <button onClick={() => reset()}>Try again</button>
+ </div>
+ )
+}
+```
+
+## Route Groups
+
+```tsx
+// (marketing) and (shop) share the same URL level
+app/
+├── (marketing)/
+│ ├── layout.tsx # Marketing layout
+│ └── about/
+│ └── page.tsx # /about
+└── (shop)/
+ ├── layout.tsx # Shop layout
+ └── products/
+ └── page.tsx # /products
+```
+
+## Parallel Routes
+
+```tsx
+// app/dashboard/layout.tsx
+export default function Layout({
+ children,
+ analytics,
+ team,
+}: {
+ children: React.ReactNode
+ analytics: React.ReactNode
+ team: React.ReactNode
+}) {
+ return (
+ <>
+ {children}
+ {analytics}
+ {team}
+ </>
+ )
+}
+
+// app/dashboard/@analytics/page.tsx
+export default function Analytics() {
+ return <div>Analytics Dashboard</div>
+}
+```
+
+## Intercepting Routes
+
+```tsx
+// Show modal when navigating from same app
+// but show full page on direct navigation
+
+// app/photos/[id]/page.tsx (full page)
+export default function PhotoPage({ params }: { params: { id: string } }) {
+ return <div>Photo {params.id} - Full Page</div>
+}
+
+// app/@modal/(.)photos/[id]/page.tsx (modal)
+export default function PhotoModal({ params }: { params: { id: string } }) {
+ return <div>Photo {params.id} - Modal</div>
+}
+```
+
+## Dynamic Routes
+
+```tsx
+// app/blog/[slug]/page.tsx
+export default function BlogPost({ params }: { params: { slug: string } }) {
+ return <h1>Post: {params.slug}</h1>
+}
+
+// Generate static params at build time
+export async function generateStaticParams() {
+ const posts = await fetch('https://api.example.com/posts').then(res => res.json())
+
+ return posts.map((post: { slug: string }) => ({
+ slug: post.slug,
+ }))
+}
+
+// Opt out of static generation
+export const dynamic = 'force-dynamic'
+
+// Revalidate every 60 seconds
+export const revalidate = 60
+```
+
+## Catch-All Routes
+
+```tsx
+// app/docs/[...slug]/page.tsx
+// Matches: /docs/a, /docs/a/b, /docs/a/b/c
+export default function Docs({ params }: { params: { slug: string[] } }) {
+ return <div>Docs: {params.slug.join('/')}</div>
+}
+
+// Optional catch-all: [[...slug]]
+// Also matches: /docs
+```
+
+## Route Handlers (API Routes)
+
+```tsx
+// app/api/users/route.ts
+import { NextRequest, NextResponse } from 'next/server'
+
+export async function GET(request: NextRequest) {
+ const users = await db.user.findMany()
+ return NextResponse.json(users)
+}
+
+export async function POST(request: NextRequest) {
+ const body = await request.json()
+ const user = await db.user.create({ data: body })
+ return NextResponse.json(user, { status: 201 })
+}
+
+// Dynamic routes: app/api/users/[id]/route.ts
+export async function GET(
+ request: NextRequest,
+ { params }: { params: { id: string } }
+) {
+ const user = await db.user.findUnique({ where: { id: params.id } })
+ return NextResponse.json(user)
+}
+```
+
+## Metadata API
+
+```tsx
+// app/blog/[slug]/page.tsx
+import type { Metadata } from 'next'
+
+export async function generateMetadata(
+ { params }: { params: { slug: string } }
+): Promise<Metadata> {
+ const post = await fetchPost(params.slug)
+
+ return {
+ title: post.title,
+ description: post.excerpt,
+ openGraph: {
+ title: post.title,
+ description: post.excerpt,
+ images: [{ url: post.coverImage }],
+ },
+ }
+}
+```
+
+## Quick Reference
+
+| File | Purpose | Use Case |
+|------|---------|----------|
+| `layout.tsx` | Persistent UI across routes | Shared navigation, auth wrapper |
+| `page.tsx` | Route UI | Actual page content |
+| `loading.tsx` | Loading fallback | Automatic Suspense boundary |
+| `error.tsx` | Error boundary | Handle errors gracefully |
+| `template.tsx` | Re-mounted layout | Analytics, animations |
+| `not-found.tsx` | 404 page | Custom not found UI |
+| `route.ts` | API handler | Backend API endpoints |
diff --git a/.claude/skills/nextjs-developer/references/data-fetching.md b/.claude/skills/nextjs-developer/references/data-fetching.md
new file mode 100644
index 0000000..df9ac2f
--- /dev/null
+++ b/.claude/skills/nextjs-developer/references/data-fetching.md
@@ -0,0 +1,482 @@
+# Data Fetching & Caching
+
+## Extended fetch API
+
+Next.js extends the native fetch with caching and revalidation options:
+
+```tsx
+// app/page.tsx
+async function getData() {
+ const res = await fetch('https://api.example.com/posts', {
+ cache: 'force-cache', // Default: cache forever (SSG)
+ })
+
+ if (!res.ok) {
+ throw new Error('Failed to fetch data')
+ }
+
+ return res.json()
+}
+
+export default async function Page() {
+ const data = await getData()
+ return <div>{/* render data */}</div>
+}
+```
+
+## Cache Options
+
+```tsx
+// 1. Force cache (Static Site Generation)
+fetch('https://api.example.com/data', {
+ cache: 'force-cache' // Default behavior
+})
+
+// 2. No cache (Server-Side Rendering)
+fetch('https://api.example.com/data', {
+ cache: 'no-store' // Always fetch fresh data
+})
+
+// 3. Revalidate (Incremental Static Regeneration)
+fetch('https://api.example.com/data', {
+ next: { revalidate: 3600 } // Revalidate every hour
+})
+
+// 4. Revalidate with tags
+fetch('https://api.example.com/data', {
+ next: { tags: ['posts'] }
+})
+```
+
+## Revalidation Methods
+
+### Time-based Revalidation (ISR)
+
+```tsx
+// Revalidate every 60 seconds
+async function getPosts() {
+ const res = await fetch('https://api.example.com/posts', {
+ next: { revalidate: 60 }
+ })
+ return res.json()
+}
+
+// Route segment config
+export const revalidate = 60 // seconds
+
+export default async function Page() {
+ const posts = await getPosts()
+ return <div>{/* render */}</div>
+}
+```
+
+### On-Demand Revalidation
+
+```tsx
+// app/api/revalidate/route.ts
+import { revalidatePath, revalidateTag } from 'next/cache'
+import { NextRequest } from 'next/server'
+
+export async function POST(request: NextRequest) {
+ const path = request.nextUrl.searchParams.get('path')
+
+ if (path) {
+ revalidatePath(path)
+ return Response.json({ revalidated: true, now: Date.now() })
+ }
+
+ return Response.json({ revalidated: false })
+}
+
+// Usage in Server Action
+'use server'
+
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(data: FormData) {
+ await db.post.create({ data })
+
+ // Revalidate specific path
+ revalidatePath('/posts')
+
+ // Revalidate entire layout
+ revalidatePath('/posts', 'layout')
+}
+```
+
+### Tag-based Revalidation
+
+```tsx
+// Fetch with tags
+async function getPosts() {
+ const res = await fetch('https://api.example.com/posts', {
+ next: { tags: ['posts'] }
+ })
+ return res.json()
+}
+
+async function getAuthors() {
+ const res = await fetch('https://api.example.com/authors', {
+ next: { tags: ['authors'] }
+ })
+ return res.json()
+}
+
+// Revalidate by tag
+import { revalidateTag } from 'next/cache'
+
+export async function createPost() {
+ // Revalidate all fetches tagged with 'posts'
+ revalidateTag('posts')
+}
+```
+
+## Route Segment Config
+
+```tsx
+// app/posts/page.tsx
+
+// Force dynamic rendering
+export const dynamic = 'force-dynamic' // 'auto' | 'force-dynamic' | 'error' | 'force-static'
+
+// Revalidation interval
+export const revalidate = 3600 // false | 0 | number (seconds)
+
+// Fetch cache
+export const fetchCache = 'auto' // 'auto' | 'default-cache' | 'only-cache' | 'force-cache' | 'force-no-store' | 'default-no-store' | 'only-no-store'
+
+// Runtime
+export const runtime = 'nodejs' // 'nodejs' | 'edge'
+
+// Preferred region
+export const preferredRegion = 'auto' // 'auto' | 'home' | 'edge' | string | string[]
+
+export default async function Page() {
+ return <div>Posts</div>
+}
+```
+
+## Parallel Data Fetching
+
+```tsx
+async function getUser() {
+ return fetch('https://api.example.com/user')
+}
+
+async function getPosts() {
+ return fetch('https://api.example.com/posts')
+}
+
+async function getComments() {
+ return fetch('https://api.example.com/comments')
+}
+
+export default async function Page() {
+ // Fetch in parallel with Promise.all
+ const [user, posts, comments] = await Promise.all([
+ getUser(),
+ getPosts(),
+ getComments(),
+ ])
+
+ return (
+ <div>
+ <UserInfo user={user} />
+ <Posts posts={posts} />
+ <Comments comments={comments} />
+ </div>
+ )
+}
+```
+
+## Sequential Data Fetching
+
+```tsx
+// When one fetch depends on another
+export default async function Page({ params }: { params: { id: string } }) {
+ // First fetch
+ const user = await fetch(`https://api.example.com/users/${params.id}`)
+ .then(res => res.json())
+
+ // Second fetch depends on first
+ const posts = await fetch(`https://api.example.com/users/${user.id}/posts`)
+ .then(res => res.json())
+
+ return (
+ <div>
+ <h1>{user.name}</h1>
+ <Posts posts={posts} />
+ </div>
+ )
+}
+```
+
+## Streaming with Suspense
+
+```tsx
+// app/page.tsx
+import { Suspense } from 'react'
+
+async function Posts() {
+ const posts = await fetch('https://api.example.com/posts', {
+ cache: 'no-store'
+ }).then(res => res.json())
+
+ return (
+ <ul>
+ {posts.map((post: Post) => (
+ <li key={post.id}>{post.title}</li>
+ ))}
+ </ul>
+ )
+}
+
+export default function Page() {
+ return (
+ <div>
+ <h1>Posts</h1>
+ <Suspense fallback={<div>Loading posts...</div>}>
+ <Posts />
+ </Suspense>
+ </div>
+ )
+}
+```
+
+## React cache for Deduplication
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const getUser = cache(async (id: string) => {
+ const res = await fetch(`https://api.example.com/users/${id}`)
+ return res.json()
+})
+
+// components/user-profile.tsx
+export async function UserProfile({ userId }: { userId: string }) {
+ const user = await getUser(userId) // Cached
+ return <div>{user.name}</div>
+}
+
+// components/user-posts.tsx
+export async function UserPosts({ userId }: { userId: string }) {
+ const user = await getUser(userId) // Uses cached result
+ return <div>{user.posts.length} posts</div>
+}
+
+// app/page.tsx
+export default function Page() {
+ return (
+ <>
+ <UserProfile userId="123" />
+ <UserPosts userId="123" /> {/* Same fetch, deduplicated */}
+ </>
+ )
+}
+```
+
+## Database Queries
+
+```tsx
+// lib/db.ts
+import { PrismaClient } from '@prisma/client'
+
+const globalForPrisma = global as unknown as { prisma: PrismaClient }
+
+export const db = globalForPrisma.prisma || new PrismaClient()
+
+if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = db
+
+// app/posts/page.tsx
+import { db } from '@/lib/db'
+
+export const revalidate = 60 // Revalidate every 60 seconds
+
+export default async function PostsPage() {
+ const posts = await db.post.findMany({
+ include: { author: true },
+ orderBy: { createdAt: 'desc' },
+ })
+
+ return (
+ <div>
+ {posts.map(post => (
+ <article key={post.id}>
+ <h2>{post.title}</h2>
+ <p>By {post.author.name}</p>
+ </article>
+ ))}
+ </div>
+ )
+}
+```
+
+## Error Handling
+
+```tsx
+async function getData() {
+ const res = await fetch('https://api.example.com/data')
+
+ if (!res.ok) {
+ // This will activate the closest error.tsx
+ throw new Error('Failed to fetch data')
+ }
+
+ return res.json()
+}
+
+export default async function Page() {
+ const data = await getData()
+ return <div>{data.title}</div>
+}
+
+// app/error.tsx
+'use client'
+
+export default function Error({
+ error,
+ reset,
+}: {
+ error: Error & { digest?: string }
+ reset: () => void
+}) {
+ return (
+ <div>
+ <h2>Something went wrong!</h2>
+ <button onClick={() => reset()}>Try again</button>
+ </div>
+ )
+}
+```
+
+## Loading States
+
+```tsx
+// app/posts/loading.tsx
+export default function Loading() {
+ return <div>Loading posts...</div>
+}
+
+// app/posts/page.tsx
+export default async function PostsPage() {
+ const posts = await fetch('https://api.example.com/posts')
+ .then(res => res.json())
+
+ return <div>{/* render posts */}</div>
+}
+```
+
+## Client-Side Data Fetching
+
+```tsx
+// When you need client-side fetching
+'use client'
+
+import useSWR from 'swr'
+
+const fetcher = (url: string) => fetch(url).then(res => res.json())
+
+export function Posts() {
+ const { data, error, isLoading } = useSWR('/api/posts', fetcher, {
+ refreshInterval: 3000, // Refresh every 3 seconds
+ })
+
+ if (error) return <div>Failed to load</div>
+ if (isLoading) return <div>Loading...</div>
+
+ return (
+ <ul>
+ {data.map((post: Post) => (
+ <li key={post.id}>{post.title}</li>
+ ))}
+ </ul>
+ )
+}
+```
+
+## Preloading Data
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const preload = (id: string) => {
+ void getUser(id) // Trigger fetch without awaiting
+}
+
+export const getUser = cache(async (id: string) => {
+ return fetch(`https://api.example.com/users/${id}`)
+ .then(res => res.json())
+})
+
+// components/user.tsx
+import { getUser, preload } from '@/lib/data'
+
+export async function User({ id }: { id: string }) {
+ const user = await getUser(id)
+ return <div>{user.name}</div>
+}
+
+// app/page.tsx
+import { User } from '@/components/user'
+import { preload } from '@/lib/data'
+
+export default async function Page() {
+ preload('123') // Start loading immediately
+ return <User id="123" />
+}
+```
+
+## Static Generation with Dynamic Routes
+
+```tsx
+// app/posts/[slug]/page.tsx
+type Post = {
+ slug: string
+ title: string
+ content: string
+}
+
+export async function generateStaticParams() {
+ const posts = await fetch('https://api.example.com/posts')
+ .then(res => res.json())
+
+ return posts.map((post: Post) => ({
+ slug: post.slug,
+ }))
+}
+
+export default async function Post({ params }: { params: { slug: string } }) {
+ const post = await fetch(`https://api.example.com/posts/${params.slug}`)
+ .then(res => res.json())
+
+ return (
+ <article>
+ <h1>{post.title}</h1>
+ <div>{post.content}</div>
+ </article>
+ )
+}
+```
+
+## Quick Reference
+
+| Strategy | Config | Use Case |
+|----------|--------|----------|
+| **SSG** | `cache: 'force-cache'` | Static content |
+| **SSR** | `cache: 'no-store'` | Always fresh data |
+| **ISR** | `next: { revalidate: 60 }` | Periodic updates |
+| **Tag-based** | `next: { tags: ['posts'] }` | On-demand revalidation |
+| **Dynamic** | `export const dynamic = 'force-dynamic'` | Per-request data |
+
+## Best Practices
+
+1. **Default to caching** - Use force-cache for static content
+2. **Use ISR** - Revalidate periodically for semi-dynamic content
+3. **Parallel fetching** - Use Promise.all for independent requests
+4. **Deduplicate** - Use React cache() for repeated calls
+5. **Stream with Suspense** - Show content progressively
+6. **Tag your fetches** - Enable granular revalidation
+7. **Handle errors** - Use error.tsx for graceful degradation
diff --git a/.claude/skills/nextjs-developer/references/deployment.md b/.claude/skills/nextjs-developer/references/deployment.md
new file mode 100644
index 0000000..9bad909
--- /dev/null
+++ b/.claude/skills/nextjs-developer/references/deployment.md
@@ -0,0 +1,545 @@
+# Deployment & Production
+
+## Vercel Deployment (Recommended)
+
+### Quick Deploy
+
+```bash
+# Install Vercel CLI
+npm i -g vercel
+
+# Deploy
+vercel
+
+# Production deployment
+vercel --prod
+```
+
+### vercel.json Configuration
+
+```json
+{
+ "buildCommand": "next build",
+ "devCommand": "next dev",
+ "installCommand": "npm install",
+ "framework": "nextjs",
+ "regions": ["iad1"],
+ "env": {
+ "DATABASE_URL": "@database-url",
+ "NEXT_PUBLIC_API_URL": "https://api.example.com"
+ },
+ "headers": [
+ {
+ "source": "/api/(.*)",
+ "headers": [
+ { "key": "Access-Control-Allow-Origin", "value": "*" },
+ { "key": "Access-Control-Allow-Methods", "value": "GET,POST,PUT,DELETE" }
+ ]
+ }
+ ],
+ "redirects": [
+ {
+ "source": "/old-blog/:slug",
+ "destination": "/blog/:slug",
+ "permanent": true
+ }
+ ],
+ "rewrites": [
+ {
+ "source": "/api/:path*",
+ "destination": "https://api.example.com/:path*"
+ }
+ ]
+}
+```
+
+### Environment Variables
+
+```bash
+# .env.local (not committed)
+DATABASE_URL="postgresql://user:pass@localhost:5432/db"
+NEXTAUTH_SECRET="your-secret"
+
+# .env.production (committed, public vars only)
+NEXT_PUBLIC_API_URL="https://api.example.com"
+```
+
+```tsx
+// Access in Server Components
+const dbUrl = process.env.DATABASE_URL
+
+// Access in Client Components (must be prefixed with NEXT_PUBLIC_)
+const apiUrl = process.env.NEXT_PUBLIC_API_URL
+```
+
+## Self-Hosting
+
+### Standalone Output
+
+```js
+// next.config.js
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+ output: 'standalone',
+}
+
+module.exports = nextConfig
+```
+
+```bash
+# Build
+npm run build
+
+# The standalone folder contains everything needed
+# Copy these to your server:
+# - .next/standalone/
+# - .next/static/
+# - public/
+
+# Run on server
+node .next/standalone/server.js
+```
+
+### Node.js Server
+
+```bash
+# Build
+npm run build
+
+# Start production server
+npm start
+
+# With PM2 for process management
+pm2 start npm --name "nextjs" -- start
+pm2 startup
+pm2 save
+```
+
+## Docker Deployment
+
+### Dockerfile (Multi-stage)
+
+```dockerfile
+# Stage 1: Dependencies
+FROM node:20-alpine AS deps
+RUN apk add --no-cache libc6-compat
+WORKDIR /app
+
+COPY package.json package-lock.json ./
+RUN npm ci
+
+# Stage 2: Builder
+FROM node:20-alpine AS builder
+WORKDIR /app
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+
+ENV NEXT_TELEMETRY_DISABLED 1
+
+RUN npm run build
+
+# Stage 3: Runner
+FROM node:20-alpine AS runner
+WORKDIR /app
+
+ENV NODE_ENV production
+ENV NEXT_TELEMETRY_DISABLED 1
+
+RUN addgroup --system --gid 1001 nodejs
+RUN adduser --system --uid 1001 nextjs
+
+COPY --from=builder /app/public ./public
+COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
+COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
+
+USER nextjs
+
+EXPOSE 3000
+
+ENV PORT 3000
+ENV HOSTNAME "0.0.0.0"
+
+CMD ["node", "server.js"]
+```
+
+### docker-compose.yml
+
+```yaml
+version: '3.8'
+
+services:
+ nextjs:
+ build:
+ context: .
+ dockerfile: Dockerfile
+ ports:
+ - "3000:3000"
+ environment:
+ - DATABASE_URL=postgresql://postgres:postgres@db:5432/myapp
+ - NEXTAUTH_URL=http://localhost:3000
+ - NEXTAUTH_SECRET=your-secret
+ depends_on:
+ - db
+ restart: unless-stopped
+
+ db:
+ image: postgres:16-alpine
+ environment:
+ - POSTGRES_USER=postgres
+ - POSTGRES_PASSWORD=postgres
+ - POSTGRES_DB=myapp
+ volumes:
+ - postgres_data:/var/lib/postgresql/data
+ restart: unless-stopped
+
+volumes:
+ postgres_data:
+```
+
+```bash
+# Build and run
+docker-compose up -d
+
+# View logs
+docker-compose logs -f nextjs
+
+# Rebuild
+docker-compose up -d --build
+```
+
+## Production Optimization
+
+### next.config.js
+
+```js
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+ // Standalone for self-hosting
+ output: 'standalone',
+
+ // Image optimization
+ images: {
+ formats: ['image/avif', 'image/webp'],
+ remotePatterns: [
+ {
+ protocol: 'https',
+ hostname: 'cdn.example.com',
+ pathname: '/images/**',
+ },
+ ],
+ deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
+ imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
+ },
+
+ // Compression
+ compress: true,
+
+ // Security headers
+ async headers() {
+ return [
+ {
+ source: '/:path*',
+ headers: [
+ {
+ key: 'X-DNS-Prefetch-Control',
+ value: 'on'
+ },
+ {
+ key: 'Strict-Transport-Security',
+ value: 'max-age=63072000; includeSubDomains; preload'
+ },
+ {
+ key: 'X-Frame-Options',
+ value: 'SAMEORIGIN'
+ },
+ {
+ key: 'X-Content-Type-Options',
+ value: 'nosniff'
+ },
+ {
+ key: 'X-XSS-Protection',
+ value: '1; mode=block'
+ },
+ {
+ key: 'Referrer-Policy',
+ value: 'origin-when-cross-origin'
+ },
+ ],
+ },
+ ]
+ },
+
+ // Experimental features
+ experimental: {
+ optimizePackageImports: ['@mui/material', 'lodash'],
+ },
+
+ // Bundle analyzer
+ webpack: (config, { isServer }) => {
+ if (process.env.ANALYZE === 'true') {
+ const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
+ config.plugins.push(
+ new BundleAnalyzerPlugin({
+ analyzerMode: 'static',
+ reportFilename: isServer
+ ? '../analyze/server.html'
+ : './analyze/client.html',
+ })
+ )
+ }
+ return config
+ },
+}
+
+module.exports = nextConfig
+```
+
+### Bundle Analysis
+
+```bash
+# Install analyzer
+npm install -D @next/bundle-analyzer
+
+# Analyze
+ANALYZE=true npm run build
+
+# Or use built-in
+npm run build -- --experimental-build-mode=compile
+```
+
+### Performance Monitoring
+
+```tsx
+// app/layout.tsx
+import { SpeedInsights } from '@vercel/speed-insights/next'
+import { Analytics } from '@vercel/analytics/react'
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html>
+ <body>
+ {children}
+ <SpeedInsights />
+ <Analytics />
+ </body>
+ </html>
+ )
+}
+```
+
+## CDN & Edge
+
+### Static Asset CDN
+
+```js
+// next.config.js
+const nextConfig = {
+ assetPrefix: process.env.NODE_ENV === 'production'
+ ? 'https://cdn.example.com'
+ : '',
+}
+```
+
+### Edge Runtime
+
+```tsx
+// app/api/edge/route.ts
+export const runtime = 'edge'
+
+export async function GET(request: Request) {
+ return new Response('Hello from Edge!', {
+ status: 200,
+ headers: {
+ 'content-type': 'text/plain',
+ },
+ })
+}
+
+// app/page.tsx
+export const runtime = 'edge'
+
+export default async function Page() {
+ return <div>Edge-rendered page</div>
+}
+```
+
+## Caching Strategy
+
+### ISR (Incremental Static Regeneration)
+
+```tsx
+// app/blog/[slug]/page.tsx
+export const revalidate = 3600 // Revalidate every hour
+
+export default async function BlogPost({ params }: { params: { slug: string } }) {
+ const post = await fetchPost(params.slug)
+ return <article>{post.content}</article>
+}
+```
+
+### On-Demand Revalidation
+
+```tsx
+// app/api/revalidate/route.ts
+import { revalidatePath } from 'next/cache'
+import { NextRequest } from 'next/server'
+
+export async function POST(request: NextRequest) {
+ const secret = request.nextUrl.searchParams.get('secret')
+
+ if (secret !== process.env.REVALIDATE_SECRET) {
+ return Response.json({ message: 'Invalid secret' }, { status: 401 })
+ }
+
+ const path = request.nextUrl.searchParams.get('path') || '/'
+
+ revalidatePath(path)
+
+ return Response.json({ revalidated: true, now: Date.now() })
+}
+```
+
+## Database Connection Pooling
+
+```ts
+// lib/db.ts
+import { PrismaClient } from '@prisma/client'
+
+const globalForPrisma = global as unknown as {
+ prisma: PrismaClient | undefined
+}
+
+export const db =
+ globalForPrisma.prisma ??
+ new PrismaClient({
+ log: process.env.NODE_ENV === 'development' ? ['query', 'error', 'warn'] : ['error'],
+ })
+
+if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = db
+```
+
+## Health Check Endpoint
+
+```tsx
+// app/api/health/route.ts
+import { db } from '@/lib/db'
+
+export async function GET() {
+ try {
+ // Check database connection
+ await db.$queryRaw`SELECT 1`
+
+ return Response.json({
+ status: 'ok',
+ timestamp: new Date().toISOString(),
+ uptime: process.uptime(),
+ })
+ } catch (error) {
+ return Response.json(
+ {
+ status: 'error',
+ message: 'Database connection failed',
+ },
+ { status: 503 }
+ )
+ }
+}
+```
+
+## CI/CD with GitHub Actions
+
+```yaml
+# .github/workflows/deploy.yml
+name: Deploy to Production
+
+on:
+ push:
+ branches: [main]
+
+jobs:
+ deploy:
+ runs-on: ubuntu-latest
+
+ steps:
+ - uses: actions/checkout@v3
+
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
+ with:
+ node-version: '20'
+ cache: 'npm'
+
+ - name: Install dependencies
+ run: npm ci
+
+ - name: Run tests
+ run: npm test
+
+ - name: Build
+ run: npm run build
+ env:
+ DATABASE_URL: ${{ secrets.DATABASE_URL }}
+ NEXTAUTH_SECRET: ${{ secrets.NEXTAUTH_SECRET }}
+
+ - name: Deploy to Vercel
+ uses: amondnet/vercel-action@v25
+ with:
+ vercel-token: ${{ secrets.VERCEL_TOKEN }}
+ vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
+ vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
+ vercel-args: '--prod'
+```
+
+## Monitoring & Logging
+
+```tsx
+// app/error.tsx
+'use client'
+
+import * as Sentry from '@sentry/nextjs'
+import { useEffect } from 'react'
+
+export default function Error({
+ error,
+}: {
+ error: Error & { digest?: string }
+}) {
+ useEffect(() => {
+ Sentry.captureException(error)
+ }, [error])
+
+ return <div>Something went wrong!</div>
+}
+```
+
+## Quick Reference
+
+| Platform | Best For | Effort |
+|----------|----------|--------|
+| **Vercel** | Zero-config, optimal performance | Low |
+| **Netlify** | Alternative to Vercel | Low |
+| **Railway** | Simple hosting with databases | Medium |
+| **AWS/GCP** | Enterprise, custom needs | High |
+| **Docker** | Self-hosting, full control | High |
+
+## Production Checklist
+
+- [ ] Enable TypeScript strict mode
+- [ ] Configure CSP headers
+- [ ] Setup error monitoring (Sentry)
+- [ ] Configure analytics (Vercel/GA)
+- [ ] Optimize images (next/image)
+- [ ] Enable compression
+- [ ] Setup CDN for static assets
+- [ ] Configure database connection pooling
+- [ ] Add health check endpoint
+- [ ] Setup CI/CD pipeline
+- [ ] Configure environment variables
+- [ ] Enable ISR/SSG where possible
+- [ ] Test Core Web Vitals
+- [ ] Setup logging (Datadog/LogRocket)
+- [ ] Configure backup strategy
diff --git a/.claude/skills/nextjs-developer/references/server-actions.md b/.claude/skills/nextjs-developer/references/server-actions.md
new file mode 100644
index 0000000..6d1f08a
--- /dev/null
+++ b/.claude/skills/nextjs-developer/references/server-actions.md
@@ -0,0 +1,462 @@
+# Server Actions
+
+## Basic Server Action
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { db } from '@/lib/db'
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(formData: FormData) {
+ const title = formData.get('title') as string
+ const content = formData.get('content') as string
+
+ await db.post.create({
+ data: { title, content }
+ })
+
+ revalidatePath('/posts')
+}
+```
+
+## Form with Server Action
+
+```tsx
+// app/posts/new/page.tsx
+import { createPost } from '@/app/actions'
+
+export default function NewPost() {
+ return (
+ <form action={createPost}>
+ <input name="title" required />
+ <textarea name="content" required />
+ <button type="submit">Create Post</button>
+ </form>
+ )
+}
+```
+
+## Server Action with Validation
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { z } from 'zod'
+import { revalidatePath } from 'next/cache'
+
+const CreatePostSchema = z.object({
+ title: z.string().min(3).max(100),
+ content: z.string().min(10),
+})
+
+export async function createPost(formData: FormData) {
+ const validatedFields = CreatePostSchema.safeParse({
+ title: formData.get('title'),
+ content: formData.get('content'),
+ })
+
+ if (!validatedFields.success) {
+ return {
+ errors: validatedFields.error.flatten().fieldErrors,
+ }
+ }
+
+ const { title, content } = validatedFields.data
+
+ await db.post.create({
+ data: { title, content }
+ })
+
+ revalidatePath('/posts')
+ return { success: true }
+}
+```
+
+## Client Component with Server Action
+
+```tsx
+// components/create-post-form.tsx
+'use client'
+
+import { createPost } from '@/app/actions'
+import { useFormState, useFormStatus } from 'react-dom'
+
+const initialState = {
+ errors: {},
+}
+
+function SubmitButton() {
+ const { pending } = useFormStatus()
+
+ return (
+ <button type="submit" disabled={pending}>
+ {pending ? 'Creating...' : 'Create Post'}
+ </button>
+ )
+}
+
+export function CreatePostForm() {
+ const [state, formAction] = useFormState(createPost, initialState)
+
+ return (
+ <form action={formAction}>
+ <div>
+ <input name="title" />
+ {state.errors?.title && <p>{state.errors.title[0]}</p>}
+ </div>
+
+ <div>
+ <textarea name="content" />
+ {state.errors?.content && <p>{state.errors.content[0]}</p>}
+ </div>
+
+ <SubmitButton />
+ </form>
+ )
+}
+```
+
+## Server Action with Redirect
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { redirect } from 'next/navigation'
+import { revalidatePath } from 'next/cache'
+
+export async function createPost(formData: FormData) {
+ const post = await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ }
+ })
+
+ revalidatePath('/posts')
+ redirect(`/posts/${post.id}`)
+}
+```
+
+## Optimistic Updates
+
+```tsx
+// components/todo-list.tsx
+'use client'
+
+import { experimental_useOptimistic as useOptimistic } from 'react'
+import { toggleTodo } from '@/app/actions'
+
+export function TodoList({ todos }: { todos: Todo[] }) {
+ const [optimisticTodos, addOptimisticTodo] = useOptimistic(
+ todos,
+ (state, newTodo: Todo) => [...state, newTodo]
+ )
+
+ async function handleSubmit(formData: FormData) {
+ const title = formData.get('title') as string
+ const newTodo = { id: crypto.randomUUID(), title, completed: false }
+
+ // Optimistically update UI
+ addOptimisticTodo(newTodo)
+
+ // Send to server
+ await createTodo(formData)
+ }
+
+ return (
+ <div>
+ <ul>
+ {optimisticTodos.map(todo => (
+ <li key={todo.id}>{todo.title}</li>
+ ))}
+ </ul>
+
+ <form action={handleSubmit}>
+ <input name="title" />
+ <button type="submit">Add</button>
+ </form>
+ </div>
+ )
+}
+```
+
+## Server Action with Authentication
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { auth } from '@/lib/auth'
+import { redirect } from 'next/navigation'
+
+export async function createPost(formData: FormData) {
+ const session = await auth()
+
+ if (!session) {
+ redirect('/login')
+ }
+
+ await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ authorId: session.user.id,
+ }
+ })
+
+ revalidatePath('/posts')
+}
+```
+
+## Inline Server Action
+
+```tsx
+// app/posts/page.tsx
+import { db } from '@/lib/db'
+import { revalidatePath } from 'next/cache'
+
+export default async function Posts() {
+ const posts = await db.post.findMany()
+
+ async function deletePost(formData: FormData) {
+ 'use server'
+
+ const id = formData.get('id') as string
+ await db.post.delete({ where: { id } })
+ revalidatePath('/posts')
+ }
+
+ return (
+ <ul>
+ {posts.map(post => (
+ <li key={post.id}>
+ {post.title}
+ <form action={deletePost}>
+ <input type="hidden" name="id" value={post.id} />
+ <button type="submit">Delete</button>
+ </form>
+ </li>
+ ))}
+ </ul>
+ )
+}
+```
+
+## Programmatic Server Action Call
+
+```tsx
+// components/delete-button.tsx
+'use client'
+
+import { deletePost } from '@/app/actions'
+
+export function DeleteButton({ postId }: { postId: string }) {
+ async function handleDelete() {
+ if (confirm('Are you sure?')) {
+ await deletePost(postId)
+ }
+ }
+
+ return (
+ <button onClick={handleDelete}>
+ Delete
+ </button>
+ )
+}
+
+// app/actions.ts
+'use server'
+
+export async function deletePost(postId: string) {
+ await db.post.delete({ where: { id: postId } })
+ revalidatePath('/posts')
+}
+```
+
+## Revalidation Strategies
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { revalidatePath, revalidateTag } from 'next/cache'
+
+export async function updatePost(id: string, data: UpdatePostData) {
+ await db.post.update({ where: { id }, data })
+
+ // Revalidate specific path
+ revalidatePath('/posts')
+ revalidatePath(`/posts/${id}`)
+
+ // Revalidate all paths in a layout
+ revalidatePath('/posts', 'layout')
+
+ // Revalidate by cache tag
+ revalidateTag('posts')
+}
+```
+
+## Server Action with File Upload
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { writeFile } from 'fs/promises'
+import { join } from 'path'
+
+export async function uploadAvatar(formData: FormData) {
+ const file = formData.get('avatar') as File
+
+ if (!file) {
+ return { error: 'No file uploaded' }
+ }
+
+ const bytes = await file.arrayBuffer()
+ const buffer = Buffer.from(bytes)
+
+ const path = join(process.cwd(), 'public', 'uploads', file.name)
+ await writeFile(path, buffer)
+
+ return { success: true, path: `/uploads/${file.name}` }
+}
+
+// components/upload-form.tsx
+'use client'
+
+import { uploadAvatar } from '@/app/actions'
+
+export function UploadForm() {
+ async function handleSubmit(formData: FormData) {
+ const result = await uploadAvatar(formData)
+ if (result.success) {
+ console.log('Uploaded to:', result.path)
+ }
+ }
+
+ return (
+ <form action={handleSubmit}>
+ <input type="file" name="avatar" accept="image/*" />
+ <button type="submit">Upload</button>
+ </form>
+ )
+}
+```
+
+## Error Handling
+
+```tsx
+// app/actions.ts
+'use server'
+
+export async function createPost(formData: FormData) {
+ try {
+ await db.post.create({
+ data: {
+ title: formData.get('title') as string,
+ content: formData.get('content') as string,
+ }
+ })
+
+ revalidatePath('/posts')
+ return { success: true }
+ } catch (error) {
+ console.error('Failed to create post:', error)
+ return { error: 'Failed to create post' }
+ }
+}
+
+// components/form.tsx
+'use client'
+
+export function CreatePostForm() {
+ const [error, setError] = useState<string | null>(null)
+
+ async function handleSubmit(formData: FormData) {
+ const result = await createPost(formData)
+
+ if (result.error) {
+ setError(result.error)
+ } else {
+ // Success
+ router.push('/posts')
+ }
+ }
+
+ return (
+ <form action={handleSubmit}>
+ {error && <div className="error">{error}</div>}
+ {/* form fields */}
+ </form>
+ )
+}
+```
+
+## Server Action with Cookies
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { cookies } from 'next/headers'
+
+export async function setTheme(theme: 'light' | 'dark') {
+ cookies().set('theme', theme, {
+ httpOnly: true,
+ secure: process.env.NODE_ENV === 'production',
+ maxAge: 60 * 60 * 24 * 365, // 1 year
+ path: '/',
+ })
+}
+
+export async function getTheme() {
+ return cookies().get('theme')?.value ?? 'light'
+}
+```
+
+## Rate Limiting
+
+```tsx
+// app/actions.ts
+'use server'
+
+import { ratelimit } from '@/lib/redis'
+
+export async function createPost(formData: FormData) {
+ const session = await auth()
+ const { success } = await ratelimit.limit(session.user.id)
+
+ if (!success) {
+ return { error: 'Rate limit exceeded' }
+ }
+
+ // Create post...
+}
+```
+
+## Quick Reference
+
+| Capability | Usage |
+|------------|-------|
+| **Define** | Add 'use server' at top of file or function |
+| **Form** | Pass action to `<form action={serverAction}>` |
+| **Programmatic** | Call directly: `await serverAction(data)` |
+| **Validation** | Use Zod/TypeBox before mutations |
+| **Revalidate** | `revalidatePath()` or `revalidateTag()` |
+| **Redirect** | `redirect()` after mutation |
+| **Errors** | Return error objects, handle in client |
+| **Files** | Access via `formData.get()` as File |
+
+## Best Practices
+
+1. **Always validate** - Use Zod/TypeBox for type-safe validation
+2. **Revalidate** - Call revalidatePath() after mutations
+3. **Handle errors** - Return error objects instead of throwing
+4. **Auth checks** - Verify session before mutations
+5. **Rate limiting** - Protect against abuse
+6. **Type safety** - Define input/output types
+7. **Optimistic updates** - Use useOptimistic for better UX
diff --git a/.claude/skills/nextjs-developer/references/server-components.md b/.claude/skills/nextjs-developer/references/server-components.md
new file mode 100644
index 0000000..7d681a1
--- /dev/null
+++ b/.claude/skills/nextjs-developer/references/server-components.md
@@ -0,0 +1,384 @@
+# React Server Components
+
+## Server Components (Default)
+
+```tsx
+// app/page.tsx - Server Component by default
+import { db } from '@/lib/db'
+
+export default async function Page() {
+ // Data fetching in Server Component
+ const users = await db.user.findMany()
+
+ return (
+ <div>
+ <h1>Users</h1>
+ <ul>
+ {users.map(user => (
+ <li key={user.id}>{user.name}</li>
+ ))}
+ </ul>
+ </div>
+ )
+}
+```
+
+## Benefits of Server Components
+
+- **Zero bundle size** - Server Components don't add JavaScript to client bundle
+- **Direct backend access** - Query databases, read files, use secrets
+- **Automatic code splitting** - Only Client Components add to bundle
+- **Streaming** - Send UI progressively as data loads
+- **No client-side waterfalls** - Fetch all data in parallel on server
+
+## Client Components
+
+```tsx
+// components/counter.tsx
+'use client' // Required directive
+
+import { useState } from 'react'
+
+export function Counter() {
+ const [count, setCount] = useState(0)
+
+ return (
+ <button onClick={() => setCount(count + 1)}>
+ Count: {count}
+ </button>
+ )
+}
+```
+
+## When to Use Client Components
+
+Use `'use client'` when you need:
+- **Interactivity** - onClick, onChange, event handlers
+- **State** - useState, useReducer
+- **Effects** - useEffect, useLayoutEffect
+- **Browser APIs** - localStorage, window, document
+- **Custom hooks** - Any hook using client-only features
+- **Class components** - Component lifecycle methods
+
+## Composition Pattern
+
+```tsx
+// app/page.tsx - Server Component
+import { ClientWrapper } from './client-wrapper'
+import { db } from '@/lib/db'
+
+export default async function Page() {
+ const data = await db.query()
+
+ return (
+ <div>
+ {/* Server Component content */}
+ <h1>Server Content</h1>
+
+ {/* Pass data to Client Component */}
+ <ClientWrapper initialData={data}>
+ {/* Server Component as children */}
+ <ServerSidebar />
+ </ClientWrapper>
+ </div>
+ )
+}
+
+// components/client-wrapper.tsx
+'use client'
+
+export function ClientWrapper({
+ children,
+ initialData,
+}: {
+ children: React.ReactNode
+ initialData: Data
+}) {
+ const [data, setData] = useState(initialData)
+
+ return (
+ <div>
+ {/* Client Component UI */}
+ <button onClick={() => refresh()}>Refresh</button>
+ {/* Server Component children */}
+ {children}
+ </div>
+ )
+}
+```
+
+## Streaming with Suspense
+
+```tsx
+// app/page.tsx
+import { Suspense } from 'react'
+import { SlowComponent } from './slow-component'
+import { FastComponent } from './fast-component'
+
+export default function Page() {
+ return (
+ <div>
+ {/* Renders immediately */}
+ <FastComponent />
+
+ {/* Shows fallback while loading */}
+ <Suspense fallback={<div>Loading...</div>}>
+ <SlowComponent />
+ </Suspense>
+ </div>
+ )
+}
+
+// components/slow-component.tsx
+async function getData() {
+ await new Promise(resolve => setTimeout(resolve, 3000))
+ return { data: 'Loaded!' }
+}
+
+export async function SlowComponent() {
+ const data = await getData()
+ return <div>{data.data}</div>
+}
+```
+
+## Parallel Data Fetching
+
+```tsx
+// app/dashboard/page.tsx
+async function getUser() {
+ return fetch('https://api.example.com/user')
+}
+
+async function getPosts() {
+ return fetch('https://api.example.com/posts')
+}
+
+export default async function Dashboard() {
+ // Fetch in parallel
+ const [user, posts] = await Promise.all([
+ getUser(),
+ getPosts(),
+ ])
+
+ return (
+ <div>
+ <UserProfile user={user} />
+ <PostsList posts={posts} />
+ </div>
+ )
+}
+```
+
+## Sequential Data Fetching
+
+```tsx
+// app/artist/[id]/page.tsx
+async function getArtist(id: string) {
+ return fetch(`https://api.example.com/artists/${id}`)
+}
+
+async function getAlbums(artistId: string) {
+ return fetch(`https://api.example.com/artists/${artistId}/albums`)
+}
+
+export default async function ArtistPage({ params }: { params: { id: string } }) {
+ // Sequential: albums depends on artist
+ const artist = await getArtist(params.id)
+ const albums = await getAlbums(artist.id)
+
+ return (
+ <div>
+ <h1>{artist.name}</h1>
+ <Albums albums={albums} />
+ </div>
+ )
+}
+```
+
+## Preloading Data
+
+```tsx
+// lib/data.ts
+import { cache } from 'react'
+
+export const getUser = cache(async (id: string) => {
+ return db.user.findUnique({ where: { id } })
+})
+
+// components/user-profile.tsx
+export async function UserProfile({ userId }: { userId: string }) {
+ const user = await getUser(userId)
+ return <div>{user.name}</div>
+}
+
+// app/page.tsx
+import { getUser } from '@/lib/data'
+import { UserProfile } from '@/components/user-profile'
+
+export default async function Page() {
+ // Preload
+ getUser('123')
+
+ return (
+ <div>
+ {/* This will use cached result */}
+ <UserProfile userId="123" />
+ </div>
+ )
+}
+```
+
+## Server Component Patterns
+
+### Pattern: Layout with Data Fetching
+
+```tsx
+// app/dashboard/layout.tsx
+import { auth } from '@/lib/auth'
+import { db } from '@/lib/db'
+
+export default async function DashboardLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ const session = await auth()
+ const user = await db.user.findUnique({ where: { id: session.userId } })
+
+ return (
+ <div>
+ <Sidebar user={user} />
+ <main>{children}</main>
+ </div>
+ )
+}
+```
+
+### Pattern: Conditional Client Components
+
+```tsx
+// app/page.tsx
+import { ClientComponent } from './client-component'
+
+export default async function Page() {
+ const data = await fetchData()
+
+ // Only render Client Component when needed
+ if (data.requiresInteractivity) {
+ return <ClientComponent data={data} />
+ }
+
+ return <div>{data.content}</div>
+}
+```
+
+### Pattern: Server Component with Client Island
+
+```tsx
+// app/blog/[slug]/page.tsx
+import { LikeButton } from './like-button'
+
+export default async function BlogPost({ params }: { params: { slug: string } }) {
+ const post = await getPost(params.slug)
+
+ return (
+ <article>
+ {/* Server-rendered content */}
+ <h1>{post.title}</h1>
+ <div dangerouslySetInnerHTML={{ __html: post.content }} />
+
+ {/* Client island for interactivity */}
+ <LikeButton postId={post.id} initialLikes={post.likes} />
+ </article>
+ )
+}
+```
+
+## Context in Server/Client Components
+
+```tsx
+// app/providers.tsx
+'use client'
+
+import { ThemeProvider } from 'next-themes'
+
+export function Providers({ children }: { children: React.ReactNode }) {
+ return <ThemeProvider>{children}</ThemeProvider>
+}
+
+// app/layout.tsx
+import { Providers } from './providers'
+
+export default function RootLayout({
+ children,
+}: {
+ children: React.ReactNode
+}) {
+ return (
+ <html>
+ <body>
+ <Providers>{children}</Providers>
+ </body>
+ </html>
+ )
+}
+```
+
+## Third-Party Components
+
+```tsx
+// components/carousel-wrapper.tsx
+'use client'
+
+import { Carousel } from 'third-party-carousel'
+
+export function CarouselWrapper({ items }: { items: Item[] }) {
+ return <Carousel items={items} />
+}
+
+// app/page.tsx
+import { CarouselWrapper } from '@/components/carousel-wrapper'
+
+export default async function Page() {
+ const items = await fetchItems()
+ return <CarouselWrapper items={items} />
+}
+```
+
+## Edge Runtime
+
+```tsx
+// app/api/route.ts
+export const runtime = 'edge'
+
+export async function GET() {
+ return new Response('Hello from Edge!')
+}
+
+// app/page.tsx
+export const runtime = 'edge'
+
+export default async function Page() {
+ return <div>Edge-rendered page</div>
+}
+```
+
+## Quick Reference
+
+| Capability | Server Component | Client Component |
+|------------|------------------|------------------|
+| Data fetching | ✅ Yes | ⚠️ Use SWR/React Query |
+| Backend access | ✅ Yes (DB, files) | ❌ No |
+| Event handlers | ❌ No | ✅ Yes |
+| State/Effects | ❌ No | ✅ Yes |
+| Browser APIs | ❌ No | ✅ Yes |
+| Bundle size | 0 KB | Adds to bundle |
+| Streaming | ✅ Yes | ❌ No |
+
+## Best Practices
+
+1. **Default to Server Components** - Only use 'use client' when needed
+2. **Move Client Components down** - Push them to leaves of component tree
+3. **Pass data down** - Fetch in Server Components, pass to Client Components
+4. **Use composition** - Nest Server Components inside Client Components via children
+5. **Cache expensive operations** - Use React cache() for deduplication
diff --git a/.claude/skills/seo-audit/SKILL.md b/.claude/skills/seo-audit/SKILL.md
deleted file mode 100644
index c525957..0000000
--- a/.claude/skills/seo-audit/SKILL.md
+++ /dev/null
@@ -1,497 +0,0 @@
----
-name: seo-audit
-description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
-metadata:
- version: 2.0.0
----
-
-# SEO Audit
-
-You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before auditing, understand:
-
-1. **Site Context**
- - What type of site? (SaaS, e-commerce, blog, etc.)
- - What's the primary business goal for SEO?
- - What keywords/topics are priorities?
-
-2. **Current State**
- - Any known issues or concerns?
- - Current organic traffic level?
- - Recent changes or migrations?
-
-3. **Scope**
- - Full site audit or specific pages?
- - Technical + on-page, or one focus area?
- - Access to Search Console / analytics?
-
----
-
-## Audit Framework
-
-### Schema Markup Detection Limitation
-
-**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**
-
-Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `<script>` tags during conversion).
-
-**To accurately check for schema markup, use one of these methods:**
-1. **Browser tool** — render the page and run: `document.querySelectorAll('script[type="application/ld+json"]')`
-2. **Google Rich Results Test** — https://search.google.com/test/rich-results
-3. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)
-
-Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false audit findings — these tools can't see JS-injected schema.
-
-### Priority Order
-1. **Crawlability & Indexation** (can Google find and index it?)
-2. **Technical Foundations** (is the site fast and functional?)
-3. **On-Page Optimization** (is content optimized?)
-4. **Content Quality** (does it deserve to rank?)
-5. **Authority & Links** (does it have credibility?)
-
----
-
-## Technical SEO Audit
-
-### Crawlability
-
-**Robots.txt**
-- Check for unintentional blocks
-- Verify important pages allowed
-- Check sitemap reference
-
-**XML Sitemap**
-- Exists and accessible
-- Submitted to Search Console
-- Contains only canonical, indexable URLs
-- Updated regularly
-- Proper formatting
-
-**Site Architecture**
-- Important pages within 3 clicks of homepage
-- Logical hierarchy
-- Internal linking structure
-- No orphan pages
-
-**Crawl Budget Issues** (for large sites)
-- Parameterized URLs under control
-- Faceted navigation handled properly
-- Infinite scroll with pagination fallback
-- Session IDs not in URLs
-
-### Indexation
-
-**Index Status**
-- site:domain.com check
-- Search Console coverage report
-- Compare indexed vs. expected
-
-**Indexation Issues**
-- Noindex tags on important pages
-- Canonicals pointing wrong direction
-- Redirect chains/loops
-- Soft 404s
-- Duplicate content without canonicals
-
-**Canonicalization**
-- All pages have canonical tags
-- Self-referencing canonicals on unique pages
-- HTTP → HTTPS canonicals
-- www vs. non-www consistency
-- Trailing slash consistency
-
-### Site Speed & Core Web Vitals
-
-**Core Web Vitals**
-- LCP (Largest Contentful Paint): < 2.5s
-- INP (Interaction to Next Paint): < 200ms
-- CLS (Cumulative Layout Shift): < 0.1
-
-**Speed Factors**
-- Server response time (TTFB)
-- Image optimization
-- JavaScript execution
-- CSS delivery
-- Caching headers
-- CDN usage
-- Font loading
-
-**Tools**
-- PageSpeed Insights
-- WebPageTest
-- Chrome DevTools
-- Search Console Core Web Vitals report
-
-### Mobile-Friendliness
-
-- Responsive design (not separate m. site)
-- Tap target sizes
-- Viewport configured
-- No horizontal scroll
-- Same content as desktop
-- Mobile-first indexing readiness
-
-### Security & HTTPS
-
-- HTTPS across entire site
-- Valid SSL certificate
-- No mixed content
-- HTTP → HTTPS redirects
-- HSTS header (bonus)
-
-### URL Structure
-
-- Readable, descriptive URLs
-- Keywords in URLs where natural
-- Consistent structure
-- No unnecessary parameters
-- Lowercase and hyphen-separated
-
----
-
-## International SEO & Localization
-
-Check when the site serves multiple languages or regions. Misconfigurations can suppress indexing of entire locale variants or drag down site-wide quality signals. See [International SEO reference](references/international-seo.md) for evidence and source URLs.
-
-### Hreflang
-
-Three equivalent placement methods: HTML `<link>` in `<head>`, HTTP `Link` headers, XML sitemap `<xhtml:link>`. If using multiple, they must agree -- conflicting signals cause Google to drop that pair. For 10+ locales, prefer sitemap-based (no page weight, no per-request cost).
-
-**Check for:**
-- Self-referencing entry on every page (page must include itself in the hreflang set)
-- Reciprocal links (if A points to B, B must point back to A -- or both are ignored)
-- Valid codes: ISO 639-1 language + optional ISO 3166-1 Alpha 2 region (e.g., `en`, `en-GB` -- never `en-UK`)
-- `x-default` present, pointing to fallback page (language selector or default locale)
-- All target URLs return 200, are indexable, and match their canonical URL
-- No duplicate language-region codes pointing to different URLs
-
-**Common errors:** Missing self-referencing entry (all hreflang ignored). No return tag / one-directional (pair dropped). Invalid codes like `en-UK` (use `en-GB`). Hreflang target is non-canonical, 404, or blocked (cluster discarded). HTML and sitemap annotations disagree (conflicting pair dropped).
-
-**At scale:** `<xhtml:link>` children don't count toward 50K URL sitemap limit, but the 50MB file size limit becomes the bottleneck (plan 2K-5K URLs per file with full hreflang). Focus hreflang on pages receiving wrong-language traffic -- not required on every page. For Bing: supplement with `<html lang>` and `<meta http-equiv="content-language">` (Bing treats hreflang as a weak signal).
-
-### Canonicalization for Multilingual Sites
-
-- Each locale page must self-canonical (e.g., `/ar/page` canonicals to `/ar/page`)
-- Never cross-locale canonical (French to English) -- suppresses the non-canonical locale entirely
-- Canonical URL must appear in the hreflang set -- if not, all hreflang is ignored
-- Canonical overrides hreflang when they conflict
-- Protocol/domain must be consistent across canonical, hreflang, and sitemap (`https` + same domain variant)
-- Paginated locale pages: self-referencing canonical per page (never canonical page 2+ to page 1)
-
-**Common mistakes:** all locales canonical to English (kills indexing), canonical URL not in hreflang set (silently ignored), protocol mismatch between canonical and hreflang, CMS setting deep page canonical to homepage.
-
-### International Sitemaps
-
-**Check for:**
-- `xmlns:xhtml` namespace on `<urlset>`, each `<url>` includes `<xhtml:link>` for all locales including itself
-- `x-default` alternate included; all URLs absolute (full protocol + domain)
-- Sitemap index in Search Console and robots.txt; split by content type, not by locale
-
-**Next.js caveat:** `alternates.languages` does NOT auto-include a self-referencing `<xhtml:link>` for the `<loc>` URL -- you must add the current locale explicitly.
-
-### Locale URL Structure
-
-**Recommended:** Subdirectories (`/en/`, `/ar/`). **Acceptable:** Subdomains or ccTLDs. **Not recommended:** URL parameters (`?lang=en`).
-
-**Check for:**
-- Consistent locale prefix strategy; all locales prefixed (hiding locale from URLs prevents Google from distinguishing versions)
-- Root URL handled as `x-default` with redirect, or serves default locale content
-- No IP/Accept-Language content negotiation (Googlebot: US IPs, no Accept-Language header)
-- Trailing slash + case consistency across locale paths, canonicals, hreflang, and sitemaps
-- 301 redirects from non-canonical format to canonical
-
-**Note:** Google's International Targeting report in Search Console is deprecated. Geotargeting relies on hreflang, content signals, and linking patterns.
-
-### Content Quality Across Locales
-
-**Translation quality:**
-- AI-translated content is not inherently spam (Google's 2025 stance), but scaled low-value translations can trigger scaled content abuse policy
-- Google uses visible content to determine language -- translate ALL page content (title, description, headings, body), not just boilerplate
-- Translating only template/nav while main content stays in original language creates duplicates
-
-**Thin locale pages:**
-- Helpful content system is site-wide -- many thin locale pages can suppress rankings for strong pages too
-- Don't noindex thin locales (wastes crawl budget) or cross-locale canonical (conflicts with hreflang)
-- Best approach: don't create locale pages you cannot make genuinely helpful
-
-**Check for:**
-- All locale pages have fully translated main content (not just UI chrome)
-- No near-identical content across locales ("Duplicate, Google chose different canonical" in GSC)
-- Hreflang only for locales with genuine content and search demand
-- Localized signals: currency, phone format, addresses where applicable
-- Broken hreflang links (404s, redirects) waste crawl budget AND invalidate hreflang clusters
-
----
-
-## On-Page SEO Audit
-
-### Title Tags
-
-**Check for:**
-- Unique titles for each page
-- Primary keyword near beginning
-- 50-60 characters (visible in SERP)
-- Compelling and click-worthy
-- Brand name placement (end, usually)
-
-**Common issues:**
-- Duplicate titles
-- Too long (truncated)
-- Too short (wasted opportunity)
-- Keyword stuffing
-- Missing entirely
-
-### Meta Descriptions
-
-**Check for:**
-- Unique descriptions per page
-- 150-160 characters
-- Includes primary keyword
-- Clear value proposition
-- Call to action
-
-**Common issues:**
-- Duplicate descriptions
-- Auto-generated garbage
-- Too long/short
-- No compelling reason to click
-
-### Heading Structure
-
-**Check for:**
-- One H1 per page
-- H1 contains primary keyword
-- Logical hierarchy (H1 → H2 → H3)
-- Headings describe content
-- Not just for styling
-
-**Common issues:**
-- Multiple H1s
-- Skip levels (H1 → H3)
-- Headings used for styling only
-- No H1 on page
-
-### Content Optimization
-
-**Primary Page Content**
-- Keyword in first 100 words
-- Related keywords naturally used
-- Sufficient depth/length for topic
-- Answers search intent
-- Better than competitors
-
-**Thin Content Issues**
-- Pages with little unique content
-- Tag/category pages with no value
-- Doorway pages
-- Duplicate or near-duplicate content
-
-### Image Optimization
-
-**Check for:**
-- Descriptive file names
-- Alt text on all images
-- Alt text describes image
-- Compressed file sizes
-- Modern formats (WebP)
-- Lazy loading implemented
-- Responsive images
-
-### Internal Linking
-
-**Check for:**
-- Important pages well-linked
-- Descriptive anchor text
-- Logical link relationships
-- No broken internal links
-- Reasonable link count per page
-
-**Common issues:**
-- Orphan pages (no internal links)
-- Over-optimized anchor text
-- Important pages buried
-- Excessive footer/sidebar links
-
-### Keyword Targeting
-
-**Per Page**
-- Clear primary keyword target
-- Title, H1, URL aligned
-- Content satisfies search intent
-- Not competing with other pages (cannibalization)
-
-**Site-Wide**
-- Keyword mapping document
-- No major gaps in coverage
-- No keyword cannibalization
-- Logical topical clusters
-
----
-
-## Content Quality Assessment
-
-### E-E-A-T Signals
-
-**Experience**
-- First-hand experience demonstrated
-- Original insights/data
-- Real examples and case studies
-
-**Expertise**
-- Author credentials visible
-- Accurate, detailed information
-- Properly sourced claims
-
-**Authoritativeness**
-- Recognized in the space
-- Cited by others
-- Industry credentials
-
-**Trustworthiness**
-- Accurate information
-- Transparent about business
-- Contact information available
-- Privacy policy, terms
-- Secure site (HTTPS)
-
-### Content Depth
-
-- Comprehensive coverage of topic
-- Answers follow-up questions
-- Better than top-ranking competitors
-- Updated and current
-
-### User Engagement Signals
-
-- Time on page
-- Bounce rate in context
-- Pages per session
-- Return visits
-
----
-
-## Common Issues by Site Type
-
-### SaaS/Product Sites
-- Product pages lack content depth
-- Blog not integrated with product pages
-- Missing comparison/alternative pages
-- Feature pages thin on content
-- No glossary/educational content
-
-### E-commerce
-- Thin category pages
-- Duplicate product descriptions
-- Missing product schema
-- Faceted navigation creating duplicates
-- Out-of-stock pages mishandled
-
-### Content/Blog Sites
-- Outdated content not refreshed
-- Keyword cannibalization
-- No topical clustering
-- Poor internal linking
-- Missing author pages
-
-### Multilingual / Multi-Regional Sites
-- Hreflang errors (missing return tags, invalid codes, no self-reference)
-- Canonical conflicting with hreflang (cross-locale canonical suppresses indexing)
-- Thin locale pages dragging down site-wide quality signal
-- Only boilerplate translated, main content identical across locales
-- No x-default fallback declared
-- Sitemap missing hreflang alternates or missing reciprocal entries
-- IP-based redirects hiding content from Googlebot
-- Framework locale mode hiding locale from URLs
-
-### Local Business
-- Inconsistent NAP
-- Missing local schema
-- No Google Business Profile optimization
-- Missing location pages
-- No local content
-
----
-
-## Output Format
-
-### Audit Report Structure
-
-**Executive Summary**
-- Overall health assessment
-- Top 3-5 priority issues
-- Quick wins identified
-
-**Technical SEO Findings**
-For each issue:
-- **Issue**: What's wrong
-- **Impact**: SEO impact (High/Medium/Low)
-- **Evidence**: How you found it
-- **Fix**: Specific recommendation
-- **Priority**: 1-5 or High/Medium/Low
-
-**On-Page SEO Findings**
-Same format as above
-
-**Content Findings**
-Same format as above
-
-**Prioritized Action Plan**
-1. Critical fixes (blocking indexation/ranking)
-2. High-impact improvements
-3. Quick wins (easy, immediate benefit)
-4. Long-term recommendations
-
----
-
-## References
-
-- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
-- [International SEO](references/international-seo.md): Evidence and sources for hreflang, canonical + i18n, sitemaps, URL structure, and content quality across locales
-- For AI search optimization (AEO, GEO, LLMO, AI Overviews), see the **ai-seo** skill
-
----
-
-## Tools Referenced
-
-**Free Tools**
-- Google Search Console (essential)
-- Google PageSpeed Insights
-- Bing Webmaster Tools
-- Rich Results Test (**use this for schema validation — it renders JavaScript**)
-- Mobile-Friendly Test
-- Schema Validator
-
-> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Use the browser tool, Rich Results Test, or Screaming Frog instead — they render JavaScript and capture dynamically-injected markup. See the Schema Markup Detection Limitation section above.
-
-**Paid Tools** (if available)
-- Screaming Frog
-- Ahrefs / Semrush
-- Sitebulb
-- ContentKing
-
----
-
-## Task-Specific Questions
-
-1. What pages/keywords matter most?
-2. Do you have Search Console access?
-3. Any recent changes or migrations?
-4. Who are your top organic competitors?
-5. What's your current organic traffic baseline?
-
----
-
-## Related Skills
-
-- **ai-seo**: For optimizing content for AI search engines (AEO, GEO, LLMO)
-- **programmatic-seo**: For building SEO pages at scale
-- **site-architecture**: For page hierarchy, navigation design, and URL structure
-- **schema**: For implementing structured data
-- **cro**: For optimizing pages for conversion (not just ranking)
-- **analytics**: For measuring SEO performance
diff --git a/.claude/skills/seo-audit/evals/evals.json b/.claude/skills/seo-audit/evals/evals.json
deleted file mode 100644
index e3415c5..0000000
--- a/.claude/skills/seo-audit/evals/evals.json
+++ /dev/null
@@ -1,136 +0,0 @@
-{
- "skill_name": "seo-audit",
- "evals": [
- {
- "id": 1,
- "prompt": "Can you do an SEO audit of our SaaS website? We're getting about 2,000 organic visits/month but feel like we should be getting more. URL: https://example.com",
- "expected_output": "Should check for product-marketing.md first. Should ask clarifying questions about priority keywords, Search Console access, recent changes, and competitors. Should follow the audit framework priority order: Crawlability & Indexation, Technical Foundations, On-Page Optimization, Content Quality, Authority & Links. Should check robots.txt, XML sitemap, site architecture. Should evaluate title tags, meta descriptions, heading structure, and content optimization. Should NOT report on schema markup based solely on web_fetch (must note the detection limitation). Output should follow the Audit Report Structure: Executive Summary, Technical SEO Findings, On-Page SEO Findings, Content Findings, and Prioritized Action Plan.",
- "assertions": [
- "Checks for product-marketing.md",
- "Asks clarifying questions about keywords, Search Console, recent changes",
- "Follows audit priority order: crawlability first, then technical, on-page, content, authority",
- "Checks robots.txt and XML sitemap",
- "Evaluates title tags, meta descriptions, heading structure",
- "Does NOT claim 'no schema found' based on web_fetch alone",
- "Notes schema markup detection limitation",
- "Output has Executive Summary",
- "Output has Prioritized Action Plan",
- "Each finding has Issue, Impact, Evidence, Fix, and Priority"
- ],
- "files": []
- },
- {
- "id": 2,
- "prompt": "Why am I not ranking for 'project management software'? We have a page targeting that keyword but it's stuck on page 3.",
- "expected_output": "Should trigger on the casual 'why am I not ranking' phrasing. Should investigate both on-page and off-page factors. On-page: check title tag, H1, URL alignment with keyword; evaluate content depth vs competitors; check for keyword cannibalization. Technical: check indexation status, canonical tags, crawlability. Content quality: assess E-E-A-T signals, content depth, user engagement. Should provide specific, actionable fixes organized by priority. Should mention competitive analysis against current top-ranking pages.",
- "assertions": [
- "Triggers on casual 'why am I not ranking' phrasing",
- "Checks title tag, H1, URL alignment with target keyword",
- "Evaluates content depth vs competitors",
- "Checks for keyword cannibalization",
- "Checks indexation status and canonical tags",
- "Assesses E-E-A-T signals",
- "Mentions competitive analysis against top-ranking pages",
- "Provides actionable fixes organized by priority"
- ],
- "files": []
- },
- {
- "id": 3,
- "prompt": "We just migrated from WordPress to Next.js and our organic traffic dropped 40% in the last month. Help!",
- "expected_output": "Should treat this as an urgent migration diagnostic. Should immediately check: redirect mapping (301s from old URLs to new), canonical tags on new pages, robots.txt not blocking crawlers, XML sitemap submitted and updated, meta tags preserved. Should check for common migration issues: redirect chains/loops, soft 404s, lost internal links, changed URL structures without redirects. Should reference Search Console coverage report for indexation issues. Should provide a prioritized recovery plan with critical fixes first. Should mention monitoring timeline expectations (recovery can take weeks).",
- "assertions": [
- "Treats as urgent migration diagnostic",
- "Checks redirect mapping (301s)",
- "Checks canonical tags on new pages",
- "Checks robots.txt not blocking crawlers",
- "Checks XML sitemap updated and submitted",
- "Checks for redirect chains or loops",
- "Checks for soft 404s",
- "References Search Console coverage report",
- "Provides prioritized recovery plan",
- "Mentions recovery timeline expectations"
- ],
- "files": []
- },
- {
- "id": 4,
- "prompt": "Review the technical SEO of our e-commerce site. We have about 50,000 products and use faceted navigation.",
- "expected_output": "Should focus on e-commerce-specific technical issues: faceted navigation creating duplicate content, crawl budget management for large product catalog, parameterized URLs, product schema markup (with the caveat about detection limitations). Should check for thin category pages, duplicate product descriptions, out-of-stock page handling. Should address crawl budget issues: pagination, infinite scroll handling, session IDs in URLs. Should provide structured findings with Impact ratings and specific fixes.",
- "assertions": [
- "Addresses faceted navigation duplicate content",
- "Addresses crawl budget for large catalog",
- "Checks for parameterized URL issues",
- "Mentions product schema with detection limitation caveat",
- "Checks for thin category pages",
- "Checks for duplicate product descriptions",
- "Addresses out-of-stock page handling",
- "Addresses pagination and infinite scroll",
- "Findings include Impact ratings and specific fixes"
- ],
- "files": []
- },
- {
- "id": 5,
- "prompt": "Can you check our blog posts for on-page SEO issues? We publish 4 posts per week but traffic has been flat for 6 months.",
- "expected_output": "Should apply the Content/Blog Sites framework: check for outdated content not refreshed, keyword cannibalization, missing topical clustering, poor internal linking, missing author pages. Should audit on-page elements: title tags, meta descriptions, heading structure, keyword targeting per post. Should assess E-E-A-T signals for blog content. Should check for content depth issues and whether posts answer search intent. Should recommend a content audit process and provide a prioritized action plan for the existing content library.",
- "assertions": [
- "Applies Content/Blog Sites framework",
- "Checks for outdated content",
- "Checks for keyword cannibalization",
- "Checks for topical clustering",
- "Checks for internal linking quality",
- "Checks for author pages and E-E-A-T signals",
- "Audits title tags, meta descriptions, heading structure",
- "Assesses whether content answers search intent",
- "Recommends content audit process",
- "Provides prioritized action plan"
- ],
- "files": []
- },
- {
- "id": 6,
- "prompt": "I run a local plumbing business with 3 locations. My website barely shows up when people search for 'plumber near me' in our areas. What's wrong?",
- "expected_output": "Should apply the Local Business site-type framework. Should check for: inconsistent NAP (Name, Address, Phone) across the site, missing local schema markup (with detection limitation caveat), Google Business Profile optimization, missing individual location pages for each of the 3 locations, and missing local content. Should also check standard technical and on-page factors. Should recommend local-specific fixes: location-specific pages with unique content, local schema on each, GBP optimization, citation consistency.",
- "assertions": [
- "Applies Local Business framework",
- "Checks NAP consistency",
- "Checks for local schema markup with detection caveat",
- "Addresses Google Business Profile optimization",
- "Recommends individual location pages for each location",
- "Recommends local content strategy",
- "Checks standard technical SEO factors too",
- "Provides prioritized local SEO action plan"
- ],
- "files": []
- },
- {
- "id": 7,
- "prompt": "Our site loads really slowly, especially on mobile. Pages take 5-6 seconds to load. Is this hurting our SEO?",
- "expected_output": "Should focus on Site Speed and Core Web Vitals. Should explain CWV thresholds: LCP < 2.5s, INP < 200ms, CLS < 0.1, and that 5-6s load time is well above acceptable. Should investigate speed factors: server response time (TTFB), image optimization, JavaScript execution, CSS delivery, caching headers, CDN usage, font loading. Should recommend specific tools: PageSpeed Insights, WebPageTest, Chrome DevTools, Search Console CWV report. Should explain that yes, page speed is a ranking factor and directly impacts SEO. Should provide prioritized fixes.",
- "assertions": [
- "Focuses on Core Web Vitals",
- "Explains CWV thresholds (LCP, INP, CLS)",
- "Identifies 5-6s as well above acceptable",
- "Investigates specific speed factors",
- "Recommends specific diagnostic tools",
- "Confirms page speed impacts SEO rankings",
- "Provides prioritized speed fixes",
- "Addresses mobile-specific performance"
- ],
- "files": []
- },
- {
- "id": 8,
- "prompt": "I want to add FAQ schema to my product pages. Can you help me set that up?",
- "expected_output": "Should recognize this is a schema markup implementation task, not an SEO audit. Should defer to or cross-reference the schema skill, which specifically handles structured data implementation including FAQ schema. May briefly mention that FAQ schema can enable rich results, but should make clear that schema is the right skill for implementation.",
- "assertions": [
- "Recognizes this as schema markup implementation",
- "References or defers to schema skill",
- "Does not attempt a full SEO audit",
- "May briefly mention FAQ schema benefits"
- ],
- "files": []
- }
- ]
-}
diff --git a/.claude/skills/seo-audit/references/ai-writing-detection.md b/.claude/skills/seo-audit/references/ai-writing-detection.md
deleted file mode 100644
index cb67ece..0000000
--- a/.claude/skills/seo-audit/references/ai-writing-detection.md
+++ /dev/null
@@ -1,200 +0,0 @@
-# AI Writing Detection
-
-Words, phrases, and punctuation patterns commonly associated with AI-generated text. Avoid these to ensure writing sounds natural and human.
-
-Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Walter Writes (2025), Textero (2025), Plagiarism Today (2025), Rolling Stone (2025), MDPI Blog (2025)
-
----
-
-## Contents
-- Em Dashes: The Primary AI Tell
-- Overused Verbs
-- Overused Adjectives
-- Overused Transitions and Connectors
-- Phrases That Signal AI Writing (Opening Phrases, Transitional Phrases, Concluding Phrases, Structural Patterns)
-- Filler Words and Empty Intensifiers
-- Academic-Specific AI Tells
-- How to Self-Check
-
-## Em Dashes: The Primary AI Tell
-
-**The em dash (—) has become one of the most reliable markers of AI-generated content.**
-
-Em dashes are longer than hyphens (-) and are used for emphasis, interruptions, or parenthetical information. While they have legitimate uses in writing, AI models drastically overuse them.
-
-### Why Em Dashes Signal AI Writing
-- AI models were trained on edited books, academic papers, and style guides where em dashes appear frequently
-- AI uses em dashes as a shortcut for sentence variety instead of commas, colons, or parentheses
-- Most human writers rarely use em dashes because they don't exist as a standard keyboard key
-- The overuse is so consistent that it has become the unofficial signature of ChatGPT writing
-
-### What To Do Instead
-| Instead of | Use |
-|------------|-----|
-| The results—which were surprising—showed... | The results, which were surprising, showed... |
-| This approach—unlike traditional methods—allows... | This approach, unlike traditional methods, allows... |
-| The study found—as expected—that... | The study found, as expected, that... |
-| Communication skills—both written and verbal—are essential | Communication skills (both written and verbal) are essential |
-
-### Guidelines
-- Use commas for most parenthetical information
-- Use colons to introduce explanations or lists
-- Use parentheses for supplementary information
-- Reserve em dashes for rare, deliberate emphasis only
-- If you find yourself using more than one em dash per page, revise
-
----
-
-## Overused Verbs
-
-| Avoid | Use Instead |
-|-------|-------------|
-| delve (into) | explore, examine, investigate, look at |
-| leverage | use, apply, draw on |
-| optimise | improve, refine, enhance |
-| utilise | use |
-| facilitate | help, enable, support |
-| foster | encourage, support, develop, nurture |
-| bolster | strengthen, support, reinforce |
-| underscore | emphasise, highlight, stress |
-| unveil | reveal, show, introduce, present |
-| navigate | manage, handle, work through |
-| streamline | simplify, make more efficient |
-| enhance | improve, strengthen |
-| endeavour | try, attempt, effort |
-| ascertain | find out, determine, establish |
-| elucidate | explain, clarify, make clear |
-
----
-
-## Overused Adjectives
-
-| Avoid | Use Instead |
-|-------|-------------|
-| robust | strong, reliable, thorough, solid |
-| comprehensive | complete, thorough, full, detailed |
-| pivotal | key, critical, central, important |
-| crucial | important, key, essential, critical |
-| vital | important, essential, necessary |
-| transformative | significant, important, major |
-| cutting-edge | new, advanced, recent, modern |
-| groundbreaking | new, original, significant |
-| innovative | new, original, creative |
-| seamless | smooth, easy, effortless |
-| intricate | complex, detailed, complicated |
-| nuanced | subtle, complex, detailed |
-| multifaceted | complex, varied, diverse |
-| holistic | complete, whole, comprehensive |
-
----
-
-## Overused Transitions and Connectors
-
-| Avoid | Use Instead |
-|-------|-------------|
-| furthermore | also, in addition, and |
-| moreover | also, and, besides |
-| notwithstanding | despite, even so, still |
-| that being said | however, but, still |
-| at its core | essentially, fundamentally, basically |
-| to put it simply | in short, simply put |
-| it is worth noting that | note that, importantly |
-| in the realm of | in, within, regarding |
-| in the landscape of | in, within |
-| in today's [anything] | currently, now, today |
-
----
-
-## Phrases That Signal AI Writing
-
-### Opening Phrases to Avoid
-- "In today's fast-paced world..."
-- "In today's digital age..."
-- "In an era of..."
-- "In the ever-evolving landscape of..."
-- "In the realm of..."
-- "It's important to note that..."
-- "Let's delve into..."
-- "Imagine a world where..."
-
-### Transitional Phrases to Avoid
-- "That being said..."
-- "With that in mind..."
-- "It's worth mentioning that..."
-- "At its core..."
-- "To put it simply..."
-- "In essence..."
-- "This begs the question..."
-
-### Concluding Phrases to Avoid
-- "In conclusion..."
-- "To sum up..."
-- "By [doing X], you can [achieve Y]..."
-- "In the final analysis..."
-- "All things considered..."
-- "At the end of the day..."
-
-### Structural Patterns to Avoid
-- "Whether you're a [X], [Y], or [Z]..." (listing three examples after "whether")
-- "It's not just [X], it's also [Y]..."
-- "Think of [X] as [elaborate metaphor]..."
-- Starting sentences with "By" followed by a gerund: "By understanding X, you can Y..."
-
----
-
-## Filler Words and Empty Intensifiers
-
-These words often add nothing to meaning. Remove them or find specific alternatives:
-
-- absolutely
-- actually
-- basically
-- certainly
-- clearly
-- definitely
-- essentially
-- extremely
-- fundamentally
-- incredibly
-- interestingly
-- naturally
-- obviously
-- quite
-- really
-- significantly
-- simply
-- surely
-- truly
-- ultimately
-- undoubtedly
-- very
-
----
-
-## Academic-Specific AI Tells
-
-| Avoid | Use Instead |
-|-------|-------------|
-| shed light on | clarify, explain, reveal |
-| pave the way for | enable, allow, make possible |
-| a myriad of | many, numerous, various |
-| a plethora of | many, numerous, several |
-| paramount | very important, essential, critical |
-| pertaining to | about, regarding, concerning |
-| prior to | before |
-| subsequent to | after |
-| in light of | because of, given, considering |
-| with respect to | about, regarding, for |
-| in terms of | regarding, for, about |
-| the fact that | that (or rewrite sentence) |
-
----
-
-## How to Self-Check
-
-1. Read your text aloud. If phrases sound unnatural in speech, revise them
-2. Ask: "Would I say this in a conversation with a colleague?"
-3. Check for repetitive sentence structures
-4. Look for clusters of the words listed above
-5. Ensure varied sentence lengths (not all similar length)
-6. Verify each intensifier adds genuine meaning
diff --git a/.claude/skills/seo-audit/references/international-seo.md b/.claude/skills/seo-audit/references/international-seo.md
deleted file mode 100644
index d2a2d1e..0000000
--- a/.claude/skills/seo-audit/references/international-seo.md
+++ /dev/null
@@ -1,230 +0,0 @@
-# International SEO: Evidence & Sources
-
-Detailed evidence backing the International SEO & Localization section of the SEO Audit skill. Organized by topic with source URLs and key quotes.
-
----
-
-## Hreflang
-
-### Placement Methods
-
-Google supports three equivalent methods: HTML `<link>` in `<head>`, HTTP `Link` headers, and XML sitemap `<xhtml:link>` elements. Google confirmed no method is prioritized over another.
-
-Google combines signals from both HTML and sitemaps. If the same language-region pair points to different URLs across methods, Google drops that pair rather than guessing.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [SEJ: Google Combines Hreflang Signals](https://www.searchenginejournal.com/google-combines-hreflang-signals-from-html-sitemaps/389219/)
-
-### Reciprocal Requirement
-
-Google's docs: "If page X links to page Y, page Y must link back to page X. If not, those annotations may be ignored or not interpreted correctly."
-
-Every page must include itself (self-referencing) in the hreflang set. Missing self-referencing is the #1 error found by Semrush audits. A study of 374,756 domains found 67% of hreflang implementations had issues.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Semrush: 9 Common Hreflang Errors](https://www.semrush.com/blog/hreflang-errors/)
-- [SE Land: 31% of International Websites Contain Hreflang Errors](https://searchengineland.com/study-31-of-international-websites-contain-hreflang-errors-395161)
-
-### x-default
-
-Introduced April 2013. Designates the fallback page for users whose language/region matches no declared variant. Can point to the same URL as one of the language-specific alternates. Must be included in the complete set of annotations on every variant page.
-
-- [Google Blog: x-default hreflang](https://developers.google.com/search/blog/2013/04/x-default-hreflang-for-international-pages)
-- [Google Blog: How x-default can help you (2023)](https://developers.google.com/search/blog/2023/05/x-default)
-
-### Language & Region Codes
-
-Language: ISO 639-1 (2-letter). Region: ISO 3166-1 Alpha 2 (2-letter). Format: `language[-script][-region]`.
-
-You cannot specify a region code alone. Common mistakes: `en-UK` (should be `en-GB`), `es-419` (not ISO 3166-1). A study found 8.9% of sites using hreflang contain invalid language codes.
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [SE Land: 31% Study](https://searchengineland.com/study-31-of-international-websites-contain-hreflang-errors-395161)
-
-### Hreflang at Scale (20+ locales)
-
-With 20 locales, HTML `<head>` hreflang adds ~1.5KB per page for zero user benefit. Sitemap-based hreflang has zero runtime performance impact. `<xhtml:link>` child elements do NOT count toward the 50,000 URL sitemap limit (only `<loc>` elements count).
-
-John Mueller recommends focusing hreflang on pages receiving wrong-language traffic, not every page: "I wouldn't do it for any of the other pages of the site because it's so complex & hard to manage."
-
-- [SERoundtable: Child Elements Don't Count](https://www.seroundtable.com/google-child-elements-dont-count-towards-sitemap-url-limit-34377.html)
-- [SERoundtable: Where To Focus Hreflang](https://www.seroundtable.com/using-hreflang-34127.html)
-- [Yoast: hreflang Ultimate Guide](https://yoast.com/hreflang-ultimate-guide/)
-
-### Google vs Bing
-
-Bing treats hreflang as a "weak signal." Bing relies on `content-language` meta tag, HTML `lang` attribute, ccTLDs, and server location. Yandex supports hreflang like Google.
-
-For both engines: implement hreflang (Google/Yandex) + `<html lang="...">` + `<meta http-equiv="content-language">` (Bing).
-
-- [Digital Ready Marketing: Bing Doesn't Use Hreflang](https://digitalreadymarketing.com/bing-doesnt-use-hreflang-annotation-what-does-it-use/)
-- [Yoast: hreflang Ultimate Guide](https://yoast.com/hreflang-ultimate-guide/)
-
----
-
-## Canonicalization & i18n
-
-### Self-Referencing Canonicals
-
-Each locale page must canonical to itself. John Mueller: "Don't use a rel=canonical across languages/countries, only use it on a per-country/language basis."
-
-Google's docs: "Specify a canonical page in the same language, or the best possible substitute language if a canonical doesn't exist for the same language."
-
-- [John Mueller: hreflang canonical](https://johnmu.com/hreflang-canonical/)
-- [Google: Consolidate Duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
-
-### Canonical Overrides Hreflang
-
-Mueller: "If your canonical is pointing somewhere else, Google will follow that and ignore your hreflang annotation." The canonical URL must be one of the URLs in the hreflang set, or all hreflang markup is ignored.
-
-Google also states: "Google prefers URLs that are part of hreflang clusters for canonicalization" -- when signals align, hreflang strengthens canonical selection.
-
-- [John Mueller: hreflang canonical](https://johnmu.com/hreflang-canonical/)
-- [SEJ: Hreflang Tags Are Hints](https://www.searchenginejournal.com/google-reminds-that-hreflang-tags-are-hints-not-directives/546428/)
-- [Google: Consolidate Duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
-
-### Near-Duplicate Regional Variants
-
-Mueller (2023 Office Hours): "If the content is completely the same, and we can't tell any difference, then for simplicity and user experience we may just show one version -- even if hreflang is present."
-
-Google's duplicate detection runs BEFORE hreflang evaluation. To keep both versions indexed, you need substantive content differences beyond currency symbols.
-
-- [International Web Mastery: Same-Language Duplicate Pages](https://internationalwebmastery.com/blog/how-google-handles-canonicalization-of-same-language-duplicate-near-duplicate-pages/)
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Pagination Across Locales
-
-Google: "Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL." Each paginated page in each locale gets self-referencing canonical. `rel="next/prev"` deprecated March 2019.
-
-- [Google: Pagination Best Practices](https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading)
-
----
-
-## International Sitemaps
-
-### Structure
-
-Each `<url>` entry includes `<xhtml:link>` alternates for every locale. Requires `xmlns:xhtml="http://www.w3.org/1999/xhtml"` namespace.
-
-Split sitemaps by content type, not by locale. Splitting by locale creates maintenance problems because every locale sitemap must reference every other locale (reciprocal requirement).
-
-- [Google Search Central: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Lumar: How Google Handles Hreflang](https://www.lumar.io/office-hours/hreflang/)
-
-### Size Limits
-
-50,000 URLs / 50MB uncompressed per sitemap. Only `<loc>` elements count toward the 50K limit. But with 20 hreflang alternates per entry, the 50MB file size limit becomes the bottleneck. Plan for 2,000-5,000 URLs per sitemap when using full hreflang.
-
-- [Google: Build and Submit a Sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)
-- [SERoundtable: Sitemap 50,000 Limit](https://www.seroundtable.com/google-sitemap-50-000-limit-based-on-location-urls-not-alternative-urls-33843.html)
-
-### Submission
-
-Submit the sitemap index in Search Console AND reference it in robots.txt. Individual child sitemaps can be submitted separately for per-sitemap reporting.
-
-- [Google: Build and Submit a Sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)
-
-### Next.js Caveat
-
-Next.js `alternates.languages` does NOT automatically include a self-referencing `<xhtml:link>` for the `<loc>` URL. You must explicitly include the `<loc>` URL's own language in the `languages` object.
-
-- [Next.js Docs: sitemap.xml](https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap)
-
----
-
-## URL Structure
-
-### Strategies Compared
-
-Google treats subdirectories and subdomains equivalently. Mueller: "From our point of view...they say subdomains and subdirectories are essentially equivalent."
-
-URL parameters (`?lang=en`) are explicitly "Not recommended" per Google docs.
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Default Language
-
-Mueller recommends: set `/` as x-default, put each language in its own prefix. Without marking `/` as x-default, "to Google it can look like '/' is a separate page from the others."
-
-- [Google Blog: x-default](https://developers.google.com/search/blog/2023/05/x-default)
-- [Google Blog: Creating the Right Homepage](https://developers.google.com/search/blog/2014/05/creating-right-homepage-for-your)
-
-### Content Negotiation / IP Redirects
-
-Google strongly advises against locale-adaptive pages. Googlebot crawls from US IPs and does not send Accept-Language headers. Separate URLs + hreflang are required.
-
-- [Google: Locale-Adaptive Pages](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages)
-
-### Trailing Slash Consistency
-
-Mueller: trailing slash is "a significant part of the URL and will change the URL if it's there or not." Pick one format for all locale paths, internal links, canonicals, hreflang, and sitemaps.
-
-Mueller (2025): "Consistency is the biggest technical SEO factor."
-
-- [SERoundtable: Consistency Is The Biggest Technical SEO Factor](https://www.seroundtable.com/google-consistency-seo-40427.html)
-
-### Search Console Geotargeting
-
-The International Targeting report is deprecated. Google now relies entirely on hreflang, content language analysis, and linking patterns. You can add subdirectory properties for per-locale reporting.
-
-- [Google Support: International Targeting Deprecated](https://support.google.com/webmasters/answer/12474899?hl=en)
-
-### Framework Locale Modes
-
-Use `localePrefix: 'always'` (next-intl) or equivalent. Never hide locale from URLs -- Google needs unique URLs per language. Using `'never'` mode disables alternate links entirely.
-
-- [next-intl: Routing Configuration](https://next-intl.dev/docs/routing/configuration)
-- [Next.js Discussion #18419](https://github.com/vercel/next.js/discussions/18419)
-
----
-
-## Content Quality Across Locales
-
-### Auto-Translated Content (2025 Stance)
-
-Google removed longstanding guidance advising against auto-translated content in mid-2025. Current stance: "Our policies do not strictly define content that has been translated by AI as spam." The scaled content abuse policy mentions translation as a possible vector, but does not ban it.
-
-Reddit scaled AI translations to 35+ languages with Google's knowledge. The key distinction is intent and quality, not the method.
-
-- [Google Spam Policies](https://developers.google.com/search/docs/essentials/spam-policies)
-- [Glenn Gabe: Auto-Translating Content](https://www.gsqi.com/marketing-blog/auto-translating-content-google-scaled-content-abuse/)
-- [SE Land: Reddit AI Translations](https://searchengineland.com/google-comments-on-reddits-use-of-ai-to-translate-its-pages-456908)
-
-### Thin Locale Pages
-
-Google: "Localized versions of a page are only considered duplicates if the main content of the page remains untranslated." Pages with only translated boilerplate get clustered as duplicates.
-
-Do NOT use noindex for unwanted locale pages (wastes crawl budget). Do NOT canonical cross-locale (conflicts with hreflang). Best approach: don't create locale pages you can't make genuinely helpful.
-
-- [Google: Localized Versions](https://developers.google.com/search/docs/specialty/international/localized-versions)
-- [Google: Crawl Budget Management](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget)
-
-### Helpful Content System Impact
-
-Merged into core ranking March 2024. Site-wide signal: "any content -- not just unhelpful content -- on sites determined to have relatively high amounts of unhelpful content overall is less likely to perform well in Search."
-
-Low-quality translated pages can drag down the entire site. This is the strongest argument against creating locale pages that aren't genuinely helpful.
-
-- [Google Blog: Helpful Content Update](https://developers.google.com/search/blog/2022/08/helpful-content-update)
-- [Amsive: What Changed in 2024](https://www.amsive.com/insights/seo/googles-helpful-content-update-ranking-system-what-happened-and-what-changed-in-2024/)
-
-### Partial Translation
-
-Google: "Translating only the boilerplate text of your pages while keeping the bulk of your content in a single language...can create a bad user experience." Google uses visible content (not lang attribute) to determine page language.
-
-Translate ALL content on a page if you create a locale version. Untranslated metadata (title, description) in the wrong language reduces CTR.
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
-
-### Crawl Budget
-
-Only a concern for 1M+ pages or 10K+ pages changing daily. But alternate URLs (hreflang targets) do consume crawl budget. Broken hreflang links waste budget AND invalidate signals.
-
-- [Google: Crawl Budget Management](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget)
-- [Google Blog: Crawl Budget](https://developers.google.com/search/blog/2017/01/what-crawl-budget-means-for-googlebot)
-
-### Locale-Specific Signals
-
-Google identifies audience via: "local addresses and phone numbers on the pages, the use of local language and currency, links from other local sites, or signals from your Business Profile."
-
-- [Google: Managing Multi-Regional Sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)
diff --git a/skills-lock.json b/skills-lock.json
index 3c4cd15..7a50723 100644
--- a/skills-lock.json
+++ b/skills-lock.json
@@ -13,17 +13,17 @@
"skillPath": "skills/gsap/SKILL.md",
"computedHash": "ef2658b3705d3fd5c8e38d197b31521553a0bee3b40bda2ab70bf22bd6b88854"
},
+ "nextjs-developer": {
+ "source": "jeffallan/claude-skills",
+ "sourceType": "github",
+ "skillPath": "skills/nextjs-developer/SKILL.md",
+ "computedHash": "99cc9507d254aa8ce627a4c86755fa0424f19fafb857dc02f7f6e02a086312f8"
+ },
"react-three-fiber": {
"source": "vercel-labs/json-render",
"sourceType": "github",
"skillPath": "skills/react-three-fiber/SKILL.md",
"computedHash": "33cfac131cbe9c89b14c4b49ca01e0b0a4a3f9c23bb6c81ac0514143703283e8"
- },
- "seo-audit": {
- "source": "coreyhaines31/marketingskills",
- "sourceType": "github",
- "skillPath": "skills/seo-audit/SKILL.md",
- "computedHash": "606da61224d9d5687020816292c88152a7fcb27ce375b22f92f429e074f07f34"
}
}
}