deploying-app
deploying-app
Pre-Deployment
- Run a pre-deployment check via validating-pre-deployment to validate configuration.
- present the list of supported
wasp deployproviders under the "Wasp Deploy" section of the docs and ask the user to choose one. - follow the steps from the chosen provider's guide to deploy the app.
OAuth Redirect URLs
If they user is using OAuth providers, inform them that they need to add the redirect URLs to the OAuth providers in the provider's dashboard. For example: https://your-server-url.com/auth/google/callback
More info can be found in the Wasp Social Auth Providers docs.
Deployment Interrupted
Safe to rerun: wasp deploy <provider> deploy
DO NOT rerun: wasp deploy <provider> launch commands (one-time only)
More from wasp-lang/claude-plugins
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.
6add-feature
Add Wasp's built-in features to your app — auth, email, jobs, and more. These are full-stack, batteries-included features that Wasp handles for you. Use when the user wants to add meta tags, authentication (email, social auth providers), email sending, database setup, styling (tailwind, shadcn), or other Wasp-powered functionality.
5wasp-plugin-init
Add Wasp knowledge to your project's CLAUDE.md
2plugin-help
Shows the Wasp plugin's available features, commands, and skills.
2