Start the Wasp dev server and set up full debugging visibility. This includes running the server (with access to logs), and connecting browser console access so Claude can see client-side errors. Essential for any development or debugging work.
/plugin marketplace add wasp-lang/claude-plugins/plugin install wasp@wasp-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
running-db-migrations.mdbackground tasks tab.Grep the .env.server file for DATABASE_URL. If no line starts with DATABASE_URL, continue following this step.
If the user does have their own DATABASE_URL env var set, move on to Step 2.
Check the schema.prisma file in the project root for the datasource block to see which database is being used.
Skip to Step 2: SQLite stores data in a local file, no database server needed.
Start the managed database container as a background task:
wasp start db
Docker needs to be installed and running for the managed Postgres database container (wasp start db) to work.
Run this as a background task in the current claude code session. Wait 5-15 seconds for the database to be ready.
Run as a background task:
wasp start
Listen to the output from wasp start and if it gives a prisma db migration warning, follow the running-db-migrations.md reference.
Confirm client (localhost:3000) and server (localhost:3001) are running by checking the background task output.
If started as background task in current session: Listen to the output for development and debugging information. If started externally: Instruct the user to check the output of the external terminal and share its output with you.
This step is critical for effective development and debugging. Without browser console access, Claude cannot see client-side errors, warnings, or React issues that occur in the browser.
Ask the user (via the AskUserQuestion tool) which method they'd like to use for giving Claude visibility into the browser console:
| Option | Description |
|---|---|
| Chrome DevTools MCP (recommended) | Use the mcp__plugin_wasp_chrome-devtools tool (bundled with the plugin) |
| Built-in Chrome | Use Claude Code's built-in browser connection (check status with /chrome command) |
| Manual | User will manually copy/paste console output when needed |
| Other | User has another preference |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.