Communitygithub.com

Next.js i18n Einrichtung (`nextjs-i18n-setup`)

Next-intl Internationalisierung für Next.js App Router bootstrappen, konfigurieren und verifizieren (proxy.ts/middleware.ts, next/root-params, [locale]-Layout, Routing)

Was ist Next.js i18n Einrichtung (`nextjs-i18n-setup`)?

Diese Fertigkeit automatisiert die vollständige Einrichtung von `next-intl` in einem bestehenden Next.js App Router Projekt. Sie erkennt automatisch die Next.js Version (16+ oder ≤15) und erstellt den passenden Interceptor (`proxy.ts` oder `middleware.ts`), konfiguriert das Routing über `i18n/routing.ts`, erstellt einen Request-Handler mit dem modernen `next/root-params`-Ansatz (anstelle der veralteten `requestLocale` / `setRequestLocale()`) und generiert Navigationshilfen in `i18n/navigation.ts`. Nach der Installation werden Wörterbücher für alle unterstützten Sprachen angelegt, das Root-Layout unter `app/[locale]/` inklusive `generateStaticParams()` und `NextIntlClientProvider` eingerichtet, sowie TypeScript-Typen in `global.d.ts` erweitert. Die Fertigkeit eignet sich für Entwickler, die ein existierendes Next.js-Projekt schnell und korrekt internationalisieren möchten – inklusive eines Verifikationsskripts und der Integration mit der Next.js-Plugin-Konfiguration. Unterstützte Auslöser sind Befehle wie "/nextjs-i18n-setup", "setup i18n", "install next-intl", "configure next-intl", "add internationalization", "setup locale routing" und "migrate to [locale]". Sie wird in Terminal-Umgebungen wie Claude Code, Cursor oder Codex verwendet.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-i18n-setup
Original anzeigen→Alle Skills durchsuchen

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Dokumentation

Next.js i18n Einrichtung (nextjs-i18n-setup)

Integriere next-intl in ein bestehendes Next.js App Router Projekt mit modernem next/root-params, dynamischem Segment app/[locale]/ und Next.js 16+ (proxy.ts) / Next.js <=15 (middleware.ts).

[!TIP] Boilerplate & Vorlagen: Siehe references/templates.md für vollständige Codevorlagen zum Einfügen beim Erstellen von Dateien. Schnelle Ausführung: Delegiere die Überprüfung an einen leichten Unter-Agenten (Model: 'flash').

1. Architekturregeln & Anforderungen

  1. Metadaten-Vertrag: Stelle sicher, dass docs/project.json Folgendes enthält: 
    "dictionaries_dir": "messages",
"dictionary_file_pattern": "[locale].json"
  2. Next.js Versions-Interceptor:
    • Next.js 16+: Verwende proxy.ts (oder src/proxy.ts). Migriere und entferne die alte middleware.ts.
    • Next.js <=15: Verwende middleware.ts (oder src/middleware.ts).
  3. Moderne Root-Parameter: Verwende next/root-params (await rootParams.locale()) in i18n/request.ts. Die veralteten requestLocale und setRequestLocale() sind nicht erlaubt.
  4. Navigation: Exportiere Link, redirect, usePathname, useRouter aus i18n/navigation.ts (reines TypeScript, kein JSX).
  5. Statische Generierung: Das Root-Layout app/[locale]/layout.tsx MUSS generateStaticParams() exportieren, das { locale } für alle unterstützten Sprachen zurückgibt.

2. Einrichtungs-Checkliste

  • Schritt 0: Prüfung: Überprüfe docs/project.json (supported_languages) und die Next.js-Version in package.json.
  • Schritt 1: Installation: Führe <pkg_mgr> add next-intl aus (z.B. pnpm add next-intl).
  • Schritt 2: Konfigurations-Metadaten: Stelle sicher, dass dictionaries_dir: "messages" in docs/project.json gesetzt ist.
  • Schritt 3: Routing: Erstelle i18n/routing.ts mit defineRouting (siehe Vorlagen).
  • Schritt 4: Request-Handler: Erstelle i18n/request.ts mit next/root-params (siehe Vorlagen).
  • Schritt 5: Navigationshilfen: Erstelle i18n/navigation.ts (siehe Vorlagen).
  • Schritt 6: Next-Plugin: Umwickle next.config.ts mit createNextIntlPlugin() (siehe Vorlagen).
  • Schritt 7: Interceptor: Erstelle proxy.ts (Next 16+) oder middleware.ts (Next <=15) mit einem Asset-Filter-Matcher (siehe Vorlagen).
  • Schritt 8: Starter-Wörterbücher: Stelle sicher, dass messages/[locale].json für alle unterstützten Sprachen existiert und übereinstimmende Basisschlüssel enthält.
  • Schritt 9: Layout & Routen migrieren: Verschiebe die Top-Level-Routen nach app/[locale]/. Konfiguriere dynamische dir, lang, generateStaticParams und <NextIntlClientProvider> (siehe Vorlagen).
  • Schritt 10: Typ-Erweiterung: Deklariere AppConfig.Messages in global.d.ts (siehe Vorlagen).
  • Schritt 11: Navigations-Imports: Aktualisiere interne Links in bestehenden Komponenten, um @/i18n/navigation zu verwenden.
  • Schritt 12: Überprüfung: Führe das Verifikationsskript und den Build aus: 
    pwsh .agents/skills/nextjs-i18n-setup/scripts/verify-setup.ps1 -Quiet
pnpm run build

3. Vorlage für den Einrichtungsausführungsbericht

## 🌐 Next.js i18n Einrichtungsausführungsbericht

| Schritt / Komponente | Zielfile(s)                   | Status                          | Anmerkungen              |
| :------------------- | :---------------------------- | :------------------------------ | :----------------------- |
| **Paket**            | `package.json` (`next-intl`)  | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Installierte Laufzeit    |
| **Projektkonfig**    | `docs/project.json`           | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Konfiguriertes Nachrichtenverzeichnis |
| **Routing**          | `i18n/routing.ts`             | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Sprachen & Standard      |
| **Request**          | `i18n/request.ts`             | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | next/root-params         |
| **Navigation**       | `i18n/navigation.ts`          | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Reine TS-Hilfsfunktionen |
| **Plugin**           | `next.config.ts`              | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | withNextIntl umwickelt   |
| **Interceptor**      | `proxy.ts` / `middleware.ts`  | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]`| Routen-Matcher           |
| **Wörterbücher**     | `messages/[locale].json`      | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Starter-Wörterbücher     |
| **Layout**           | `app/[locale]/layout.tsx`     | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | Statische Parameter & Anbieter |
| **Typen**            | `global.d.ts`                 | `[IMPLEMENTIERT]` / `[UNVERÄNDERT]` | AppConfig-Erweiterung    |
| **Verifizierung**    | `verify-setup.ps1` & Build    | `[BESTANDEN]`                   | Sauberer Build           |

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

BIGboss248/nextjs-wordpress

Create, configure, manage, and validate Google Antigravity customizations including skills, rules, MCP servers, lifecycle hooks, plugins, and custom JSON configs. Use when adding new capabilities to Antigravity, configuring MCP servers, writing rules, creating skills, setting up hooks, or modernizing legacy workflows.

BIGboss248/nextjs-wordpress

Spawn multiple agents into a shared conversation where they debate, disagree, and converge on a solution via a shared chat.json file. Use for architecture decisions, code review debates, design trade-offs, or any problem that benefits from adversarial reasoning. Triggers on "chatroom", "agent debate", "have agents discuss", "agent chatroom", "debate this", or /agent-chatrooms. Also triggers on phrases like "have 3 agents argue about", "multi-agent discussion", or "let them debate".

BIGboss248/nextjs-wordpress

Always-active code intelligence, search, and navigation skill utilizing the codebase-memory MCP server. Enforces an index-first protocol (verifying and refreshing the knowledge graph via index_repository or index_status before searching, required because background auto_watch is disabled to eliminate editor stutter and system lag), followed by graph-first exploration (search_graph, trace_path, get_code_snippet, query_graph, get_architecture, detect_changes) instead of naive text grep or full-file reads. Always activate before searching the codebase, inspecting unknown architecture, finding symbols, or tracing callers/callees.

BIGboss248/nextjs-wordpress

>- Discover, interview, and craft comprehensive UX/UI design specifications (design-spec.md) and design tokens for web components. Triggers on "/component-design", "design component", "design section", "design UI", "wireframe component", or "create design spec".

BIGboss248/nextjs-wordpress

>- Configure and query WooCommerce APIs including WPGraphQL, WooGraphQL, and JWT auth for headless frontends. Use when connecting Next.js to WooCommerce or fetching store catalog data.

BIGboss248/nextjs-wordpress

Orchestrate parallel browser automation using multiple Chrome DevTools MCP instances. Use when a task requires doing the same browser action across many targets simultaneously (e.g., submitting contact forms, filling applications, scraping pages that need JS rendering). Spin up 1-5 parallel Chrome agents.

BIGboss248/nextjs-wordpress

Workflow for spawning an independent subagent to conduct unbiased code reviews and inject adversarial edge-case tests ([ComponentName].edge.test.tsx).

BIGboss248/nextjs-wordpress

>- Build Next.js App Router React components with Suspense skeletons, semantic OKLCH tokens, Jest + RTL unit tests, Playwright visual/hydration checks, and Tailwind logical styling. Triggers on "/nextjs-component-dev", "create component", "new component", "build component", or "develop component".

BIGboss248/nextjs-wordpress

>- Bootstrap, configure, and verify the complete Next.js App Router development environment, developer tooling, testing suites, MCP servers, Docker containerization, and CI/CD. Triggers on "/nextjs-dev-setup", "setup nextjs dev environment", "start a nextjs project", or "containerize nextjs app".

BIGboss248/nextjs-wordpress

>- Configure production health monitoring endpoints (/api/health), Docker Compose probes, and runtime metrics in Next.js App Router applications. Use when asked to "setup health check", "add health endpoint", "docker compose healthcheck nextjs", "configure health monitor", or "/nextjs-healthcheck".

BIGboss248/nextjs-wordpress

Read/write translation dictionaries (messages/[locale].json), next-intl hooks (getTranslations/useTranslations), providers (Storybook/tests/subtrees), and BiDi styling. Triggers on "/nextjs-i18n-usage", "i18n dictionary", "use translations", "read dictionary", "i18n provider", "next-intl hooks", "storybook i18n", "test i18n", "add translation keys", "localize component", "create a component", "update a component".

BIGboss248/nextjs-wordpress

>- Configure, test, and verify OpenTelemetry (OTel) observability in Next.js App Router applications. Triggers on "/nextjs-otel", "setup otel", "configure opentelemetry", "test otel", or "verify opentelemetry".

BIGboss248/nextjs-wordpress

Step-by-step workflow for designing and building Next.js App Router pages (RSC page.tsx, loading skeleton, metadata, JSON-LD schema, and dynamic static params). Triggers on "/nextjs-page-dev", "create page", "new page", "develop page", "build route", or "implement page".

BIGboss248/nextjs-wordpress

>- Orchestrate end-to-end planning for Next.js App Router projects, generating canonical specifications, design systems, and a 7-phase modular implementation roadmap in docs/plan/. Triggers on "/nextjs-plan", "plan a nextjs project", "plan nextjs app", "create nextjs project plan", "outline nextjs architecture", or "generate plan".

BIGboss248/nextjs-wordpress

Workflow and engineering standards for crafting co-located Storybook CSF3 stories ([ComponentName].stories.tsx) with interactive controls, action spies, and 4 canonical theme variants.

BIGboss248/nextjs-wordpress

>- Build Next.js e-commerce frontends backed by WooCommerce APIs, handling ISR catalogs, cart sessions, and JWT authentication. Use when building or querying Next.js stores with WooCommerce.

BIGboss248/nextjs-wordpress

Self-correcting rules engine and feedback loop that learns from user corrections, mistakes, and project-specific constraints by maintaining a persistent autofix ruleset. Scans learned rules before starting any task, resolves conflicts, and automatically appends new rules upon corrections. Triggers on user corrections ("no, do it this way", "never do X", "always use Y"), /learn, "self repair", "add rule", "update rules", or when diagnosing assumptions and bugs. CRITICAL ALWAYS-ACTIVE LIFECYCLE SKILL. Must always be kept in context, loaded at session start, and consulted before starting ANY task to read and apply active constraints from autofix.json. MUST ALWAYS be triggered immediately whenever the user provides ANY correction, preference, criticism, rejection of an approach, or adjustment ("no", "don't do X", "use Y", "remember", "prefer"), or when any mistake/bug is identified. Automatically and immediately formulates and appends the new imperative rule to the project's autofix.json ruleset file.

BIGboss248/nextjs-wordpress

Setup, automate, and execute SEO audits, CI/CD pre-push/pre-deploy checks, and ranking optimizations using the seo CLI and MCP server.

BIGboss248/nextjs-wordpress

End-to-end repository onboarding and development environment setup skill. Scans repository structure, configures project metadata (docs/project.json), sets up the codebase-memory-mcp code intelligence knowledge graph server (in workspace mcp.json and globally for AGY only), configures git hooks with Husky and Commitlint, establishes multi-stage production Docker containerization, and automates credit-optimized Release Please CI/CD with multi-arch (AMD64 & ARM64) GHCR package deployment. Triggers on "/setup-repository", "setup repository", "setup repo", "initialize repository", "new repo setup", or when preparing any repository for development and AI agent workflows.

BIGboss248/nextjs-wordpress

AI screen scaffolding, layout generation, and variant exploration workflow powered by Google Stitch (StitchMCP). Consumes a component design specification (docs/design/components/[page name]/[component name]/design-spec.md), verifies and reuses the central Stitch project in docs/project.json (or creates/persists one if absent), seeds the project's design system into Stitch, synthesizes layout prompts to generate a screen and create one variant of the given design spec file, downloads and saves Stitch JPG screenshots and HTML code files directly into docs/design/components/[page name]/[component name]/stitch/ using binary-safe PowerShell Invoke-WebRequest, outputs image prompts to the user if visual assets are needed (without calling generate_image to conserve tokens), updates design-spec.md with Stitch layout benchmarks, and audits asset download integrity with an independent subagent. Triggers on "/stitch-design", "generate stitch screen", "create stitch variant", "scaffold screen with stitch", or "stitch...

Verwandte Skills

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community