mcpField
W
wasp-plugin-help

wasp-plugin-help

github.com/wasp-langAgent workflows14317 installsUpdated 2w ago
Repository

About wasp-plugin-help

wasp-plugin-help is a Claude Code skill that explains the Wasp plugin’s capabilities and checks whether it has been initialized. It helps developers find relevant Wasp workflows and setup guidance.

Key features

  1. 01Checks Wasp plugin initialization
  2. 02Explains plugin capabilities
  3. 03Lists skills and commands
  4. 04Provides example prompts

Use cases

  1. 01Check whether a project needs plugin setup
  2. 02Find guidance for adding Wasp features
  3. 03Review deployment and debugging workflows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wasp-lang/wasp-agent-plugins --skill wasp-plugin-help

After installing, type/wasp-plugin-helpin Claude Code to confirm it loaded.

Details

From the project README
  1. run the check-wasp-init hook using the Bash tool with node command to check if the Wasp plugin has been initialized.
  2. let the user know if the Wasp plugin has been initialized or not.
  3. 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.
  1. 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:

  1. Using the right documentation — Automatically fetches the correct Wasp docs for your project's version
  2. Avoiding common mistakes — Provides Wasp-specific tips, patterns, and best practices so the agent doesn't hallucinate or use outdated approaches
  3. Guided workflows — Skills and commands so the agent can walk you through setting up Wasp's batteries-included features (auth, email, database, styling) and deploying
  4. Full debugging visibility — Start managed databases, dev servers, and connect browser console access so the agent has full development and debugging visibility across the entire stack

The result: The agent actually understands Wasp instead of guessing.

Quick Reference

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

💬 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, LLM-friendly documentation.

🫂 Community & Contribute

Join the Wasp Discord for help and web dev discussion. Submit issues, feedback, or PRs: Wasp Agent Plugins

Comments

Markdown supported