plugin-help
Shows the Wasp plugin's available features, commands, and skills.
When & Why to Use This Skill
The plugin-help skill serves as an interactive documentation hub and onboarding guide for the Wasp plugin within Claude Code. It ensures the development environment is correctly initialized and provides developers with a quick reference to specialized commands and skills for full-stack web development, effectively preventing AI hallucinations by grounding Claude in version-specific Wasp documentation.
Use Cases
- Plugin Onboarding: Quickly discover all available slash commands like /wasp:init and /wasp:expert-advice to understand how to leverage the Wasp plugin's full potential.
- Environment Verification: Run an automated check to see if the Wasp plugin is properly initialized for the current project, receiving clear instructions on how to fix setup issues.
- Feature Discovery: Access a categorized list of specialized skills for adding authentication, managing databases, and deploying apps to Railway or Fly.io.
- Context-Aware Documentation: Ensure Claude Code uses the correct version-specific documentation (llms.txt) to provide accurate, best-practice advice for your specific Wasp project version.
| name | plugin-help |
|---|---|
| description | Shows the Wasp plugin's available features, commands, and skills. |
- run the check-wasp-init hook using the Bash tool with
nodecommand to see if Wasp knowledge has been initialized. - let the user know if the Wasp plugin has been initialized or not.
- if the Wasp plugin has not been initialized, let the user know they should take care of this first by running
/wasp:init:
⚠️
The Wasp plugin hasn't been initialized for the current project.
Run `/wasp:init` to get the plugin's full functionality.
- display the Wasp Plugin for Claude Code section to the user exactly as it is below.
--- --- 🐝 🐝 🐝 --- ---
🐝 Wasp Plugin for Claude Code
What This Plugin Does
This plugin makes Claude Code work better with Wasp by:
- Using the right documentation — Automatically fetches the correct Wasp docs for your project's version
- Avoiding common mistakes — Provides Wasp-specific tips, patterns, and best practices so Claude doesn't hallucinate or use outdated approaches
- Guided workflows — Skills and commands so Claude can walk you through setting up Wasp's batteries-included features (auth, email, database, styling) and deploying
- Full debugging visibility — Start managed databases, dev servers, and connect browser console access so Claude has full development and debugging visibility across the entire stack
The result: Claude actually understands Wasp instead of guessing.
Quick Reference
Slash Commands:
/wasp:init - Initialize plugin for your project
/wasp:expert-advice - Get advice on improvements from a Wasp expert
/wasp:help - Show this guide
Skills:
add-feature - Add Wasp's built-in features (auth, email, database, styling)
deploying-app - Guided deployment to Railway or Fly.io
start-dev-server - Start dev environment with full debugging visibility (db -> server -> browser console)
💬 Example Prompts
- "Add Google authentication to my app"
- "Help me add ShadCN UI to my app"
- "Migrate the database from SQLite to PostgreSQL and start it for me"
- "Set up email sending with SendGrid"
- "Solve the errors in the browser using the Chrome DevTools MCP server"
- "Why isn't my recurring job working?"
- "Deploy my app to Railway"
📖 Documentation Access
The plugin ensures Claude detects your project's Wasp version and references the correct documentation:
- Latest:
https://wasp.sh/llms.txt - Versioned:
https://wasp.sh/llms-{version}.txt(e.g.,llms-0.15.txt)
🫂 Community & Contribute
Join the Wasp Discord for help and web dev discussion. Submit issues, feedback, or PRs: Wasp Claude Code Plugins