configure-wasp
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.
What this skill does
# configure-wasp Configure Wasp framework features and integrations. Each invocation focuses on one feature at a time. ## Before Starting 1. 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. - **App Branding** → [app-branding.md](./app-branding.md) - **Authentication** → [authentication.md](./authentication.md) - **Email Provider** → [email-provider.md](./email-provider.md) - **Database** → [database.md](./database.md) - **Styling (CSS, UI)** → [styling.md](./styling.md) - **Verify Setup** → [verify-setup.md](./verify-setup.md) ## Guidelines for Using AskUserQuestion with Lists When asking the user to choose from fetched lists (e.g., auth methods, email providers): 1. **Always display the full list** to the user before asking them to choose, so they know all available options. 2. **Use the most popular/common options** as the selectable choices in `AskUserQuestion` (limited to 2-4 options). 3. **Remind users** they can select "Other" to specify any option from the full list that isn't shown in the quick-select options. 4. **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: 1. Summarize the changes made 2. 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 3. Ask if the user would like to configure another feature 3. If yes, return to Feature Selection 4. If no, suggest running "Verify Setup" if they haven't already
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".