Raven Medusa Ecommerce Init

Set up a complete development environment in the current project directory. By default the apps run on the host with hot reload, and PostgreSQL and Redis in Docker Compose. Every shop is a separate app, repository and data set. This workflow is what gets reused. Talk to the user in their language.

Result

• The official Medusa starter: backend and Admin in apps/backend, Next.js in apps/storefront, a shared workspace and lockfile.
• Compatible Node LTS and pnpm versions recorded in the project; the starter's orchestration preserved.
• PostgreSQL and Redis with healthchecks and durable, isolated volumes.
• Real local env files, safe secrets, an admin account and the storefront's publishable key.
• Migrations, a sample catalog, region, prices, local delivery and local checkout with the manual/system payment provider available in the chosen version.
• Commands for setup, development, stopping and resuming, and a verified product → cart → order flow.

Do not add a second backend, ORM, auth system, CMS or your own ecommerce framework. Do not implement a specific shop's requirements, courier integrations, live payments or production infrastructure. Do not run raven-init-stack: that is a different stack. Creating or editing this skill alone is not an order to initialize the application.

1. Recognize the project and the current starter

Read the local AGENTS.md and CLAUDE.md, existing manifests and project findings. Keep context/, agent instructions, .git and user files. A PRD or other Raven skills are not a precondition. Derive the name from the project or the user's argument; reduce it to a valid slug, do not interpret it as a path or shell code.