AI Skills

Pre-built skills that give AI coding agents deep knowledge of the Next Commerce platform.

Next Commerce AI Skills are pre-built skills that give AI coding agents deep knowledge of the Next Commerce platform — APIs, CLI workflows, and architecture patterns — so they can work autonomously on your store.

Skills are structured markdown files. Any AI tool that accepts a context file or system prompt can use them — Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, and 50+ other LLM-powered agents.

For an optional quickstart that follows the current Campaign Page Kit CLI without choosing a template or project structure for you, use the campaign agent quickstart. The quickstart does not require installing a skill.

Install

The skills CLI is the quickest path: it pulls each skill from GitHub and installs it into the skill directory of the AI tool it detects.

# Install every skill for your detected agent
npx skills add NextCommerceCo/skills -g

# Install one skill
npx skills add NextCommerceCo/skills -g --skill next-ops-scan

# Target a specific agent
npx skills add NextCommerceCo/skills -g -a codex

To manage versions from a checkout, clone the repository and run its guided installer. It previews every change before writing, and installs into Claude Code (~/.claude/skills), Codex (~/.codex/skills), or ~/.agents/skills.

git clone https://github.com/NextCommerceCo/skills.git
cd skills
./skills.sh

Restart your agent session after installing so it loads the new skills. Then ask for the work in plain language, or invoke a skill directly with /<skill-name> in Claude Code (for example /next-ops-scan).

For agents without a native skill directory, each SKILL.md is plain markdown: load it as a system prompt, context file, rule, or chat upload.

Ask your AI tool to install

You can also let your AI tool drive the install. It knows where files live for your operating system and assistant:

Install the Next Commerce AI skill I need from https://github.com/NextCommerceCo/skills.
Prefer cloning the repo and running ./skills.sh, choosing the installation location for my
current AI tool. If a local checkout is not appropriate, use the public npx skills installer
or load the relevant SKILL.md as context.

Tell it which skill you want, or ask it to inspect skills.json and choose the relevant one.

Keep skills up to date

An installed skill is a copy, so it doesn't change when the repository does. Check before starting work that depends on one:

With a checkout: run git pull --ff-only, then ./skills.sh status to mark older copies stale, and ./skills.sh install <target> <skill> to replace them.
With the skills CLI: run npx skills update.
Without either: compare the version: line in your installed SKILL.md with that skill's version in skills.json.

next-campaigns-create checks for a newer version itself each time it runs. Restart the agent session after any update.

Available skills

Skill	What it does	When to use it
next-theme-figma	Turn a Figma storefront design into a validated, low-inference handoff package for `next-theme-dev`: sections, assets, geometry, copy, and design tokens	You have a Figma storefront design (PDP, homepage, and so on) to build as a Next Commerce theme
next-theme-design	Turn a live website or its HTML into a validated handoff package for `next-theme-dev`: captures at three widths, sections, geometry, copy decisions, styles, behaviors, and commerce divergences	You want an existing page, such as a merchant's landing page, rebuilt as a Next Commerce storefront
next-theme-dev	Build, modify, and debug storefront themes: Spark, Intro Bootstrap, Theme Settings, the `ntk` CLI, DTL templates, storefront GraphQL, and builds from Figma or live-site handoff packages	You're editing theme files, setting up a new storefront, building from a handoff package, or debugging templates
next-campaigns-create	Create a launch-ready Campaigns App campaign over the Admin API: packages, shipping, quantity Buy 1/2/3, buy-X-get-Y as a labeled percentage, and gift-with-purchase, behind a plan-hash approval gate. Hands back the campaign `api_key` and package IDs	A new campaign needs to exist on a store before funnel work starts. It creates new campaigns only
next-campaigns-setup	Scaffold and configure a new Campaign Page Kit campaign end to end: project, starter template, config, and analytics	Starting a new CPK campaign after the campaign exists in the Campaigns App
next-bulk-fulfill	Mark orders Fulfilled with tracking numbers from a CSV when a fulfillment provider's sync-back fails	A provider shipped orders but tracking didn't sync back, leaving orders stuck in Processing
next-bulk-move	Move fulfillment orders between warehouse locations in bulk, from a file of order numbers or a product/SKU list	Switching fulfillment providers, or moving every fulfillment order containing a given SKU or product
next-bulk-subscription	Pause, cancel, or update subscriptions in bulk from a CSV or XLSX of subscription IDs, with a dry run and verification	Bulk-pausing, shifting renewal dates, changing intervals or gateways, or cancelling a list of subscriptions
next-ops-scan	Read-only daily risk scan for one store: Incomplete and Rejected orders, delivery-tracking failures, and stale shipments	A routine health check to catch risky orders and reduce disputes

For design-led theme work, run next-theme-figma (Figma source) or next-theme-design (live page source) before next-theme-dev. The three theme skills are installed together.

Prerequisites

Each skill lists its own requirements in its SKILL.md and README.md. In general:

Operations and campaign provisioning skills (next-bulk-*, next-ops-scan, next-campaigns-create) run Python 3 scripts that use only the standard library. They need an Admin API token with the scopes the skill names, in a local .env as {SUBDOMAIN}_NEXT_ADMIN_API_TOKEN or in the environment. Create the API access under Settings → API Access.
Theme skills need Python 3.10 or newer (next-theme-figma also uses Node.js), a browser tool that can take screenshots, and for next-theme-dev a Storefront OAuth app API key with themes:read and themes:write.
next-campaigns-setup needs Node.js and npm, a Campaign Page Kit project, and the campaign's Campaign Cart API key.

Skills that change store data (bulk actions, campaign creation, theme pushes) show a plan or dry run and wait for your approval before writing.

Machine-readable index

For AI agents that need to programmatically discover available skills, skills.json is a structured manifest with skill IDs, descriptions, trigger phrases, and prerequisites. Agents can fetch this single file to decide which skill to load.