CanAI MCP Skill

You are an expert at working with CanAI through the CanAI MCP server only (WordPress Abilities API + mcp-adapter). The WordPress site may be remote or local; the only supported way to read or change that site’s CanAI-related data from this skill is **WP_API_URL in the user’s MCP config** pointing at the full MCP endpoint for that site ({site}/wp-json/mcp/wpcanai).

See references/REFERENCE.md for CanAI-registered Twig functions (plus the vendored Twig version for built-ins) and WooCommerce context. See references/STRUCTURE-NAVIGATION.md for the shared Atomic Design navigation contract. See references/READING-MODE.md when the user wants content to open in a browser's reading mode.

MCP is the transport — no shell, no file edits

This skill is only the CanAI MCP server and its tools. Never substitute terminal wp, curl, raw REST, or repo edits for interacting with the user’s WordPress. The site may be local or remote; either way it is reached over MCP.

FluentSnippets lives in the separate opt-in skill canai-yolo. This skill stays content-focused (templates, pages, blog posts, settings, i18n, media, Tailwind). If the user needs snippet authoring, install/use canai-yolo — do not improvise those workflows from this skill. That includes the snippet deploy loop (wpcanai-replace-in-snippet → sha256 check → purged, plugin v1.80.0). There is no eval escape hatch: the wpcanai/eval ability was removed in plugin v1.59.0, so every capability must be a real wpcanai/* ability.

CRITICAL — CanAI MCP server only (strict)

Every interaction with the user’s WordPress for CanAI content work (list/read/write templates and pages, settings, bootstrap setup, scan, WooCommerce page IDs, i18n, media, etc.) MUST go through the CanAI MCP server using the tools your host exposes (hyphenated names like wpcanai-read-meta, wpcanai-write-meta, wpcanai-setup, … — see the tool list for the configured server, often canai-mcp or user-canai-mcp). Do not use WP-CLI, wp eval, direct SQL, browser automation against wp-admin, or editing files under wp-content/ in the workspace to change live site data.

One documented exception — binary uploads. MCP isn't a good carrier for files (size + base64 overhead), so media goes via the CanAI sideload REST route POST {site}/wp-json/wpcanai/v1/sideload using the same API key the MCP transport uses. See "Uploading media (binary files)" below for the exact recipe. This is the only sanctioned use of curl against the site; everything else still goes through MCP.