메뉴
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.
configure Wasp framework features and set up their app's branding (meta tags, SEO), authentication (email, social auth providers), database, email providers, styling (tailwind, shadcn), etc. Use when the user wants to add or set up Wasp-specific functionality.
deploy the Wasp app to Railway or Fly.io using Wasp CLI.
Shows the Wasp plugin's available features, commands, and skills.
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.
| name | add-feature |
| description | 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. |
Add Wasp's batteries-included features to your app. Each invocation focuses on one feature at a time.
main.wasp or main.wasp.ts)Present these features to the user and let them choose ONE to configure:
| Feature | Description |
|---|---|
| App Branding | Set your app's name, description, and meta tags |
| Authentication | Add login methods (Email, Google, GitHub, etc.) |
| Email Provider | Configure email sending (SendGrid, Mailgun, etc.) |
| Database | Set up your database (PostgreSQL, SQLite, etc.) |
| Styling (CSS, UI) | Add Tailwind CSS or ShadCN UI (on top of Tailwind CSS) |
| Verify Setup | Test that your app compiles and runs correctly |
Using the AskUserQuestion tool, ask the user which Wasp feature they'd like to configure:
Based on the user's selection, follow the corresponding guides below. ALWAYS follow the feature guide's corresponding raw text documentation URLs and use it as the basis for assisting the user.
When asking the user to choose from fetched lists (e.g., auth methods, email providers):
AskUserQuestion (limited to 2-4 options).Available auth methods: Username & Password, Email, Google, GitHub, Discord, Keycloak, Slack
[AskUserQuestion with 3-4 most common options]
Note: Select "Other" to choose from additional options like Discord, Keycloak, or Slack.
After completing a feature configuration: