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

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/wasp-lang/wasp-agent-plugins --skill wasp-plugin-init

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

  1. inform the user that this process will give their agent (Claude, Codex, Copilot, etc.) access to knowledge on Wasp's features, commands, workflows, and best practices by importing the `general-wasp-knowledge.md` file into the user's AGENTS.md or CLAUDE.md file. Use the AskUserQuestion tool (or equivalent) to: a) ask the user if they want to continue, b) ask if they are using Claude Code (CLAUDE.md) or other agents like Codex, Gemini, Copilot, etc. (AGENTS.md).
  2. if the user is using Claude Code, follow the Claude Code memory instructions. If the user is using other agents, follow the Other agents memory instructions.
  3. inform the user that process is complete and they can run /wasp-plugin-help to see the plugin's available skills and features.
  4. recommend the user do the following for the best Wasp development experience with Claude, Codex, Copilot, etc.:
  • Start the dev server: Tell it to run the 'start-dev-server' skill to start the Wasp app and give it access to server logs, build errors, and Wasp CLI commands
  • Enable Chrome DevTools: Prompt it to `use the Chrome DevTools MCP server` to give it visibility into browser console logs, network requests, and runtime errors

Explain that together these provide end-to-end insight (backend + frontend) for faster debugging and development.

Claude Code memory

  • get the plugin version from `${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json` (version field). Use it below as {VERSION}.
  • check if .claude/wasp/.wasp-plugin-initialized-v{VERSION} already exists. If it does, inform the user the plugin is already initialized for this version and skip the remaining steps.
  • check for any old marker files matching the pattern .wasp-plugin-initialized* in .claude/wasp/. If found, remove them — this is a version upgrade:
bash
rm -f .claude/wasp/.wasp-plugin-initialized*
bash
mkdir -p .claude/wasp && cp ./general-wasp-knowledge.md .claude/wasp/general-wasp-knowledge.md
  • if the CLAUDE.md file does not already contain a # Wasp Knowledge section, append it as an import:
markdown
# Wasp Knowledge

Wasp knowledge can be found at @.claude/wasp/general-wasp-knowledge.md
  • create the versioned marker file so the plugin knows this version's init has been run:
bash
touch .claude/wasp/.wasp-plugin-initialized-v{VERSION}

Other agents memory

  • get the plugin version from `${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json` (version field). Use it below as {VERSION}.
  • if the AGENTS.md file already contains a section starting with # Wasp Knowledge [GENERATED BY WASP, remove that entire section (from the heading to the next # heading or end of file) before adding the new one.
  • append the entire contents of `general-wasp-knowledge.md` into the user's AGENTS.md file:
  • Append a new section at the end of the file with the title # Wasp Knowledge [GENERATED BY WASP v{VERSION}].
  • Copy and paste the contents of `general-wasp-knowledge.md` into this new section.
from this repository

More skills

All skills