wasp-plugin-help
- run the check-wasp-init hook using the Bash tool with
nodecommand to check if the Wasp plugin has been initialized. - let the user know if the Wasp plugin has been initialized or not.
- if the Wasp plugin has not been initialized (the hook outputs JSON), let the user know they should take care of this first by running
/wasp-plugin-init:
⚠️
The Wasp plugin hasn't been initialized for the current project.
Run `/wasp-plugin-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, Codex, Copilot, etc. work better with Wasp by:
- Using the right documentation — Automatically fetches the correct Wasp docs for your project's version
More from wasp-lang/wasp-agent-plugins
wasp-plugin-init
Adds Wasp knowledge, LLM-friendly documentation fetching instructions, and best practices to your project's CLAUDE.md or AGENTS.md file
97expert-advice
Get advice on app improvements and functionality from a Wasp expert. Takes optional arguments for more specific requests e.g. `/expert-advice how can I improve account management?`.
95add-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.
94start-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 the agent can see client-side errors. Essential for any development or debugging work.
91deploying-app
deploy the Wasp app to Railway or Fly.io using Wasp CLI.
76