Communitygithub.com

bigboss248/nextjs-wordpress

Construa front-ends de e-commerce Next.js com APIs WooCommerce, gerenciando catálogos ISR, sessões de carrinho e autenticação JWT. Use ao construir ou consultar lojas Next.js com WooCommerce.

O que é nextjs-wordpress?

Esta skill fornece um guia operacional completo para integrar aplicações Next.js (App Router) com um backend WooCommerce headless, usando WPGraphQL, WooGraphQL e autenticação JWT. Ela cobre desde a configuração inicial do ambiente e cliente até pipelines complexos como catálogo público de produtos com ISR/SSG, autenticação de usuário com cookies seguros, dados protegidos de perfil e histórico de pedidos, e gerenciamento de sessão de carrinho com ponte para checkout nativo. A skill destaca casos de borda críticos, como o uso correto de fragmentos polimórficos para produtos variáveis e simples, e como evitar a desotimização estática/dinâmica no Next.js. Ela é útil para desenvolvedores que precisam construir lojas online escaláveis, com suporte a ISR, autenticação e integração com gateways de pagamento WooCommerce.

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

Perguntar na sua IA favorita

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

Documentação

Integração Next.js WooCommerce (nextjs-woocommerce)

Guia operacional e checklist para arquitetar, consultar e integrar aplicações Next.js App Router com um backend WooCommerce headless via WPGraphQL, WooGraphQL e Autenticação JWT.


Pré-requisitos e Referências da Documentação

  • Projeto Next.js 14+ inicializado com App Router e TypeScript.
  • Backend WooCommerce ativo com WPGraphQL, WooGraphQL e wp-graphql-jwt-authentication.
  • Para esquemas API completos e padrões de código Next.js, consulte nextjs-woocommerce-reference.md.
  • Para implementação reutilizável de cliente de busca de dados, veja woocommerce-fetcher.ts.

Checklist de Implementação Passo a Passo

flowchart TD
    S1["1. Configuração de Ambiente e Cliente"] --> S2["2. Catálogo Público de Produtos (ISR/SSG)"]
    S2 --> S3["3. Autenticação de Usuário (JWT + Cookies)"]
    S3 --> S4["4. Perfil Protegido e Histórico de Pedidos"]
    S4 --> S5["5. Sessão de Carrinho e Ponte de Checkout Nativo"]

Fase 1: Configuração de Ambiente e Cliente

  • Configurar Variáveis de Ambiente:
    • Adicione NEXT_PUBLIC_WORDPRESS_API_URL=https://sua-loja.com/graphql ao .env.example e .env.development.
    • Adicione NEXT_PUBLIC_WORDPRESS_URL=https://sua-loja.com para redirecionamentos de checkout.
  • Configurar Buscador Universal:

Fase 2: Catálogo Público de Produtos e Taxonomias

  • Navegação por Categoria: Consulte productCategories com hideEmpty: true para cabeçalhos e menus de categoria.
  • Arquivo de Grade de Produtos: Consulte products usando fragmentos de união (... on SimpleProduct, ... on VariableProduct). Configure next: { revalidate: 300, tags: ['products'] }.
  • Página de Detalhe do Produto: Pré-renderize rotas dinâmicas (app/products/[slug]/page.tsx) com generateStaticParams() consultando todos os slugs de produtos.

Fase 3: Pipeline de Autenticação JWT

  • Mutation de Login: Implemente Server Action executando login(input: { username, password }).
  • Armazenamento de Cookie: Armazene o authToken retornado em um cookie seguro HttpOnly (auth_token).
  • Ligação de Sessão: Se o cliente retornar sessionToken, armazene no cookie wc_session.
  • Logout: Limpe os cookies de autenticação no logout do usuário.

Fase 4: Dados Protegidos do Usuário e Pedidos

  • Perfil do Cliente: Consulte viewer { id name email } passando Authorization: Bearer <authToken>.
  • Histórico de Pedidos: Consulte customer { orders { nodes { id orderNumber total status } } } com cache: 'no-store'.

Fase 5: Gerenciamento de Carrinho e Estratégia de Checkout

  • Estado do Carrinho: Capture e persista o cabeçalho woocommerce-session retornado nas mutations addToCart.
  • Ponte de Checkout Nativo:
    • Redirecione usuários para https://sua-loja.com/checkout para aproveitar os gateways de pagamento nativos do WooCommerce (ZarinPal, Mellat, Stripe), logística regional e selos de conformidade sem reescrever gateways personalizados.

Casos de Borda e Armadilhas Conhecidas

  1. Desotimização Estática vs. Dinâmica: Ler cookies no layout raiz ou páginas de produto muda o Next.js para modo dinâmico SSR completo. Leia cookies de autenticação apenas dentro de Server Actions, Route Handlers ou subárvores isoladas do painel de conta (app/account/...).
  2. Fragmentos Polimórficos: Consultas diretas como products { nodes { price } } falharão na validação no WooGraphQL. Sempre envolva preços e variações em ... on SimpleProduct e ... on VariableProduct.
  3. Perda de Sessão: Ao adicionar itens ao carrinho, não reenviar o cabeçalho woocommerce-session cria um novo carrinho vazio a cada mutation.
  4. CORS no Endpoint GraphQL: Certifique-se de que o WordPress envie os cabeçalhos Access-Control-Allow-Origin e Access-Control-Allow-Headers: Authorization, Content-Type, woocommerce-session para o domínio do seu Next.js.

Verificação e Testes de Pré-voo

  • pnpm build é bem-sucedido com a geração estática das páginas de produto.
  • Teste se o formulário de login emite auth_token e redireciona para o painel.
  • A página de conta renderiza os detalhes do cliente e a lista de pedidos com token válido.
  • Adicionar ao carrinho atualiza a contagem de itens do carrinho em várias requisições do 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...

Habilidades Relacionadas