Skill Detail

Build spec-driven full-stack apps with Wasp

Use Wasp when an agent needs to scaffold or modify a React, Node.js, and Prisma app from a compact declarative spec with auth, RPC, jobs, email, and deployment conventions.

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Security Reviewed
⭐ 18.7k GitHub stars ⬇ 17.6k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill build-spec-driven-full-stack-apps-with-wasp Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Wasp CLI, Node.js, npm, React, Node.js server runtime, Prisma
Install & setup
Install the official CLI with npm i -g @wasp.sh/wasp-cli@latest, then follow the Wasp quick start and agent integration docs to create or modify the app through main.wasp.ts and related React, Node.js, and Prisma files.
Author
wasp-lang
Publisher
Organization
Last updated
Sep 20, 2026
Quick brief

Use Wasp when a coding agent needs to turn a product brief into a small full-stack web app without hand-assembling auth, RPC, background jobs, email, Prisma wiring, and deployment structure. The operator should invoke this when the task is to create or evolve an app through a high-level Wasp specification, then let the agent fill in React and Node.js logic inside the generated project boundaries. This is better than using Wasp as a normal framework only when the user wants an agent to preserve a reviewable application spec and avoid sprawling boilerplate across the stack. The scope boundary is spec-driven app scaffolding and maintenance for Wasp projects; it is not a generic React, Node.js, Prisma, or deployment skill.

How it works

What this skill actually does

Inputs and prerequisites: Wasp CLI, Node.js, npm, React, Node.js server runtime, Prisma.

Setup notes: Install the official CLI with npm i -g @wasp.sh/wasp-cli@latest, then follow the Wasp quick start and agent integration docs to create or modify the app through main.wasp.ts and related React, Node.js, and Prisma files.

Source and verification boundary: use https://wasp.sh/docs as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.