Tool Routing
Use the narrowest host-provided capability that can produce direct evidence. Every invocation through Core remains read-only on public browse surfaces; do not submit cart or checkout actions.
Browser control
Use the host browser on the configured URL for non-destructive interactions, screenshots, responsive/DOM/accessibility inspection and console/network evidence. Avoid ambient signed-in sessions. Without browser control, continue source work and block only dependent decisions.
Workbench and repository commands
Use the host workbench for source inspection, evidence and isolated checks. Prefer target-owned rg, formatter/lint/typecheck/test/build commands, shopify theme check and non-mutating CLI validation. Inspect destructive build behavior in a disposable snapshot.
Follow repository discovery: verify Jevgrep excerpts or use direct reads/rg. Retrieval does not replace Check evaluation.
Shopify developer documentation MCP
Use current Shopify developer documentation for unfamiliar Liquid tags, filters, objects, schema, theme limits, APIs, or CLI behavior. Store Skills provisions the pinned server through the plugin-root .mcp.json:
{
"mcpServers": {
"shopify-dev-mcp": {
"command": "npx",
"args": ["-y", "@shopify/dev-mcp@1.14.2"]
}
}
}
Do not change the pin to latest. Update it only as an intentional plugin change and re-run the official plugin validator.
Public web discovery
Use current public search to discover competitor candidates only after resolving the target business profile. Inspect selected pages in a real browser. Prefer brand-owned sources and current reputable evidence; search position alone does not establish leadership or relevance.
Connected integrations
Bind every integration to the configured target before reading data:
- Use GitHub for repository files, history, pull-request context, and CI evidence.
- Use Shopify for read-only aggregate orders and abandonments plus catalog, market, discount, availability, and configuration context. Never use a write-capable action.
- Use Google Analytics for read-only metadata, funnel, and aggregate report operations. Prefer a funnel report for ordered purchase steps and a standard report for segment diagnostics.
Use the host's tool discovery when exact operation names or input schemas differ. Do not request or use search, advertising, CRM, sales, session-replay, customer-data, or other integrations. Connected read access never authorizes external mutations, and output must not expose customer- or order-level data.