本文へ移動
cccskills
無料GitHub で公開

mcp-ai-wpoos-content-graph-spa

Operational guide for the NV oOS Content Graph ↔ Pro SPA surface — the

インストール方法を見る

含まれるファイル(1)

  • SKILL.md7.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

NV oOS Content Graph ↔ SPA Surface

Operational guide for the knowledge-graph page shipped by PR #6998 (2026-10-10). The companion proposal for npm packaging the shared pieces is docs/project/proposals/065-content-graph-npm-packages-proposal.md.

When to use this skill

  • Updating the #/knowledge-graph page (spa-v2 or the standalone Vite app)
  • Re-syncing the vendored explorer after plugins/nvoos-content-graph/assets/js/ changes upstream
  • Adding/extending the plugin's REST routes or auth for headless clients
  • Triaging "PHPUnit Content Graph" / "Build Content Graph Plugin" CI failures
  • Answering "does the SPA graph page work on site X" / "what auth modes does it need"

Shared mechanics live in the sibling skills: porting/UI/testing gotchas in mcp-ai-wpoos-spa-ui (vendored-upstream section), the plugin's PHPUnit Docker recipe in mcp-ai-wpoos-test-suite (standalone plugin suites section).

Surface map

PieceLocation
Canonical explorer JS/CSSplugins/nvoos-content-graph/assets/js/{content-graph-admin,content-graph-theme,content-graph-icons}.js + assets/css/content-graph-admin.css
SPA vendored copiesaddons/pro/assets/spa-v2/src/features/knowledge-graph/upstream/ (byte-identical body + documented wrapper delta)
React pageaddons/pro/assets/spa-v2/src/features/knowledge-graph/KnowledgeGraphPage.tsx (+ knowledge-graph.css, __tests__/)
Route + commandrouter.tsx (/knowledge-graph), useBootstrap.ts (nav-knowledge-graph)
Endpoints typeaddons/pro/assets/spa-v2/src/api/config.ts (ProSpaEndpoints.contentGraph)
Plugin-side endpointaddons/pro/includes/class-wp-mcp-ai-pro-spa-config.php (admin+non-guest only, class_exists( 'NvoosContentGraph\Plugin' ) gated)
Standalone app endpointexamples/nvoos-pro-spa-vite/src/runtime-config.ts (buildEndpoints())
Standalone aliases + shimsexamples/nvoos-pro-spa-vite/vite.config.ts (jquery/cytoscape/fcose aliases), src/shims/cytoscape-fcose.d.ts, tsconfig.json paths (jquery → @types/jquery, cytoscape → @types/cytoscape)
Plugin REST + authplugins/nvoos-content-graph/src/Rest/Controller.php
CI.github/workflows/phpunit-content-graph.yml, .github/workflows/build-nvoos-content-graph.yml (plugin-check job)

REST + auth contract

Namespace nvoos-content-graph/v1. Read routes (/graph, /nodes, /nodes/{id}, /edges, /search, /retrieve, /resolve, /graph/visual-config) accept, via checkReadPermission():

  1. logged-in user with read (cookie / Application Password),
  2. an NV oOS assistant credential — Authorization: Bearer cred_XXXXX.SECRET or the raw header form, gated by the wp_mcp_ai_accept_raw_credential_header filter, validated through \WP_MCP_AI_Credentials::validate_token() (must be GLOBAL-namespace-qualified inside the namespaced controller — see test-suite pattern 70), or
  3. a base-plugin guest token.

A credential-format token that FAILS validation is a definitive 401 (no fall-through); requests without a credential fall through to the guest check. Write routes (/build, /export, /sources*) stay manage_options-only — credentials can never rebuild or mutate. Standalone installs (no base plugin) are unaffected (class_exists() guarded).

GET /graph/visual-config (1.1.0+) returns { visual, presets, height, max_nodes } — the shape the SPA page assembles into window.nvoosContentGraphAdmin. The SPA page shows an unavailable/error state without it; the version hint in the page text says "1.1.0 or later".

CORS: cross-origin SPA modes need the app origin in cors_allowed_origins AND /nvoos-content-graph/v1 in wp_mcp_ai_cors_guard_route_prefixes (default scope is /mcp-ai/v1 only). Cookie mode needs neither.

Vendored explorer sync discipline

When plugins/nvoos-content-graph/assets/js/content-graph-admin.js (or the theme/icons/CSS) changes upstream:

  1. Copy the file(s) into .../knowledge-graph/upstream/ (overwrite).
  2. Re-apply ONLY the documented wrapper delta (listed in the vendored file header): IIFE → export function initNvoosGraphExplorer( $ ), the destroyed latch, namespaced .nvoos-cg document bindings, and the destroy() + return { destroy } tail. Everything else must stay byte-identical — verify with git --no-pager diff --no-index plugins/nvoos-content-graph/assets/js/content-graph-admin.js <spa-v2>/upstream/content-graph-admin.js.
  3. Re-run the spa-v2 test suite (the page tests mock the factory — they assert the contract, not the internals) and the standalone build. Careful: the monorepo standalone build can stay green while the MIRROR build fails — spa-v2 resolves its own node_modules in the monorepo, but the sync workflow ships addons/ without it. Every spa-v2 dep needs a tsconfig paths entry (typed) or a src/shims/ ambient declaration (untyped) in the standalone app; PR #7000 added the sync/deploy build-verify gates that catch this in CI.
  4. Note the sync in the plugin's CHANGELOG if the change is user-visible.

Adding a NEW id to the explorer markup requires the same id in the page's JSX toolbar (mirror SettingsPage.php), or the delegated document handlers silently never fire.

CI notes

  • Both content-graph workflows use shivammathur/setup-php with tools: wp-cli, which flakes intermittently ("Could not setup wp-cli") without failing the step — each has an "Ensure WP-CLI is available" phar-fallback step; keep it when adding steps (see test-suite skill).
  • The plugin's own test suites run via the test-suite skill's Docker recipe (isolated DB wordpress_test_nvooscg pattern); expected sizes ~163 Unit + ~27 Integration tests.

PR state (2026-10-11)

  • #6998 add/content-graph-spa-page — the page + plugin auth/route + CI hardening (this surface's origin PR). Merged — the plugin half ships in nvoos-content-graph 1.0.11 (visual-config route + bearer auth).
  • #6999 add/standalone-spa-login-rescope — wp-login proxy re-scoping. Merged (README wording + alias block conflicts resolved in-window).
  • #7000 add/standalone-spa-graph-typecheck — mirror-only TS2307 fix (jquery/cytoscape tsconfig paths) + build-verify gates in the sync/deploy workflows. Merged.
  • #7002 — knowledge-graph auth fix in the standalone SPA (fetch-wrapper ajaxPrefilter mirrors auth headers across all four modes). Merged.
  • Release note: the plugin-side surface (read-only GET /graph/visual-config
    • assistant-credential bearer auth on read routes) shipped in nvoos-content-graph 1.0.11 (wp.org upload prepared 2026-10-11; see plugins/nvoos-content-graph/WPORG-REVIEW-18POINT-SIGNOFF.md).

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

Control a headless browser to navigate URLs, click elements, fill forms, extract content from JavaScript-rendered pages, take screenshots, and automate end-to-end web workflows.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

Review code for quality, simplicity, and maintainability. Identifies unnecessary abstractions, duplicated logic, oversized functions, missing error handling, and naming issues — then fixes them automatically before presenting the result.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

WooCommerce store operations through NV oOS Pro — product research, catalog cross-referencing, inventory lookups, and Shopify or Flowhub comparisons where integrations are configured.

日本語の概要は準備中です。原文の説明を表示しています。

nvdigitalsolutions/mcp-ai-wpoos72026年10月13日 更新

nvdigitalsolutions のスキルをすべて見る

このスキルの問題を報告する