Communitygithub.com

WooCommerce Headless API (headless-woocommerce-api)

Guia para configurar, consultar e proteger APIs WooCommerce (WPGraphQL e REST) para alimentar frontends headless como Next.js e Remix.

O que é WooCommerce Headless API (headless-woocommerce-api)?

Este skill oferece uma orquestração completa para conectar aplicações frontend headless (Next.js, Remix, mobile) ao WooCommerce via APIs GraphQL e REST. Ele cobre a instalação dos plugins WPGraphQL e WooGraphQL, configuração de autenticação JWT ou OAuth, consultas otimizadas com fragments de tipos para produtos simples e variáveis, e integração com Next.js usando SSG/ISR. O skill também aborda armadilhas comuns, como a necessidade de usar condições de tipo em consultas de produtos, persistência do cabeçalho `woocommerce-session` para carrinhos, e configuração de CORS. É uma referência prática para desenvolvedores que desejam construir lojas decoupled de alto desempenho mantendo compatibilidade com gateways de pagamento locais.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Headless WooCommerce API (headless-woocommerce-api)

Guia de orquestração para configurar, consultar e proteger APIs back-end WooCommerce (WPGraphQL e REST) para alimentar aplicações frontend desacopladas (Next.js, Remix, mobile).


Pré-requisitos e Pré-condições

  • WordPress instalado com o plugin WooCommerce ativo.
  • Endpoint GraphQL acessível (padrão: https://your-store.com/graphql).
  • Para consultas aprofundadas e exemplos técnicos, veja headless-api-reference.md.
  • Para configuração do cliente frontend, inspecione storefront-client.ts.

Lista de Verificação Passo a Passo

flowchart TD
    S1["1. Instalar WPGraphQL & WooGraphQL"] --> S2["2. Semear Catálogo de Dados Simulados / Reais"]
    S2 --> S3["3. Configurar Autenticação (JWT / OAuth)"]
    S3 --> S4["4. Verificar Schema com GraphiQL"]
    S4 --> S5["5. Conectar Consultas de Cliente no Next.js"]

Estágio 1: Implantação de Plugins Back-end

  • Instalar WPGraphQL Core:
    • Instale e ative wp-graphql a partir do diretório de plugins do WordPress.
    • Verifique se o endpoint está ativo: GET/POST /graphql.
  • Instalar Extensão WooGraphQL:
    • Baixe e instale wp-graphql-woocommerce.
    • Valida que os tipos (Product, ProductCategory, Cart, Customer) aparecem no schema GraphQL.
  • Semear Dados de Teste:
    • Execute o importador CSV via Ferramentas → Importar → Produtos WooCommerce (CSV) usando sample-data/sample_products.csv.

Estágio 2: Configurar Autenticação Headless

  • Opção A: JWT Auth (wp-graphql-jwt-authentication):
    • Faça upload e ative wp-graphql-jwt-authentication.
    • Gere um segredo de 64 caracteres (openssl rand -base64 48 | tr -dc 'A-Za-z0-9_#%+=@!' | head -c 64 ou equivalente no PowerShell).
    • Injete no contêiner (docker exec -it <container> sed -i ... /var/www/html/wp-config.php), adicione ao .env (GRAPHQL_JWT_AUTH_SECRET_KEY), ou adicione diretamente ao wp-config.php:
      define( 'GRAPHQL_JWT_AUTH_SECRET_KEY', 'seu-segredo-forte-aleatorio' );
      
  • Opção B: Headless Login (wp-graphql-headless-login):
    • Use se for necessário OAuth 2.0 externo / login social (Google, GitHub).
    • Configure provedores via filtro ou configurações administrativas.

Estágio 3: Consultar Dados da Loja

  • Catálogo Público: Consulte categorias e produtos usando fragments de união (... on SimpleProduct, ... on VariableProduct).
  • Sessão do Cliente: Capture o cabeçalho woocommerce-session em mutações de carrinho e passe-o em requisições subsequentes.
  • Perfil Protegido: Passe Authorization: Bearer <authToken> para atualizações de pedidos e endereços do cliente.

Estágio 4: Integração Frontend (Next.js)

  • Implemente SSG/ISR para páginas de produtos estáticas usando consultas GraphQL públicas.
  • Mantenha tokens de carrinho no estado do lado do cliente (Zustand / LocalStorage) para manter as páginas Next.js cacheáveis.
  • Implemente Ponte de Checkout Nativo: redirecione para /checkout do WordPress para utilizar gateways de pagamento locais e conformidade com e-Namad.

Casos Limite & Armadilhas Conhecidas de IA

  1. Uniões em Consultas de Produto: Produtos WooCommerce são polimórficos. Nunca consulte price diretamente em products { nodes { price } }; você deve usar condições de tipo (... on SimpleProduct { price }, ... on VariableProduct { price }).
  2. Cabeçalho de Sessão Ausente: Itens do carrinho desaparecerão na próxima requisição se o token woocommerce-session retornado pelo servidor não for armazenado e reenviado pelo cliente frontend.
  3. Incompatibilidade com React do Admin: Evite plugins com bundles Gutenberg antigos (como painéis de configuração de wp-graphql-headless-login) se estiver usando WordPress core estrito sem etapas de construção personalizadas; opte por plugins baseados em constantes como wp-graphql-jwt-authentication.
  4. Cabeçalhos CORS: Certifique-se de que o WordPress permite requisições da sua origem frontend configurando cabeçalhos ou proxy reverso.

Verificação & Autoavaliação

  • Execute uma consulta de teste contra /graphql confirmando que productCategories e products retornam nós.
  • Execute a mutação login confirmando que um authToken válido é gerado.
  • Confirme que o cabeçalho woocommerce-session é retornado ao adicionar um item ao carrinho.

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

Habilidades Relacionadas