Wasp Lang Wasp Agent Plugins
wasp-lang-wasp-agent-plugins is a Claude Code plugin for the Build phase that makes your coding agent a Wasp full-stack expert via skills, memory, and subagents.
by wasp-lang · github.com/wasp-lang/wasp-agent-plugins
Turn Claude into a Wasp-aware full-stack copilot with curated skills, memory, and subagents for React, Prisma, auth, and deployment workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install wasp-lang-wasp-agent-plugins@wasp-lang/wasp-agent-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:wasp-lang/wasp-agent-plugins") and the paste-ready config with skillselion.get_install_config("plugin:wasp-lang/wasp-agent-plugins").
What it does
wasp-lang-wasp-agent-plugins equips Claude Code and similar agents with Wasp framework expertise so solo builders do not fight generic React plus Node advice on an opinionated full-stack stack. The plugin combines skills, persistent memory, and subagents oriented around initial project setup, feature development, authentication, Prisma modeling, and deployment-minded workflows described in the repo keywords. Canonical placement is Build / agent-tooling because the value is how your agent edits and reasons about Wasp codebases, though the same guidance spans backend structure, frontend pages, and launch prep. It suits indie SaaS founders who chose Wasp for speed and want the agent to follow framework conventions instead of inventing parallel architectures. Complexity is intermediate: you should already run or plan a Wasp app and use Claude Code plugin registration. This is a framework expert plugin pack, not a replacement for Wasp CLI or hosted CI.
Highlights
- Official-style Wasp bundle: skills, memory, and subagents for coding agents
- Full-stack focus: React client, Node.js server, Prisma data layer, and auth patterns
- Curated waspplugininit and wasppluginhelp flows for first-time and ongoing setup
- Deployment and best-practices guidance embedded for indie SaaS shipping
- Single-plugin marketplace entry from wasp-lang/wasp-agent-plugins
Why builders use it
Generic coding agents give conflicting React and Node advice that breaks Wasp conventions and slows solo full-stack shipping.
After install, your agent follows Wasp-first setup, auth, Prisma, and deployment practices while editing your Wasp project.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 7 stars, 0 votes.
FAQ
Who is wasp-lang-wasp-agent-plugins for?
Developers using Claude Code on Wasp projects who want curated skills, memory, and subagents aligned with official full-stack patterns.
When should I use wasp-lang-wasp-agent-plugins?
Use it throughout Build when scaffolding features, auth, and data models, and when you need deployment-aware guidance before ship.
How do I add wasp-lang-wasp-agent-plugins to my agent?
Register the wasp-lang/wasp-agent-plugins marketplace entry in Claude Code, run waspplugininit-style setup in a Wasp repo, then rely on the bundled help and skills during edits.
Comments
Share how you use wasp-lang-wasp-agent-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.