Communitygithub.com

BIGboss248/nextjs-wordpress

配置、測試和驗證 Next.js App Router 應用程式中的 OpenTelemetry (OTel) 可觀測性。

nextjs-wordpress 是什麼?

這個技能提供了一個模組化、可用於生產環境的工作流程,用於在 Next.js App Router 應用程式中配置、測試和驗證 OpenTelemetry 追蹤。它標準化了單一開關 (kill switch) 的使用,防止 `@vercel/otel` 的初始化錯誤,並自動化追蹤驗證流程。技能支援 `pnpm`、`bun` 和 `npm` 等套件管理工具,並透過一組逐步執行的 Runbook 引導使用者完成專案檢查、相依性安裝、`instrumentation.ts` 部署、環境變數設定,以及最終的驗證與測試。此外,它也詳細說明了常見的邊緣案例與陷阱,例如 `@vercel/otel` 的字串真值錯誤,並要求輸出結構化的驗證報告。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

Next.js OpenTelemetry 可觀測性技能 (nextjs-otel)

一個模組化、可用於生產環境的工作流程,用於在 Next.js App Router 應用程式中配置、測試和驗證 OpenTelemetry 追蹤,標準化單一開關的使用,防止 @vercel/otel 初始化錯誤,並自動化追蹤驗證。


工作流程概覽

flowchart TD
    A["1. 專案評估<br/>(App Router & package.json)"] --> B["2. 安裝相依套件<br/>(@vercel/otel & @opentelemetry/api)"]
    B --> C["3. 部署 instrumentation.ts<br/>(registerOTel + onRequestError)"]
    C --> D["4. 配置環境變數<br/>(.env.example & .env.local)"]
    D --> E["5. 驗證與測試工具<br/>(模擬 Collector 與開關)"]

逐步執行 Runbook

請依序執行以下檢查清單,以配置和驗證 OpenTelemetry 可觀測性:

1. 專案探索與相依性檢查

  • 檢查專案結構:確認 package.json 中的 Next.js App Router 版本和套件管理器 (pnpm, bun, npm)。
  • 定位 Instrumentation 根目錄:檢查專案使用的是根目錄的 instrumentation.ts 還是 src/instrumentation.ts。
  • 檢視架構標準:參閱 architectural-standards.md 了解單一開關規範和執行邊界。

2. 相依性安裝

  • 安裝核心遙測套件:
    pnpm add @vercel/otel @opentelemetry/api
    

3. 部署 instrumentation.ts

  • 建立 Instrumentation 檔案:將 instrumentation.ts.template 部署至根目錄或 src/。
  • 套用真值保護:確保 register() 在 process.env.OTEL_SDK_DISABLED 非嚴格等於 "true" 時將其刪除,以避免 @vercel/otel 的布林值評估錯誤。
  • 串接錯誤追蹤:確保 onRequestError() 能將 next.error.digest、路由路徑和 HTTP 中繼資料擷取至活動跨度中。

4. 配置環境變數

  • 更新環境範本:使用 env.otel.template 將 OpenTelemetry 配置注入 .env.example 和 .env.local。
  • 設定服務名稱與協定:配置 OTEL_SERVICE_NAME、OTEL_EXPORTER_OTLP_ENDPOINT 和 OTEL_EXPORTER_OTLP_PROTOCOL=http/json。

5. 驗證與測試

  • 啟動模擬 OTLP Collector:根據 verification-and-testing.md 在連接埠 4318 上啟動測試 collector:
    node .agents/skills/nextjs-otel/scripts/mock_collector.js
    
  • 驗證活動追蹤 (OTEL_SDK_DISABLED=false):觸發測試請求 (curl http://localhost:3000/) 並驗證 POST /v1/traces 批次是否回傳 HTTP 200 OK。
  • 驗證開關 (OTEL_SDK_DISABLED=true):確認 Next.js 伺服器日誌顯示 [OTel] Instrumentation hook skipped 且匯出 0 筆追蹤。
  • 輸出驗證報告:產生 Markdown 摘要報告。

邊緣案例與已知 AI 陷阱

[!WARNING]

  • @vercel/otel 字串真值錯誤:@vercel/otel 評估 !!process.env.OTEL_SDK_DISABLED。在 JavaScript 中,Boolean("false") 等於 true。若不將非 'true' 的 process.env.OTEL_SDK_DISABLED 刪除,設定 OTEL_SDK_DISABLED=false 會靜默地停用追蹤。
  • 次要自訂旗標:切勿在 OTEL_SDK_DISABLED 之外引入 OTEL_ENABLED。嚴格標準化使用 OTEL_SDK_DISABLED。
  • 執行邊界違規:切勿將 instrumentation.ts 或伺服器端 OpenTelemetry SDK 匯入至用戶端元件 ("use client")。
  • 鏈結指令:切勿使用鏈結指令 (&&, ||, ;)。所有設定和測試指令應單獨執行。

輸出摘要結構

完成 OpenTelemetry 設定或驗證後,輸出結構化報告:

# OpenTelemetry 驗證報告

## 狀態摘要

- **OTel 狀態**:啟用 / 停用
- **服務名稱**:<設定的服務名稱>
- **目標端點**:<設定的端點>
- **匯出器協定**:http/json | http/protobuf

## 驗證結果

| 檢查項目                 | 預期結果                 | 實際結果             | 狀態 |
| :----------------------- | :----------------------- | :------------------- | :--- |
| 初始化掛鉤               | 已註冊                   | 已註冊               | 通過 |
| 追蹤傳送 (啟用)          | POST /v1/traces (200 OK) | X 批次已接收         | 通過 |
| 開關 (停用)              | 已跳過,0 筆追蹤         | 已跳過,0 筆追蹤     | 通過 |
| 型別檢查                 | 0 錯誤                   | 0 錯誤               | 通過 |

參考指南與範本

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

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

相關技能