by vulpy-io
AI-run shop: Medusa v2 + Next.js + Payload CMS operated by Fox, the built-in AI assistant. Open-source free edition of Vulpy Commerce.
# Add to your Claude Code skills
git clone https://github.com/vulpy-io/vulpy-commerce-coreGuides for using ai agents skills like vulpy-commerce-core.
See how vulpy-commerce-core compares with popular alternatives.
vulpy-commerce-core is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by vulpy-io. AI-run shop: Medusa v2 + Next.js + Payload CMS operated by Fox, the built-in AI assistant. Open-source free edition of Vulpy Commerce. It has 52 GitHub stars.
vulpy-commerce-core's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/vulpy-io/vulpy-commerce-core" and add it to your Claude Code skills directory (see the Installation section above).
vulpy-commerce-core is primarily written in JavaScript. It is open-source under vulpy-io on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh vulpy-commerce-core against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
→ vulpy.io/commerce — product site, docs, and pricing for Vulpy Commerce.
Vulpy Commerce is an AI-run shop: the open-source Medusa v2 + Next.js + Payload CMS ecommerce stack, operated by Fox, the built-in AI assistant (Hermes agent + Vulpy WebUI). Fox sets up the store, runs it day to day (catalog, content, orders, analytics), and guides you through setup and ongoing operation.
Portable monorepo; use this repo as the upstream, each shop is a copy with its
own .data/ directory and COMPOSE_PROJECT_NAME. See TEMPLATE.md
for creating a new shop and VPS deployment.
@apps/storefront) — NextMerce UI + Medusa + Payload CMSAGENTS.md and deploy/README.mdproductSearch module)pnpm bootstrap # env files, pnpm install, DB, migrate, seed, admin, publishable key
pnpm dev
# In another terminal, while dev is running:
pnpm --filter @apps/storefront seed # Payload CMS content
| Service | URL |
|---|---|
| Fox (Vulpy WebUI) | http://localhost:8787 |
| Storefront | http://localhost:3000 |
| Payload Admin | http://localhost:3000/admin |
| Medusa API | http://localhost:9000 |
| Medusa Admin | http://localhost:9000/app |
All Docker persistence lives under .data/ (gitignored):
.data/
├── postgres/ # PostgreSQL (dev + prod)
├── redis/
├── medusa-static/ # prod uploads
├── payload-media/ # prod CMS media
├── matomo/ # prod Matomo app files
├── matomo-db/ # prod Matomo MariaDB
└── ...
On NTFS/exFAT hosts (e.g. /mnt/data), Postgres, Redis, and Matomo (app + MariaDB) auto-fall back to ~/.local/share/<project>/…. Override with POSTGRES_DATA_DIR / REDIS_DATA_DIR / MATOMO_DATA_DIR / MATOMO_DB_DATA_DIR in .env.
COMPOSE_PROJECT_NAME defaults to the folder name so multiple shops can run on one machine without container conflicts.
| Command | Description |
|---|---|
pnpm bootstrap |
Full bootstrap: env, install, DB, migrate, seed, admin, publishable key |
pnpm bootstrap:env |
Copy .env files only (no Docker) |
./scripts/init-project.sh |
Same as pnpm bootstrap |
pnpm db:up |
Start PostgreSQL + Redis |
pnpm db:hermes:up |
Optional Hermes agent |
pnpm db:matomo:up / db:matomo:down |
Optional local Matomo for analytics testing |
pnpm db:down |
Stop Docker services |
pnpm db:reset |
Wipe .data/postgres and recreate DBs |
pnpm dev |
DB + storefront + medusa-backend |
pnpm build |
Build all apps |
pnpm verify:docker:medusa-packaging |
Pre-push guard: Medusa Dockerfile packages workspace deps (static; skip with SKIP_DOCKER_PACKAGING_VERIFY=1) |
Agent guide (including how to add analytics events for new features): AGENTS.md