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).
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.
inform the user that process is complete and they can run /wasp-plugin-help to see the plugin's available skills and features.
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:

rm -f .claude/wasp/.wasp-plugin-initialized*

copy general-wasp-knowledge.md to the user's project root .claude/wasp directory:

wasp-plugin-init