Communitygithub.com

Integración Next.js con WooCommerce

Construye frontends de comercio electrónico con Next.js respaldados por APIs de WooCommerce, manejando catálogos ISR, sesiones de carrito y autenticación JWT. Úsalo al construir o consultar tiendas Next.js con WooCommerce.

¿Qué es Integración Next.js con WooCommerce?

Esta habilidad proporciona una guía completa y un checklist operativo para arquitectos y desarrolladores que buscan integrar Next.js (App Router) con un backend headless de WooCommerce utilizando WPGraphQL, WooGraphQL y autenticación JWT. Es ideal para quienes desean construir aplicaciones de comercio electrónico modernas y rápidas con Next.js, aprovechando la potencia de WooCommerce como backend. Cubre desde la configuración inicial del entorno y cliente GraphQL, hasta la implementación de un catálogo de productos con ISR (Incremental Static Regeneration), autenticación de usuarios mediante JWT almacenado en cookies seguras, gestión de carritos de compra, y una estrategia de puente para el checkout nativo de WooCommerce. La habilidad también aborda casos límite importantes, como el manejo de fragmentos polimórficos en GraphQL, la prevención de la desoptimización de rutas debido a la lectura de cookies, y la correcta gestión de sesiones de carrito para evitar la pérdida de datos. Está diseñada para plataformas como Claude Code y Cursor, y su enfoque práctico permite a los desarrolladores construir tiendas en línea completas y funcionales de manera eficiente.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-woocommerce

Preguntar en tu IA favorita

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

Documentación

Integración Next.js con WooCommerce (nextjs-woocommerce)

Manual operativo y lista de verificación para arquitecturar, consultar e integrar aplicaciones Next.js con App Router y un backend headless de WooCommerce a través de WPGraphQL, WooGraphQL y autenticación JWT.


Prerrequisitos y Referencias de Documentación

  • Proyecto Next.js 14+ inicializado con App Router y TypeScript.
  • Backend WooCommerce activo con WPGraphQL, WooGraphQL y wp-graphql-jwt-authentication.
  • Para esquemas API completos y patrones de código de Next.js, consulta nextjs-woocommerce-reference.md.
  • Para la implementación reutilizable del cliente de obtención de datos, consulta woocommerce-fetcher.ts.

Lista de Verificación de Implementación Paso a Paso

flowchart TD
    S1["1. Configuración de Entorno y Cliente"] --> S2["2. Catálogo de Productos Público (ISR/SSG)"]
    S2 --> S3["3. Autenticación de Usuarios (JWT + Cookies)"]
    S3 --> S4["4. Perfil Protegido e Historial de Pedidos"]
    S4 --> S5["5. Sesión de Carrito y Puente de Checkout Nativo"]

Fase 1: Configuración del Entorno y Cliente

  • Configurar Variables de Entorno:
    • Agrega NEXT_PUBLIC_WORDPRESS_API_URL=https://tu-tienda.com/graphql a .env.example y .env.development.
    • Agrega NEXT_PUBLIC_WORDPRESS_URL=https://tu-tienda.com para las redirecciones de checkout.
  • Configurar el Recuperador Universal:
    • Implementa woocommerce-fetcher.ts compatible con almacenamiento en caché ISR y encabezados de autenticación.

Fase 2: Catálogo Público de Productos y Taxonomías

  • Navegación por Categorías: Consulta productCategories con hideEmpty: true para encabezados y menús de categorías.
  • Archivo de Cuadrícula de Productos: Consulta products usando fragmentos de unión (... on SimpleProduct, ... on VariableProduct). Configura next: { revalidate: 300, tags: ['products'] }.
  • Página de Detalle del Producto: Pre-renderiza rutas dinámicas (app/products/[slug]/page.tsx) con generateStaticParams() consultando todos los slugs de productos.

Fase 3: Pipeline de Autenticación JWT

  • Mutación de Inicio de Sesión: Implementa una Acción de Servidor que ejecute login(input: { username, password }).
  • Almacenamiento de Cookies: Almacena el authToken devuelto en una cookie HttpOnly segura (auth_token).
  • Vinculación de Sesión: Si el cliente devuelve sessionToken, guárdalo en la cookie wc_session.
  • Cierre de Sesión: Limpia las cookies de autenticación al cerrar sesión.

Fase 4: Datos y Pedidos de Usuario Protegidos

  • Perfil del Cliente: Consulta viewer { id name email } pasando Authorization: Bearer <authToken>.
  • Historial de Pedidos: Consulta customer { orders { nodes { id orderNumber total status } } } con cache: 'no-store'.

Fase 5: Gestión del Carrito y Estrategia de Checkout

  • Estado del Carrito: Captura y persiste el encabezado woocommerce-session devuelto en las mutaciones addToCart.
  • Puente de Checkout Nativo:
    • Redirige a los usuarios a https://tu-tienda.com/checkout para aprovechar las pasarelas de pago nativas de WooCommerce (ZarinPal, Mellat, Stripe), la logística regional y los sellos de cumplimiento sin necesidad de reescribir pasarelas personalizadas.

Casos Límite y Problemas Conocidos

  1. Desoptimización Estática vs. Dinámica: Leer cookies en el diseño raíz o en las páginas de producto cambia Next.js al modo dinámico SSR completo. Solo lee cookies de autenticación dentro de Acciones de Servidor, Manejadores de Rutas o subárboles aislados del panel de cuenta (app/account/...).
  2. Fragmentos Polimórficos: Las consultas directas como products { nodes { price } } fallarán en la validación en WooGraphQL. Siempre envuelve los precios y las variaciones en ... on SimpleProduct y ... on VariableProduct.
  3. Pérdida de Sesión: Al agregar artículos al carrito, no reenviar el encabezado woocommerce-session crea un carrito vacío nuevo en cada mutación.
  4. CORS en el Endpoint GraphQL: Asegúrate de que WordPress envíe los encabezados Access-Control-Allow-Origin y Access-Control-Allow-Headers: Authorization, Content-Type, woocommerce-session para tu dominio de Next.js.

Verificación y Pruebas Previas al Vuelo

  • pnpm build se completa exitosamente con la generación estática de páginas de producto.
  • Prueba que el formulario de inicio de sesión emita auth_token y redirija al panel de control.
  • La página de cuenta muestra los detalles del cliente y la lista de pedidos con un token válido.
  • Agregar al carrito actualiza el conteo de artículos del carrito en múltiples solicitudes del cliente.

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

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

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