wasp-plugin-init
Adds Wasp knowledge, LLM-friendly documentation fetching instructions, and best practices to your project's CLAUDE.md or AGENTS.md file
What this skill does
0. 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`](./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).
1. if the user is using Claude Code, follow the [Claude Code memory](#claude-code-memory) instructions. If the user is using other agents, follow the [Other agents memory](#other-agents-memory) instructions.
2. inform the user that process is complete and they can run `/wasp-plugin-help` to see the plugin's available skills and features.
3. 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`](${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*
```
- copy [`general-wasp-knowledge.md`](./general-wasp-knowledge.md) to the user's project root `.claude/wasp` directory:
```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`](${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`](./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`](./general-wasp-knowledge.md) into this new section.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.