start the Wasp dev server, handle database setup, and run migrations. Use when the user wants to start development, run the app locally, or needs help with database migrations.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
detect-database.mdmain.wasp or main.wasp.ts)PostgreSQL: Start the managed database container as a background task:
wasp start db
Run this as a background task in the current claude code session. Wait 5-15 seconds for the database to be ready.
SQLite: Skip this step. Do NOT run wasp start db.
Before running migrations, stop any running Wasp dev server to avoid database locks and stale types.
If started as background task in current session: Use KillShell tool with the task ID.
If started externally: Instruct the user to stop the dev server in the external terminal.
Check for pending migrations by reading the migrations/ directory and the schema.prisma file and comparing.
Prisma requires an interactive terminal. There are two solutions:
script to provide a pseudo-TTY:script -q /dev/null bash -c 'wasp db migrate-dev --name <migration-name>'
wasp db migrate-dev --name migration-name
ALWAYS use --name migration-name. If the user doesn't specify one, suggest a name based on schema changes.
Run as a background task:
wasp start
localhost:3000) and server (localhost:3001) are runningplugin:wasp:chrome-devtools to check browser console for errors