start-dev-server
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.
What this skill does
## Step 0: Get User Preferences
- [ ] Ask the user if they want Claude to start the dev server(s) as a background task in the current session, or on their own in a separate terminal:
- Starting as a background task (Claude)
- Pros: Claude has more autonomy, can respond directly to dev server logs (warnings, errors).
- Cons: Certain actions can be slower, and the user has less direct control. Server logs are only visibile to the user from within the `background tasks` tab.
- Starting externally (User)
- Pros: The user has more direct control over app development and the Wasp CLI commands. Can be advantageous for more advanced users.
- Cons: Debugging and feature discovery can be slower, as Claude doesn't have direct access to dev server logs (warnings, errors) or Wasp CLI commands.
- [ ] Depending on the user's choice, follow the steps below and run the commands for the user as background tasks, or guide them through running them manually in a separate terminal.
### Step 1: Ensure the Development Database is Running
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](#step-2-start-dev-server).
Check the `schema.prisma` file in the project root for the `datasource` block to see which database is being used.
#### SQLite
**Skip to [Step 2](#step-2-start-dev-server):** SQLite stores data in a local file, no database server needed.
#### PostgreSQL
Start the managed database container as a background task:
```bash
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.
### Step 2: Start Dev Server
Run as a background task:
```bash
wasp start
```
Listen to the output from `wasp start` and if it gives a prisma **db migration warning**, follow the [running-db-migrations.md](./running-db-migrations.md) reference.
### Step 3: Verify Server is Running
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.
### Step 4: Connect Browser Console Access (Important!)
**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 |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.