Communitygithub.com

BIGboss248/nextjs-wordpress

构建由 WooCommerce API 驱动的 Next.js 电子商务前端,处理 ISR 目录、购物车会话和 JWT 认证。适用于构建或查询基于 WooCommerce 的 Next.js 商店。

nextjs-wordpress 是什么?

此技能为开发人员提供了一份完整的操作手册和检查清单,用于使用 Next.js App Router 与无头 WooCommerce 后端集成,通过 WPGraphQL、WooGraphQL 和 JWT 认证实现。它涵盖了从环境配置到购物车管理和原生结账桥接的五个实施阶段。该技能支持使用增量静态再生(ISR)和静态生成(SSG)构建高性能的公开产品目录,并实现安全的 JWT 认证管道,用于管理用户会话和保护客户数据(如个人资料和订单历史)。关键的边缘情况处理包括避免在根布局中读取 Cookie 以防止全 SSR 模式降级、在 GraphQL 查询中使用多态片段(例如 `... on SimpleProduct`)以确保正确解析,以及持久化 `woocommerce-session` 头以防止购物车会话丢失。该技能适用于 Claude Code 和 Cursor 等平台,并提供了可参考的示例文件,如 `woocommerce-fetcher.ts` 和 `nextjs-woocommerce-reference.md`。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

Next.js WooCommerce 集成 (nextjs-woocommerce)

用于架构、查询和集成 Next.js App Router 应用与无头 WooCommerce 后端(通过 WPGraphQL、WooGraphQL 和 JWT 认证)的操作手册和检查清单。


前提条件与文档参考

  • 已初始化 Next.js 14+ 项目,使用 App Router 和 TypeScript。
  • 活跃的 WooCommerce 后端,安装了 WPGraphQL、WooGraphQL 和 wp-graphql-jwt-authentication。
  • 有关完整的 API 模式和 Next.js 代码模式,请参考 nextjs-woocommerce-reference.md。
  • 有关可重用的数据获取客户端实现,请参见 woocommerce-fetcher.ts。

分步实施检查清单

flowchart TD
    S1["1. 环境与客户端设置"] --> S2["2. 公开产品目录 (ISR/SSG)"]
    S2 --> S3["3. 用户认证 (JWT + Cookies)"]
    S3 --> S4["4. 受保护的个人资料与订单历史"]
    S4 --> S5["5. 购物车会话与原生结账桥接"]

阶段 1:环境与客户端配置

  • 配置环境变量:
    • 将 NEXT_PUBLIC_WORDPRESS_API_URL=https://your-store.com/graphql 添加到 .env.example 和 .env.development。
    • 为结账重定向添加 NEXT_PUBLIC_WORDPRESS_URL=https://your-store.com。
  • 设置通用 Fetcher:

阶段 2:公开产品目录与分类

  • 类别导航:为页眉和类别菜单查询 productCategories,设置 hideEmpty: true。
  • 产品网格列表:使用联合片段(... on SimpleProduct,... on VariableProduct)查询 products。配置 next: { revalidate: 300, tags: ['products'] }。
  • 产品详情页:使用 generateStaticParams() 查询所有产品 slug,预渲染动态路由(app/products/[slug]/page.tsx)。

阶段 3:JWT 认证管道

  • 登录 Mutation:实现 Server Action,执行 login(input: { username, password })。
  • Cookie 存储:将返回的 authToken 存储在安全的 HttpOnly cookie(auth_token)中。
  • 会话绑定:如果客户返回 sessionToken,则将其存储在 wc_session cookie 中。
  • 登出:用户登出时清除认证 cookies。

阶段 4:受保护的用户数据与订单

  • 客户个人资料:使用 Authorization: Bearer <authToken> 头查询 viewer { id name email }。
  • 订单历史:使用 cache: 'no-store' 查询 customer { orders { nodes { id orderNumber total status } } }。

阶段 5:购物车管理与结账策略

  • 购物车状态:捕获并持久化 addToCart mutations 返回的 woocommerce-session 头。
  • 原生结账桥接:
    • 将用户重定向到 https://your-store.com/checkout,以利用原生 WooCommerce 支付网关(如 ZarinPal、Mellat、Stripe)、区域物流和合规认证,无需重写自定义网关。

边界情况与已知陷阱

  1. 静态与动态优化降级:在根布局或产品页面中读取 Cookie 会使 Next.js 切换到完全 SSR 动态模式。仅应在 Server Actions、Route Handlers 或隔离的账户仪表板子树(app/account/...)中读取认证 cookies。
  2. 多态片段:直接的查询如 products { nodes { price } } 会在 WooGraphQL 中通过验证失败。始终将定价和变体包装在 ... on SimpleProduct 和 ... on VariableProduct 中。
  3. 会话丢失:向购物车添加商品时,未能重新发送 woocommerce-session 头会导致每次 mutation 都创建一个新的空购物车。
  4. GraphQL 端点的 CORS:确保 WordPress 为您的 Next.js 域名发送 Access-Control-Allow-Origin 和 Access-Control-Allow-Headers: Authorization, Content-Type, woocommerce-session 头。

验证与起飞前测试

  • pnpm build 成功,产品页面静态生成。
  • 测试登录表单发出 auth_token 并重定向到仪表板。
  • 账户页面使用有效令牌渲染客户详情和订单列表。
  • 添加到购物车操作在多个客户端请求中更新购物车商品数量。

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

相关技能