From wasp
Displays Wasp plugin's features, commands, skills, and initialization status. Lists skills like add-feature, start-dev-server, and example prompts for Wasp app workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wasp:wasp-plugin-helpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. run the [check-wasp-init hook](../../hooks/check-wasp-init.js) using the Bash tool with `node` command to check if the Wasp plugin has been initialized.
node command to check if the Wasp plugin has been initialized./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.
--- --- 🐝 🐝 🐝 --- ---
This plugin makes Claude Code, Codex, Copilot, etc. work better with Wasp by:
The result: The agent actually understands Wasp instead of guessing.
Skills:
add-feature - Add Wasp's built-in features (auth, email, database, styling)
deploying-app - Guided deployment to Railway or Fly.io
expert-advice - Get advice on app improvements and functionality from a Wasp expert
start-dev-server - Start dev environment with full debugging visibility (db -> server -> browser console)
wasp-plugin-init - Adds Wasp knowledge, LLM-friendly documentation fetching instructions, and best practices to your project's CLAUDE.md or AGENTS.md file
The plugin ensures Claude detects your project's Wasp version and references the correct, LLM-friendly documentation.
Join the Wasp Discord for help and web dev discussion. Submit issues, feedback, or PRs: Wasp Agent Plugins
npx claudepluginhub wasp-lang/wasp-agent-plugins --plugin waspAdds Wasp features like authentication (email/social), email sending, PostgreSQL/SQLite database, Tailwind/ShadCN styling, and app branding/meta tags. Use for configuring full-stack capabilities in Wasp apps.
Guides selection of spences10's Claude Code ecosystem tools including MCP servers, skills, CLIs via decision trees, recommended setups, and workflows.