Communitygithub.com

WooCommerce Headless API (headless-woocommerce-api)

Configura y consulta APIs de WooCommerce incluyendo WPGraphQL, WooGraphQL y autenticación JWT para frontends headless. Útil al conectar Next.js con WooCommerce o al obtener datos del catálogo de la tienda.

¿Qué es WooCommerce Headless API (headless-woocommerce-api)?

Esta habilidad proporciona una guía completa para configurar, consultar y asegurar las APIs backend de WooCommerce (WPGraphQL y REST) con el objetivo de impulsar aplicaciones frontend desacopladas como Next.js y Remix. Abarca la instalación de plugins esenciales como WPGraphQL y WooGraphQL, la siembra de datos de catálogo de prueba, y la configuración de autenticación mediante JWT o login headless. La guía detalla cómo realizar consultas a datos públicos de la tienda, manejar sesiones de clientes mediante el encabezado 'woocommerce-session', y proteger perfiles de usuario con tokens de autorización. También incluye pautas para la integración con Next.js, como el uso de SSG/ISR y la gestión de carritos de compra en el lado del cliente, así como alertas sobre errores comunes como la falta de uso de fragmentos de unión en consultas de productos o la omisión del encabezado de sesión.

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

Preguntar en tu IA favorita

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

Documentación

API WooCommerce Headless (headless-woocommerce-api)

Guía de orquestación para configurar, consultar y asegurar las APIs backend de WooCommerce (WPGraphQL y REST) para impulsar aplicaciones frontend desacopladas (Next.js, Remix, móviles).


Requisitos y Precondiciones

  • WordPress instalado con el plugin WooCommerce activo.
  • Endpoint GraphQL accesible (por defecto: https://tu-tienda.com/graphql).
  • Para consultas profundas y ejemplos técnicos, revisa headless-api-reference.md.
  • Para la configuración del cliente frontend, inspecciona storefront-client.ts.

Lista de Verificación de Ejecución Paso a Paso

flowchart TD
    S1["1. Instalar WPGraphQL y WooGraphQL"] --> S2["2. Sembrar datos de catálogo (mock / real)"]
    S2 --> S3["3. Configurar autenticación (JWT / OAuth)"]
    S3 --> S4["4. Verificar esquema con GraphiQL"]
    S4 --> S5["5. Conectar consultas de cliente en Next.js"]

Etapa 1: Despliegue de Plugins Backend

  • Instalar WPGraphQL Core:
    • Instala y activa wp-graphql desde el directorio de plugins de WordPress.
    • Verifica que el endpoint esté activo: GET/POST /graphql.
  • Instalar la Extensión WooGraphQL:
    • Descarga e instala wp-graphql-woocommerce.
    • Valida que los tipos (Product, ProductCategory, Cart, Customer) aparezcan en el esquema GraphQL.
  • Sembrar Datos de Prueba:
    • Ejecuta el importador CSV mediante Herramientas → Importar → Productos WooCommerce (CSV) usando sample-data/sample_products.csv.

Etapa 2: Configurar Autenticación Headless

  • Opción A: JWT Auth (wp-graphql-jwt-authentication):
    • Sube y activa wp-graphql-jwt-authentication.
    • Genera un secreto de 64 caracteres (openssl rand -base64 48 | tr -dc 'A-Za-z0-9_#%+=@!' | head -c 64 o equivalente en PowerShell).
    • Inyéctalo al contenedor (docker exec -it <contenedor> sed -i ... /var/www/html/wp-config.php), agrégalo a .env (GRAPHQL_JWT_AUTH_SECRET_KEY), o directamente a wp-config.php:
      define( 'GRAPHQL_JWT_AUTH_SECRET_KEY', 'tu-secreto-fuerte-aleatorio' );
      
  • Opción B: Login Headless (wp-graphql-headless-login):
    • Úsalo si se requiere OAuth 2.0 externo / inicio de sesión social (Google, GitHub).
    • Configura los proveedores mediante filtro o ajustes de administración.

Etapa 3: Consultar Datos de la Tienda

  • Catálogo Público: Consulta categorías y productos usando fragmentos de unión (... on SimpleProduct, ... on VariableProduct).
  • Sesión del Cliente: Captura el encabezado woocommerce-session en las mutaciones del carrito y pásalo en solicitudes posteriores.
  • Perfil Protegido: Pasa Authorization: Bearer <authToken> para pedidos de clientes y actualizaciones de dirección.

Etapa 4: Integración Frontend (Next.js)

  • Implementa SSG/ISR para páginas de productos estáticos usando consultas GraphQL públicas.
  • Mantén los tokens del carrito en el estado del lado del cliente (Zustand / LocalStorage) para mantener las páginas de Next.js cacheables.
  • Implementa un puente de checkout nativo: redirige a /checkout de WordPress para utilizar pasarelas de pago locales y cumplimiento con e-Namad.

Casos Límite y Errores Conocidos de IA

  1. Uniones en Consultas de Productos: Los productos de WooCommerce son polimórficos. Nunca consultes price directamente en products { nodes { price } }; debes usar condiciones de tipo (... on SimpleProduct { price }, ... on VariableProduct { price }).
  2. Encabezado de Sesión Faltante: Los elementos del carrito desaparecerán en la siguiente solicitud si el token woocommerce-session devuelto por el servidor no es almacenado y reenviado por el cliente frontend.
  3. Incompatibilidad con React de Administración: Evita plugins con paquetes Gutenberg heredados (como los paneles de configuración de wp-graphql-headless-login) si usas WordPress estricto sin pasos de compilación personalizados; opta por plugins basados en constantes como wp-graphql-jwt-authentication.
  4. Encabezados CORS: Asegúrate de que WordPress permita solicitudes desde el origen de tu frontend configurando encabezados o un proxy inverso.

Verificación y Autocomprobación

  • Ejecuta una consulta de prueba contra /graphql confirmando que productCategories y products devuelvan nodos.
  • Ejecuta la mutación login confirmando que se genere un authToken válido.
  • Confirma que se devuelva el encabezado woocommerce-session al agregar un artículo al carrito.

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

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

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