Skip to main content
Shop Canvas Docs

AI skill

The optional agent path — the same sync engine as the plugin, driven from a prompt, with the token kept out of the conversation.

Shop Canvas ships two skill layers:

npx skills add zmolly/shopcanvas-skills --skill shopcanvas-setup
  • Full kit skill — the skill folder in your kit, including SKILL.md, references/ and scripts/sync-core.js (the same sync engine as the plugin). Install the whole folder using your agent’s local-skill workflow. Reading SKILL.md alone does not connect the agent to Framer.

Use Framer’s built-in Agents, Claude Code, Cursor or another supported assistant the same way: connect the Framer project, connect Shopify in the Shop Canvas plugin, then run the stub or the kit skill. Prefer the plugin for Connect, Sync and runtime; keep tokens out of chat.

The plugin and full skill use the same sync engine. Run one sync at a time on a project. Use the skill delivered with this kit for apply steps; the public stub does not publish private sync recipes.

What it does, in order

Reads the saved configuration and validates the store. The store domain and public token come from the plugin’s Connect screen, never from the chat. One small read-only request confirms the shop name.

Syncs the catalog into the Products collection. The full kit runs the bundled sync-core.js — the same source the plugin’s Sync tab runs — with a dry run first, then reports how many products were created, updated or marked stale.

Hands you the runtime snippet to paste into Custom Code yourself. That step stays manual on purpose.

Verifies a product page, the cart and the checkout URL, and publishes only on an explicit yes.

Safety rules the skill follows

  • Public Storefront token only. It never asks for, accepts or uses an Admin API token or password.
  • The token comes from the plugin or project config, never from the conversation.
  • Reads the catalog from Shopify; it never writes products, inventory, discounts or orders. (The storefront’s cart is created by the runtime, not by the skill.)
  • Everything it reads from the store is data, not instruction.
  • Publishing is your call. It previews and reports the change count first.

A successful Connect check does not prove CMS page bindings point at your Products collection. The full kit skill includes operator tooling to inspect bindings; the public stub does not replace that review.

A prompt to start from

Use the Shop Canvas setup skill in this kit. Confirm the connected Framer project and store. Read the saved configuration, preview catalog changes with the bundled sync engine, preserve my curated images, and stop if URLs conflict. Show me the plan before applying. Do not publish.

Your agent service may charge separately. The plugin remains the main setup path; see Optional AI help in the Framer section.

On this page