convez.ai
SkillAutomaçãoIntermediário
NextCommerceCo

Next Commerce AI Skills

NextCommerceCo/skills

Skills de IA pré-construídas para automação no Next Commerce

Ver no GitHub
InicialPluginScore · de 0 a 100

Conjunto de skills pré-construídas que capacitam agentes de IA a trabalhar autonomamente na plataforma Next Commerce, cobrindo desenvolvimento de temas, operações de fulfillment, gerenciamento de assinaturas e campanhas. As skills são arquivos markdown estruturados compatíveis com Claude Code, Cursor, Copilot e outros agentes de IA.

Instalação

$npx convez-ai NextCommerceCo/skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
1
Acompanhando
1
Saúde
37%
Último commit
há 6 dias
Versão
—
Issues abertas
5
Contribuidores
4

Casos de uso

  • Desenvolvimento e customização de temas de loja com DTL templates
  • Sincronização em lote de fulfillment com números de rastreamento
  • Movimentação em massa de orders entre diferentes centros de distribuição
  • Automação de ações em bulk para gerenciamento de assinaturas
  • Setup e configuração de novas campanhas de marketing

Veredito

Skills bem estruturadas e prontas para produção que integram profundamente com a plataforma Next Commerce, reduzindo significativamente o tempo de implementação. Melhor aproveitadas por desenvolvedores e operadores que já conhecem o ecossistema Next Commerce.

README

A tradução para o português deste README ainda está na fila.

Next Commerce AI Skills

Pre-built skills that give AI coding agents deep knowledge of the Next Commerce platform — APIs, CLI workflows, architecture patterns, and gotchas — 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. They work with Claude Code, OpenAI Codex, Cursor, GitHub Copilot, and any other agent that reads markdown.

Skills

SkillWhat It DoesWhen to Use
Theme DevelopmentBuild and customize storefront themes — DTL templates, ntk CLI, Tailwind CSS, settings, side cartYou're editing theme files, setting up a new storefront, or debugging template issues
Bulk Fulfillment SyncUpdate orders to Fulfilled with tracking numbers from a CSVYour fulfillment provider shipped orders but tracking didn't sync back — orders stuck in Processing
Bulk Fulfillment MoveMove fulfillment orders between warehouse locations in bulk — by order-number file or by Product ID / SKU listSwitching fulfillment providers, or moving every FO containing a given SKU/product to a new location
Bulk Subscription ActionsPause, cancel, or PATCH subscription fields for a list of subscription IDsMerchant wants to bulk-pause until a date, bulk-shift renewals, bulk-cancel, or migrate subscriptions between gateways
New Campaign SetupScaffold and fully configure a new Next Commerce campaign repo — brand init, starter template, campaigns.json seed, API key, store details, and analytics in one passStarting a new Next Commerce campaign for a brand

Campaigns OS Skill Boundary

This repo hosts next-campaigns-setup, which covers Next Commerce campaign repo bootstrap and first configuration.

The canonical Campaigns OS lifecycle skills — build, polish, and QA — ship with the public campaigns-os package itself and install via campaigns-os install-skills. They're version-locked to the package's CLI and contract versions, which is why they live with the package rather than in this catalog.

Quick Start

Ask Your AI Tool to Install

If you use an AI coding tool, the easiest path is to ask it to install the skill for you:

Install the Next Commerce AI skill I need from https://github.com/NextCommerceCo/skills. Use the installation location for my current AI tool and operating system. If my tool supports native skills, install each skill as a directory containing its SKILL.md. If it only supports rules, prompts, or context files, add the relevant SKILL.md there instead. Prefer HTTPS clone unless my GitHub SSH access is already configured.

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

Manual Install

We recommend the skills CLI — a friendly skill installer utility that works across every major AI coding tool. It pulls SKILL.md files from a GitHub repo and drops them into the right config directory for whichever assistant you use, with built-in support for Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Windsurf, and 50+ other LLM-powered agents.

Install all skills from this repo:

npx skills add NextCommerceCo/skills

Install a single skill:

npx skills add NextCommerceCo/skills -s next-theme-dev

List available skills without installing:

npx skills add NextCommerceCo/skills --list

Target a specific agent (auto-detected by default):

npx skills add NextCommerceCo/skills -a claude-code

Once installed, Claude Code auto-detects when a skill is relevant, or you can invoke it directly with /<skill-name> (e.g. /next-theme-dev). If the skills directory did not exist before Claude Code started, restart Claude Code so it can discover the new directory.

Update all installed skills:

npx skills update

Update a single skill:

npx skills update next-theme-dev

For tools the skills CLI doesn't support, each SKILL.md is plain markdown — load it as a system prompt, context file, or chat upload.

Machine-Readable Index

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

Prerequisites

Each skill lists its own requirements in the file. Common across all skills:

  • Access to a Next Commerce store
  • An API key with the scopes specified by the skill (create at Dashboard > Settings > API Access)

Contributing

Each skill is a directory containing a single SKILL.md file. To add a new skill:

  1. Create a directory with a descriptive name (e.g., next-my-skill/)
  2. Add a SKILL.md with YAML frontmatter (name, version, description, allowed-tools) followed by the skill instructions in markdown
  3. Add a "Using This Skill" section with cross-tool usage instructions (see existing skills for the format)
  4. Add an entry to skills.json
  5. Update this README's skills table
  6. Open a PR
Ver o original no GitHub

Bom para

Relacionados