Main review

.claude-plugin/marketplace.json

@@ -0,0 +1,28 @@
+{
+  "name": "wasp-plugins",
+  "owner": {
+    "name": "Wasp",
+    "email": "[email protected]",
+    "url": "https://wasp.sh"
+  },
+  "metadata": {
+    "description": "Official Wasp framework plugins for Claude Code",
+    "version": "1.0.0"
+  },
+  "plugins": [
+    {
+      "name": "wasp",
+      "source": "./plugins/wasp",
+      "description": "Give Claude optimized access to Wasp's documentation, features, workflows, and best practices to help you build full-stack React, NodeJS, and Prisma apps even faster.\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n⚡️ QUICK START\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n🧠 /wasp:init - initial setup (run this first!)\n📖 /wasp:help - view all plugin features",
+      "version": "1.0.0",
+      "author": {
+        "name": "Wasp"
+      },
+      "homepage": "https://wasp.sh",
+      "repository": "https://github.com/wasp-lang/claude-plugins",
+      "license": "MIT",
+      "category": "framework",
+      "keywords": ["wasp", "full-stack", "react", "nodejs", "deployment", "authentication", "web-development"]
+    }
+  ]
+}

.gitignore

@@ -0,0 +1,7 @@
+# OS files
+.DS_Store
+Thumbs.db
+
+# Local development
+.env
+.env.local

README.md

@@ -0,0 +1,49 @@
+# Wasp Claude Code Plugins
+
+Official [Claude Code](https://claude.ai/code) plugins for the [Wasp](https://wasp.sh) full-stack web framework.
+
+## Available Plugins
+
+### Wasp
+
+A Claude Code plugin for developing web apps with the Wasp full-stack framework (React, Node.js, and Prisma), providing access to:
+- optimized raw text Wasp documentation for LLMs
+- integrations guidance
+- best practices
+- expert advice on app improvements
+
+## Adding to Your Project
+
+To automatically install this marketplace for all team members, add to your project's `.claude/settings.json`:
+
+```json
+{
+  "extraKnownMarketplaces": {
+    "wasp-plugins": {
+      "source": {
+        "source": "github",
+        "repo": "wasp-lang/claude-plugins"
+      }
+    }
+  }
+}
+```
+
+## Contributing
+
+To add a new plugin:
+
+1. Create your plugin in the `plugins/` directory
+2. Add an entry to `.claude-plugin/marketplace.json`
+3. Submit a pull request
+
+## License
+
+MIT - See individual plugin directories for specific licenses.
+
+## Links
+
+- [Wasp Framework](https://wasp.sh)
+- [Wasp Documentation](https://wasp.sh/docs)
+- [Claude Code](https://claude.ai/code)
+- [Claude Code Plugin Documentation](https://docs.anthropic.com/en/docs/claude-code/plugins)

plugins/wasp/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "chrome-devtools": {
+      "command": "npx",
+      "args": ["-y", "chrome-devtools-mcp@latest"]
+    }
+  }
+}

plugins/wasp/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Wasp.sh
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

plugins/wasp/README.md

@@ -0,0 +1,98 @@
+# Wasp Claude Code Plugin
+
+A Claude Code plugin for Wasp framework development, providing optimized raw text Wasp documentation for LLMs, best practices, and tested workflows.
+
+## Features
+
+- **Optimized Documentation Access**: Claude grounds its knowledge via up-to-date raw text, versioned Wasp documentation
+- **Adds Wasp Knowledge**: Import Wasp best practices and conventions to your project's CLAUDE.md
+- **Configures Wasp**: Easily add Wasp framework features like authentication, database, email, styling (tailwind, shadcn), and other integrations
+- **Deployment Guidance**: Claude Code will guide you through deploying your Wasp app to Railway or Fly.io via the Wasp CLI
+
+## Installation
+
+### Add the Wasp marketplace
+
+```bash
+claude plugin marketplace add wasp-lang/claude-plugins
+```
+
+### Install the Wasp plugin
+
+```bash
+claude plugin install wasp@wasp-plugins --scope project
+```
+
+> [!NOTE]
+> We suggest installing the plugin at the `project` scope (`settings.json` are commited to git).
+> Or by using the `local` scope (`settings.local.json` are not commited to git).
+
+Or install the plugin interactively in a running Claude Code session:
+
+```bash
+/plugin
+```
+
+### Configure and Initialize the plugin
+
+After installing, in an active session, run:
+```bash
+/plugin
+```
+- select `wasp-plugins` under the `marketplaces` tab
+- select the `auto-update` option to enable automatic updates of the plugin
+
+Then run the initialize command to import curated Wasp resources into your project's CLAUDE.md file.
+
+```bash
+/wasp:init
+```
+
+## Commands
+
+- `/wasp:init` - Initialize the plugin
+- `/wasp:help` - Show the plugin's features, commands, and skills
+
+## Skills
+
+This plugin provides skills that Claude will automatically invoke when appropriate:
+
+### 1. Configure Wasp (`configure-wasp`)
+Configure Wasp framework features like authentication, database, email providers, CSS and UI styling libraries, and other Wasp integrations.
+
+### 2. Start Dev Server (`start-dev-server`)
+Start the Wasp development environment with proper database setup and migrations. Detects your database type (PostgreSQL vs SQLite), handles database migrations, and starts the dev server as a background task.
+
+### 3. Deployment Guide (`deploying-app`)
+Let Claude Code guide you through using Wasp's CLI for easy deployment of your Wasp app to Railway or Fly.io.
+
+## Background Hooks
+
+The plugin includes background hooks that:
+- Automatically redirect to LLM-friendly Wasp docs (`llms.txt`) instead of HTML pages
+- Detect your project's Wasp version for versioned documentation
+- Check plugin initialization status on session start
+
+## Recommended Permissions
+
+For the best experience, add these permissions to your project or user settings:
+
+```json
+{
+  "permissions": {
+    "allow": [
+      "Bash(wasp start)",
+      "Bash(wasp db:*)",
+      "Bash(wasp deploy:*)",
+      "WebFetch(domain:wasp.sh)",
+      "WebFetch(domain:raw.githubusercontent.com)"
+      "Skill(wasp:wasp-plugin-help)",
+      "Skill(wasp:start-dev-server)",
+    ]
+  }
+}
+```
+
+## License
+
+MIT

plugins/wasp/commands/expert-advice.md

@@ -0,0 +1,12 @@
+---
+argument-hint: [advice request]
+description: Get advice on app improvements and functionality from a Wasp expert. Takes optional arguments for more specific requests e.g. `/wasp:expert-advice how can I improve account management?`.
+---
+
+1. Explore the current codebase
+2. Check the wasp docs https://wasp.sh/llms.txt
+3. Explore this plugin's skills and commands
+4. Decide on a few improvements (if the user supplies arguments in the command, use them as a starting point, if not, your ideas can be app features, code improvements, enhancements, etc.)
+5. Present the improvements to the user with their names, descriptions, and pros and cons
+
+**User's assist request:** $ARGUMENTS

plugins/wasp/commands/help.md

@@ -0,0 +1,10 @@
+---
+description: Shows the Wasp plugin's available features, commands, and skills.
+---
+
+Explicitly invoke the `wasp-plugin-help` skill in the Claude Code session for the user.
+
+Example:
+```
+Run the `wasp-plugin-help` skill.
+```

plugins/wasp/commands/init.md

@@ -0,0 +1,14 @@
+---
+description: Add Wasp knowledge to your project's CLAUDE.md
+---
+
+0. inform the user that this process will give Claude access to info on Wasp's features, commands, workflows, and best practices by copying the `general-wasp-knowledge.md` file into the project directory and importing it into the user's CLAUDE.md file. Use the AskUserQuestion tool to ask the user if they want to continue.
+1. copy the file `${CLAUDE_PLUGIN_ROOT}/general-wasp-knowledge.md` from within the plugin's installation directory to the user's project `.claude/wasp/knowledge` directory using the Bash tool with `cp` command.
+2. append it to the user's CLAUDE.md file as an import:
+```markdown
+# Wasp Knowledge
+
+Wasp knowledge can be found at @.claude/wasp/knowledge/general-wasp-knowledge.md
+```
+3. inform the user that process is complete and they SHOULD NOT amend the `general-wasp-knowledge.md` file, but should ammend their CLAUDE.md file with their own custom Wasp rules, if desired.
+4. also inform the user they can run `/wasp:help` to see the plugin's available commands and skills.

plugins/wasp/general-wasp-knowledge.md

@@ -0,0 +1,126 @@
+# Wasp App
+
+This project uses TypeScript and Wasp, a batteries-included framework for building full-stack web apps with React, Node.js, and Prisma.
+
+## Documentation
+
+Your training data about Wasp may be outdated. You MUST fetch and verify against the current documentation before implementing Wasp features or answering Wasp questions:
+- https://wasp.sh/llms.txt (latest)
+- https://wasp.sh/llms-{version}.txt (versioned)
+
+## Workflows
+
+### Development Server
+
+Before starting any development task on this Wasp project (coding, debugging, adding features), you MUST check if the dev server is running:
+- Check for active background tasks (use `/tasks` command)
+- Or check if ports 3000 (client) and 3001 (server) are in use
+
+If not running, invoke the `start-dev-server` skill to start the server as a background task or externally.
+
+### Implementation Checklist
+
+1. Fetch https://wasp.sh/llms.txt to verify current syntax (see "Documentation" above)
+2. Check if the feature exists in the current codebase or starter template for reference patterns
+3. Identify which files need changes: wasp config file (`main.wasp` or `main.wasp.ts`), `schema.prisma`, `src/`
+4. Plan the order: schema → migrate → wasp config file → TypeScript
+
+### Schema Changes
+
+After ANY change to `schema.prisma`:
+1. Stop the dev server if running
+2. Run `wasp db migrate-dev --name <descriptive-name>`
+3. Restart the dev server
+
+## Project Reference
+
+### Structure
+
+```
+.
+├── .wasp/                    # Wasp output (auto-generated, do not edit)
+├── public/                   # Static assets
+├── src/                      # Feature code: server `operations.ts` and client `pages.tsx` files
+├── main.wasp or main.wasp.ts # Wasp config file: routes, pages, auth, operations, jobs, etc.
+├── schema.prisma             # Database schema (Prisma)
+```
+
+### Code Organization
+
+Organize by **feature** (vertical), not by type (client/server):
+
+```
+src/
+├── tasks/
+│   ├── TasksPage.tsx      # Page component
+│   ├── TaskList.tsx       # Component
+│   └── operations.ts      # Queries & actions
+├── auth/
+│   ├── LoginPage.tsx
+│   └── google.ts
+```
+
+### Starter Templates
+
+Highly recommend that the user chose one of the following templates when scaffolding a new Wasp app (this helps Claude understand Wasp's features and patterns):
+```bash
+wasp new my-basic-app -t basic # creates a basic starter app with core Wasp features like auth, operations, pages, etc.
+wasp new my-saas-app -t saas # creates a full-featured SaaS starter app with auth, payments, demo app, AWS S3, and more (OpenSaaS.sh)
+```
+
+See the **Starter Templates** section in https://wasp.sh/llms.txt for more templates.
+
+### Customization
+
+Wasp provides layers of customization on top of the tools it uses (vite, expressjs, react-query, client and server setup, etc.): see the **Project Setup & Customization** section in https://wasp.sh/llms.txt.
+
+### Advanced Features
+
+Wasp provides **advanced features**:
+- custom HTTP API endpoints
+- background (cron) jobs
+- type-safe links
+- websockets
+- middleware
+- email sending
+
+See the **Advanced Features** section in https://wasp.sh/llms.txt for more details.
+
+### Import Conventions
+
+**In TypeScript files:**
+- ✅ `import type { User } from 'wasp/entities'`
+- ✅ `import type { GetTasks } from 'wasp/server/operations'`
+- ✅ `import { getTasks, createTask, useQuery } from 'wasp/client/operations'`
+- ✅ `import { SubscriptionStatus } from '@prisma/client'` (for Prisma enums)
+- ✅ Local code: relative paths `import { X } from './X'`
+- ⚠️ Call actions directly using `async/await`. DO NOT use Wasp's `useAction` hook unless optimistic updates are needed.
+
+**In main.wasp:**
+- ✅ `fn: import { getTasks } from "@src/tasks/operations.ts"`
+- ❌ Never relative paths
+
+**In main.wasp.ts:**
+See the **TypeScript Config** section in https://wasp.sh/llms.txt for more details.
+
+## Troubleshooting
+
+### Debugging
+
+When errors occur:
+1. Check server terminal for backend errors (localhost:3001)
+2. Check client terminal for frontend build errors (localhost:3000)
+3. Confirm there are no client app issues in the browser console. Ask the user to choose which tool they'd prefer via the AskUserQuestion tool and run it for the user:
+  - the `mcp__plugin_wasp_chrome-devtools`
+  - Claude Code's built-in Chrome browser function
+
+### Common Mistakes
+
+| Symptom | Fix |
+|---------|-----|
+| `context.entities.X undefined` | Add entity to `entities: [...]` in main.wasp |
+| Schema changes not applying | Run `wasp db migrate-dev --name <descriptive-name>` |
+| Can't login after email signup with `Dummy` email provider | Check the server logs for the verification link or set SKIP_EMAIL_VERIFICATION_IN_DEV=true in .env.server |
+| Types stale after changes | Restart TS server |
+| Wasp not recognizing changes | **WAIT PATIENTLY** as Wasp recompiles the project. Re-run `wasp start` if necessary.|
+| Persistent weirdness after waiting patiently and restarting. | Run `wasp clean` && `wasp start` |