configure-wasp
Configure Wasp framework features and integrations. Each invocation focuses on one feature at a time.
Before Starting
- Verify user is in the Wasp project root directory (check for wasp config file:
main.wasp or main.wasp.ts)
Available Wasp Features
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 |
Feature Selection
Using the AskUserQuestion tool, ask the user which Wasp feature they'd like to configure:
- Use the most relevant options as selectable choices (limited to 2-4 options)
- Remind users they can select "Other" to choose from additional features
Execute Selected Feature
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.
Guidelines for Using AskUserQuestion with Lists
When asking the user to choose from fetched lists (e.g., auth methods, email providers):
- Always display the full list to the user before asking them to choose, so they know all available options.
- Use the most popular/common options as the selectable choices in
AskUserQuestion (limited to 2-4 options).
- Remind users they can select "Other" to specify any option from the full list that isn't shown in the quick-select options.
- Example format:
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 Feature Completion
After completing a feature configuration:
- Summarize the changes made
- If applicable, let them know if there are any environment variables they need to set and ask them if they need guidance on how to set them
- if so, fetch the raw github doc file URL for the environment variables and guide the user through the process
- Ask if the user would like to configure another feature
- If yes, return to Feature Selection
- If no, suggest running "Verify Setup" if they haven't already
1---2name: configure-wasp3description: 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.4---5
6# configure-wasp
7
8Configure Wasp framework features and integrations. Each invocation focuses on one feature at a time.
9
10## Before Starting
11
121. Verify user is in the Wasp project root directory (check for wasp config file: `main.wasp` or `main.wasp.ts`)
13
14## Available Wasp Features
15
16Present these features to the user and let them choose ONE to configure:
17
18| Feature | Description |
19|---------|-------------|
20| **App Branding** | Set your app's name, description, and meta tags |
21| **Authentication** | Add login methods (Email, Google, GitHub, etc.) |
22| **Email Provider** | Configure email sending (SendGrid, Mailgun, etc.) |
23| **Database** | Set up your database (PostgreSQL, SQLite, etc.) |
24| **Styling (CSS, UI)** | Add Tailwind CSS or ShadCN UI (on top of Tailwind CSS) |
25| **Verify Setup** | Test that your app compiles and runs correctly |
26
27## Feature Selection
28
29Using the `AskUserQuestion` tool, ask the user which Wasp feature they'd like to configure:
30- Use the most relevant options as selectable choices (limited to 2-4 options)
31- Remind users they can select "Other" to choose from additional features
32
33## Execute Selected Feature
34
35Based on the user's selection, follow the corresponding guides below.
36ALWAYS follow the feature guide's corresponding raw text documentation URLs and use it as the basis for assisting the user.
37
38- **App Branding** → [app-branding.md](./app-branding.md)
39- **Authentication** → [authentication.md](./authentication.md)
40- **Email Provider** → [email-provider.md](./email-provider.md)
41- **Database** → [database.md](./database.md)
42- **Styling (CSS, UI)** → [styling.md](./styling.md)
43- **Verify Setup** → [verify-setup.md](./verify-setup.md)
44
45## Guidelines for Using AskUserQuestion with Lists
46
47When asking the user to choose from fetched lists (e.g., auth methods, email providers):
48
491. **Always display the full list** to the user before asking them to choose, so they know all available options.
502. **Use the most popular/common options** as the selectable choices in `AskUserQuestion` (limited to 2-4 options).
513. **Remind users** they can select "Other" to specify any option from the full list that isn't shown in the quick-select options.
524. **Example format:**
53 ```
54 Available auth methods: Username & Password, Email, Google, GitHub, Discord, Keycloak, Slack
55
56 [AskUserQuestion with 3-4 most common options]
57
58 Note: Select "Other" to choose from additional options like Discord, Keycloak, or Slack.
59 ```
60
61## After Feature Completion
62
63After completing a feature configuration:
641. Summarize the changes made
652. If applicable, let them know if there are any environment variables they need to set and ask them if they need guidance on how to set them
66 - if so, fetch the raw github doc file URL for the environment variables and guide the user through the process
673. Ask if the user would like to configure another feature
683. If yes, return to Feature Selection
694. If no, suggest running "Verify Setup" if they haven't already
aibot88