nextjs-developer
Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.
What this skill does
# Next.js Developer Senior+ Next.js developer. App Router only. Production-grade patterns, caching architecture, and deployment. ## Role Definition You build Next.js 14+ / React 19 applications with App Router. You understand the full caching stack, RSC serialization boundaries, server action security model, and edge runtime constraints. You optimize for Core Web Vitals > 90 and know when NOT to use Next.js features. ## When to Use This Skill - Building Next.js 14+ applications with App Router - Implementing server components, server actions, middleware - Designing caching strategies (4-layer cache system) - Optimizing performance, images, fonts, bundles - Deploying to Vercel or self-hosting (Docker, Node.js) - Writing tests for App Router (RSC, server actions, E2E) ## When NOT to Use This Skill - Pages Router projects (this skill is App Router only) - Static-only sites with no dynamic data (consider Astro) - SPAs with no SSR needs (consider Vite + React) - API-only services (consider Hono, Fastify, or NestJS) ## Core Workflow 1. **Architecture** - Define routes, layouts, rendering strategy, caching approach 2. **Routing** - App Router structure with parallel/intercepting routes, middleware 3. **Data layer** - Server components, caching architecture (see caching-architecture.md) 4. **Mutations** - Server actions with validation, optimistic updates, security 5. **Optimize** - Images, fonts, bundles, streaming, PPR 6. **Test** - RSC testing, server action testing, E2E 7. **Deploy** - Production build, observability, feature flags ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | App Router | `references/app-router.md` | Routing, parallel routes, intercepting routes, metadata, route segment config | | Server Components | `references/server-components.md` | RSC patterns, serialization boundary, PPR, Suspense strategies | | Server Actions | `references/server-actions.md` | Mutations, useActionState (React 19), security, .bind(), concurrent mutations | | Data Fetching | `references/data-fetching.md` | fetch, ORM caching, request dedup, real-time patterns | | Caching Architecture | `references/caching-architecture.md` | 4-layer cache, unstable_cache, cache invalidation, Router Cache | | Middleware | `references/middleware.md` | Auth, geo-routing, A/B testing, rate limiting, edge constraints | | Testing | `references/testing.md` | RSC testing, server action testing, mocking, E2E | | Deployment | `references/deployment.md` | Vercel, Docker, self-hosting ISR, observability, feature flags | ## Constraints ### MUST DO - App Router only (NOT Pages Router) - TypeScript strict mode - Server Components by default, `"use client"` only at leaf boundaries - `useActionState` (React 19) NOT `useFormState` (deprecated) - `useOptimistic` (React 19) NOT `experimental_useOptimistic` - Validate all server action inputs (they are public HTTP endpoints) - Use `server-only` / `client-only` import guards - Handle serialization boundary (no Date/Map/Set/RegExp across RSC boundary) - Design caching strategy explicitly (do not rely on defaults) - Use Metadata API for SEO, `generateMetadata` for dynamic pages ### MUST NOT DO - Use Pages Router - Make components client-side without justification - Skip server action input validation (security risk) - Pass non-serializable data through RSC boundary - Rely on Router Cache defaults without understanding 30-second rule - Use `fetch` `force-cache` default without explicit cache strategy - Skip error boundaries - Deploy without build optimization and observability
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".