Communitygithub.com

BIGboss248/nextjs-wordpress

Habilita la lectura/escritura de diccionarios de traducción (messages/[locale].json), los hooks next-intl (getTranslations/useTranslations), proveedores (Storybook/pruebas/subárboles) y estilos BiDi. Se activa con frases como "/nextjs-i18n-usage", "diccionario i18n", "usar traducciones", "leer diccionario", "proveedor i18n", "hooks next-intl", "storybook i18n", "probar i18n", "agregar claves de traducción", "localizar componente", "crear un componente", "actualizar un componente".

¿Qué es nextjs-wordpress?

Esta skill, denominada `nextjs-i18n-usage`, proporciona pautas de ingeniería, hooks y patrones de proveedores para consumir traducciones de `next-intl` en aplicaciones Next.js, cubriendo tanto componentes del servidor (RSC) como del cliente. Su propósito es eliminar cualquier texto codificado directamente, obligando a que todo el contenido visible se gestione exclusivamente mediante diccionarios de traducción ubicados en `messages/[locale].json`. La skill define un contrato de cero-hardcode que prohíbe cadenas literales en JSX y requiere la sincronización simultánea de todas las traducciones en todos los archivos de locale antes de escribir cualquier interfaz. Incluye una tabla de referencia rápida con las APIs y hooks adecuados para cada entorno: `getTranslations` para RSC, `useTranslations` para componentes cliente, `NextIntlClientProvider` para Storybook y testing, y el módulo `@/i18n/navigation` para el enrutamiento. Además, impone estándares de estilo BiDi (LTR/RTL) mediante propiedades lógicas de Tailwind (ms-, me-, text-start, etc.) y una verificación de paridad de diccionarios mediante un script PowerShell. La skill está diseñada para Cursor y entornos de desarrollo basados en reglas de ingeniería de IA, y se activa con comandos como "/nextjs-i18n-usage" o frases relacionadas con diccionarios i18n, proveedores y componentes. En resumen, esta skill garantiza una internacionalización robusta, sin hardcoding, con soporte completo para direccionalidad y pruebas, unificando el flujo de trabajo de traducciones en Next.js.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-i18n-usage
Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

Diccionarios y Proveedores i18n de Next.js (nextjs-i18n-usage)

Estándares de ingeniería, hooks y patrones de proveedores para consumir traducciones de next-intl en Componentes de Servidor React (RSC), Componentes de Cliente, historias de Storybook y entornos de prueba.

[!TIP] Patrones de Implementación: Consulta references/examples.md para ejemplos de código completos (RSC, formularios de cliente, selectores de idioma, decoradores de Storybook y envoltorios de prueba). Ejecución Rápida: Delega la validación de diccionarios o la sincronización de claves a un subagente ligero (Model: 'flash').

1. Contrato de Cero-Hardcode

  • Cero Texto Codificado: Nunca escribas etiquetas visibles para el usuario, marcadores de posición o cadenas de respaldo en JSX.
  • Sin Objetos Mock: Los diccionarios mock en el archivo (por ejemplo const DEFAULT_CONTENT = {...}) están PROHIBIDOS.
  • Sincronización Síncrona: Al agregar/actualizar copia de la UI, inserta traducciones auténticas en TODOS los archivos de locale en messages/[locale].json (ej. messages/en.json y messages/fa.json) antes de escribir JSX.

2. Referencia Rápida de APIs y Hooks

Entorno / ObjetivoHook / APISintaxis de Ejemplo
Componente de Servidor (RSC)getTranslationsconst t = await getTranslations('namespace');
Formateador de ServidorgetFormatterconst format = await getFormatter(); format.dateTime(...)
Metadatos DinámicosgetTranslationsexport async function generateMetadata({ params }) { ... }
Componente de ClienteuseTranslationsconst t = useTranslations('namespace');
Formateador de ClienteuseFormatterconst format = useFormatter(); format.number(...)
Texto Enriquecido (Cliente)t.richt.rich('terms', { link: (c) => <Link href="/t">{c}</Link> })
Navegación@/i18n/navigationimport { Link, useRouter, usePathname } from '@/i18n/navigation';
Vista Previa de StorybookNextIntlClientProviderEnvuelve el decorador de vista previa con <NextIntlClientProvider locale="en" messages={enMessages}>
Pruebas Unitarias (Jest)renderWithIntlEnvuelve el renderizado con <NextIntlClientProvider locale="en" messages={messages}>

3. Estándares BiDi (LTR / RTL) y de Estilo

  1. Solo Propiedades Lógicas de Tailwind:
    • Prohibido: ml-*, mr-*, pl-*, pr-*, left-*, right-*, text-left, text-right
    • Requerido: ms-*, me-*, ps-*, pe-*, start-*, end-*, text-start, text-end
  2. Dirección Dinámica: <html dir="rtl"> dinámico para fa/ar y dir="ltr" para en.

4. Anti-patrones y Errores Comunes

ErrorCausa RaízSolución
useTranslations en RSCLos hooks no pueden ejecutarse en componentes de servidor asíncronosUsa await getTranslations('ns')
getTranslations en ClienteFunción asíncrona solo de servidorUsa useTranslations('ns') con "use client"
"No se encontró contexto intl"Proveedor faltante en Storybook/pruebasEnvuelve la historia/prueba en <NextIntlClientProvider>
Respaldo CodificadoEj. `t('btn')
next/link sin procesarElimina el prefijo de locale al cambiar de rutaUsa Link de @/i18n/navigation

5. Verificación de Paridad

Ejecuta la verificación de paridad de diccionarios:

pwsh .agents/skills/nextjs-i18n-usage/scripts/verify-dictionaries.ps1

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

Bootstrap, configure, and verify next-intl App Router internationalization (proxy.ts/middleware.ts, next/root-params, [locale] layout, routing). Triggers on "/nextjs-i18n-setup", "setup i18n", "install next-intl", "configure next-intl", "add internationalization", "setup locale routing", "migrate to [locale]".

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...

Skills relacionados

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