medusajs/medusa-agent-skills
19 skills26k installs3.9k starsGitHub
Install
npx skills add https://github.com/medusajs/medusa-agent-skillsSkills in this repo
1Storefront Best Practicesstorefront-best-practices is a framework-agnostic agent skill for ecommerce storefront work across Next.js, SvelteKit, TanStack Start, React, and Vue. It applies to checkout flows, cart pages, product listings, navigation, homepage layouts, and Medusa backend integration. Critical patterns require loading reference/design.md before any UI component to discover design tokens and prevent inconsistent styles. Reference files cover connecting-to-backend.md, medusa.md SDK setup, navbar, hero, footer, product listing and details layouts, checkout architecture, seo.md, and mobile-responsiveness.md. Accessibility rules mandate aria-live polite on cart count updates and keyboard navigation for cart and checkout interactions. Mobile guidance requires env safe-area-inset-bottom on sticky purchase bars and 44px minimum touch targets. Performance rules include loading lazy on below-fold product images and keeping mobile images under 500KB. SEO requires product JSON-LD schema for Google Shopping rich snippets. Developers reach for it when adding checkout, implementing cart behavior, or connecting any storefront surface to Medusa.3.2kinstalls2Building With Medusabuilding-with-medusa is the required agent skill for Medusa backend development covering custom modules, workflows, API routes, data models, module links, and business logic placement. The critical architecture flow is Module data models and CRUD, Workflow business logic with rollback, API Route HTTP interface, then Frontend SDK consumers. Key conventions restrict HTTP methods to GET, POST, and DELETE never PUT or PATCH, require workflows for all mutations, and place validation in workflow steps not routes. Reference files must load before implementation: custom-modules.md, workflows.md, api-routes.md, module-links.md, querying-data.md, and authentication.md as applicable. Critical rules include arch-workflow-required, type-request-schema with Zod inferred MedusaRequest types, and data-price-format stating prices store as-is not cents. Data access uses query.graph for cross-module retrieval and query.index for filtering linked modules, avoiding JavaScript filter on linked data. Module names must be camelCase without dashes and linkable is automatic on data models. Developers reach for it whenever planning or implementing Medusa modules, workflows, admin or store routes, or cross-m.3.1kinstalls3Building Admin Dashboard Customizationsbuilding-admin-dashboard-customizations is a medusajs/medusa-agent-skills guide for extending the Medusa Admin dashboard with widgets, custom pages, forms, tables, and navigation using the Admin SDK and Medusa UI design system. It must load before any admin UI work and directs agents to reference files for data loading, forms, display patterns, table selection, navigation, and typography rather than relying solely on MedusaDocs MCP props. Critical setup requires an exact Medusa JS SDK client with session auth type and VITE_BACKEND_URL, plus pnpm-specific peer dependency installs for @tanstack/react-query and react-router-dom versions matching the dashboard lockfile. Data loading enforces separate display queries on mount versus modal or form queries triggered by user action, with explicit cache invalidation after mutations. Widget zones, route definitions, and component patterns follow Medusa UI semantic classes documented in the reference files. The skill distinguishes admin UI routes from backend API routes handled by building-with-medusa and storefront work covered by building-storefronts. Developers invoke it when creating product widgets, custom admin pages, data tables, moda.3kinstalls4Building StorefrontsMedusa Storefront Development is the required skill for any storefront task involving custom API routes, SDK integration, React Query patterns, mutations, and cache invalidation when building on Medusa. Critical rules mandate always using the Medusa JS SDK instead of raw fetch because publishable API keys and auth headers are injected automatically. Built-in endpoints should use sdk.store and sdk.admin methods, while custom routes use sdk.client.fetch with plain object bodies never wrapped in JSON.stringify. React Query guidance covers useQuery for GET, useMutation for POST and DELETE, hierarchical query keys, invalidation on success, and handling isLoading, isPending, and isError states. A critical display rule states Medusa prices are stored as-is so 49.99 displays directly without dividing by 100. The skill requires loading references/frontend-integration.md before implementation and pairs with building-with-medusa for backend module, workflow, and API route work. Common mistakes checklist flags fetch usage, wrong SDK methods, missing invalidation, flat query keys, and price division errors.2.9kinstalls5Learning MedusaThis is NOT a passive reference skill This is an INTERACTIVE TUTORING SESSION where you Claude guide the user through building a brands feature in Medusa teaching architecture concepts along the way Your Role Act as a coding bootcamp instructor patient encouraging thorough and focused on teaching understanding not just completion What You ll Build Together A brands feature that allows Creating brands via API Linking brands to products Viewing brands in the admin dashboard Architecture Focus The user will deeply understand Module Workflow API Route pattern Module Links for cross module relationships Workflow Hooks for extending core flows Admin UI customization patterns When this skill is loaded you MUST follow this protocol The learning medusa agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation2.4kinstalls6Db MigrateExecute the Medusa database migration command to apply pending migrations Use the Bash tool to execute npx medusa db migrate Report the migration results to the user including Number of migrations applied Any errors that occurred Success confirmation The db migrate agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation2.3kinstalls7Db GenerateGenerate database migrations for the specified Medusa module The user will provide the module name as an argument e g brand product custom module For example medusa dev db generate brand Use the Bash tool to execute the command npx medusa db generate module name replacing module name with the provided argument Report the results to the user including The db generate agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation2.3kinstalls8New UserA Medusa agent skill that automates admin user creation by executing the npx medusa user command with email and password arguments. Designed for developers integrating Medusa into agent workflows, this skill handles user provisioning, error reporting, and next-step guidance. Executes via Bash tool integration with Medusa CLI, returning confirmation of user creation or detailed error messages. Streamlines initial setup and admin account management in headless commerce deployments.2kinstalls9Using Medusa Cloudusing-medusa-cloud is a workflow skill from the medusa-cloud plugin in medusajs/medusa-agent-skills for operating Medusa commerce backends on Medusa Cloud through the Cloud CLI. The skill teaches agents correct mcloud auth, project and organization selection, deployment inspection, environment lifecycle commands, variable management, and log filtering so storefront linkage and env configuration stay aligned with Medusa conventions. Developers reach for using-medusa-cloud when a Medusa backend is already targeting Cloud and they need agent-driven deploy debugging, environment redeploys, or managed infra operations without hand-reading CLI docs. The medusa-cloud plugin bundles 8 related Cloud CLI skills alongside using-medusa-cloud, covering auth, deployments, environments, logs, variables, organizations, and projects. Install via Claude Code plugin marketplace or yarn skills add medusajs/medusa-agent-skills for Cursor and other agents.724installs10Mcloud Deploymentsmcloud-deployments is a Medusa agent skill from medusajs/medusa-agent-skills that wraps the Medusa Cloud CLI for deployment inspection and promotion. The skill runs `mcloud deployments` commands with mandatory `--json` output, confirms org and project context via `mcloud whoami --json`, and uses `jq` to parse deployment records and build logs keyed by `depl_*` deployment IDs or build IDs. Developers reach for mcloud-deployments when they need repeatable rollout steps, environment targeting, or post-deploy verification on Medusa Cloud without manually chaining shell commands. The skill is constrained to Bash tools scoped to `mcloud deployments*` and `jq*`, making it suitable for agents debugging failed builds or checking release status on mcloud.685installs11Mcloud Environmentsmcloud-environments is a Medusa Cloud agent skill from medusajs/medusa-agent-skills that guides AI agents through six `mcloud environments` subcommands—list, get, create, delete, redeploy, and trigger-build—plus `mcloud use` context switching and `jq` JSON parsing. The skill enforces safety rules such as blocking production deletes, requiring `--yes` for non-interactive deletes, and choosing redeploy versus trigger-build based on whether the fix is environment-side or committed code. Developers reach for mcloud-environments when provisioning new long-lived Cloud environments, redeploying after variable or infra changes, or kicking off fresh builds from a tracked branch without memorizing CLI flags and guardrails.671installs12Mcloud Logsmcloud-logs in medusajs/medusa-agent-skills teaches developers to execute mcloud logs against Medusa Cloud environments when debugging checkout failures, webhook errors, or slow API paths in production commerce workloads. The skill wraps the Medusa Cloud CLI with Bash(mcloud logs*) and jq* for filtering backend or storefront logs by time range, deployment scope, and error text. Constraints document that --follow and --json are incompatible, so programmatic analysis should use bounded --from/--to windows with --json instead of streaming pipelines. Follow mode streams until Ctrl+C and must stay out of scripts. Default retrieval returns the last 500 log lines, giving agents a bounded starting corpus before deeper search. Developers reach for mcloud-logs when interpreting runtime backend or storefront logs on Medusa Cloud rather than guessing failure causes from local-only output. The workflow fits commerce engineers operating deployed Medusa backends who need jq-friendly JSON log slices or human-readable tail output during incident response on live storefront and API deployments.671installs13Mcloud Projectsmcloud-projects is an agent skill for Medusa Cloud that wraps Bash access to mcloud projects and mcloud use, plus jq for parsing JSON output. Developers invoke it when onboarding new stores, resolving project handles by name, retrieving linked environment details, or cleaning up obsolete hosted commerce projects. The skill documents irreversible delete behavior and recommends --yes for scripted or non-interactive deletes. Allowed tools are scoped to mcloud projects*, mcloud use*, and jq*, keeping agent actions aligned with official Medusa Cloud project management workflows rather than ad-hoc API calls.669installs14Mcloud Variablesmcloud-variables is a Claude Code skill from medusajs/medusa-agent-skills that runs mcloud variables commands to inspect environment variables across Medusa Cloud projects and environments. The skill lists and retrieves configuration keys for database URLs, payment provider keys, and third-party API tokens while enforcing a safety rule to never pass --reveal unless the user explicitly requests secret values. Developers reach for mcloud-variables when preparing or auditing Medusa Cloud deploys and need to confirm which variables exist per environment without manually opening the dashboard. Lookups require --project and --environment flags, and output can be piped through jq for structured inspection.669installs15Mcloud Organizationsmcloud-organizations is an agent skill from medusajs/medusa-agent-skills that wraps mcloud organizations CLI commands for Medusa Cloud account administration. Allowed tools include Bash on mcloud organizations*, mcloud use*, and jq* for JSON output parsing. Developers use it to discover organizations, resolve organization IDs by name, and retrieve details including members and subscription status before running environment commands. The skill documents an auth constraint: organizations list requires personal authentication via browser login or personal access key, and organization access keys return 401 on that command. When authenticated with MCLOUD_TOKEN using an org access key, developers must use alternative discovery paths documented in the skill. Output includes organization listings and JSON metadata for account scoping.668installs16Ecommerce StorefrontAn official Medusa plugin for building e-commerce storefronts on the Medusa platform. It helps developers create the customer-facing shopping frontend that connects to a Medusa commerce backend. Useful for teams building online stores with Medusa.0installs17Learn MedusaAn official Medusa plugin that helps developers learn the Medusa e-commerce framework. It provides guidance on Medusa concepts, APIs, and how to build with the platform. A reference and onboarding aid for teams adopting Medusa.0installs18Medusa CloudA plugin for Medusa Cloud, the managed hosting and deployment platform for Medusa-based e-commerce applications. It helps developers deploy and operate their Medusa commerce stores on Medusa's cloud infrastructure. Part of the official Medusa agent-skills set.0installs19Medusa DevAn official Medusa plugin for developing on the Medusa e-commerce platform. It supports building and customizing Medusa commerce backends, including modules, APIs, and extensions. Aimed at developers implementing and extending Medusa-based stores.0installs