Help us improve
Share bugs, ideas, or general feedback.
From opensaas-stack
Build applications and features on the OpenSaaS Stack. Use this whenever a user describes building an app, adding functionality, implementing a feature, or asks "how do I implement X" in an OpenSaaS Stack project. Also trigger when the user describes business requirements, data models, or use cases — even if they don't say "OpenSaaS" explicitly.
npx claudepluginhub opensaasau/stack --plugin opensaas-stackHow this skill is triggered — by the user, by Claude, or both
Slash command
/opensaas-stack:opensaas-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Invoke this skill when you detect:
Generates Vibes SaaS app with auth, billing, and live deployment via self-contained pipeline using Agent Teams. Use for one-step SaaS shipping or 'launch/ship it' requests.
Guides building production-ready SaaS MVPs from idea validation and tech stack selection (Next.js, Tailwind, Supabase, Stripe) to multi-tenant architecture, auth, payments, deployment, and launch checklist.
Adds Wasp features like authentication (email/social), email sending, PostgreSQL/SQLite database, Tailwind/ShadCN styling, and app branding/meta tags. Use for configuring full-stack capabilities in Wasp apps.
Share bugs, ideas, or general feedback.
Invoke this skill when you detect:
This skill transforms application requirements into concrete OpenSaaS feature implementations by:
Ask clarifying questions to understand:
Map their needs to OpenSaaS features:
Built-in Features (use opensaas_implement_feature):
authenticationblog (adaptable to many content types)commentsfile-uploadsemantic-searchCustom Features (use opensaas_implement_feature with feature: "custom"):
Implement features in dependency order:
For each feature:
opensaas_implement_feature with the feature IDopensaas_answer_feature with their responsesopensaas_answer_followupAfter implementing all features:
pnpm generate, pnpm db:push)User: "I want to create an app that tracks food consumption"
Clarifying Questions:
authentication feature neededFood listFoodLog listcomments or custom social featuresFeature Mapping:
authentication featureFood list with nutrition dataFoodLog list with relationshipsMealPlan listImplementation:
// 1. Implement authentication
opensaas_implement_feature({ feature: 'authentication' })
// Guide through: email/password, no special roles, basic profile
// 2. Implement custom food database
opensaas_implement_feature({
feature: 'custom',
description:
'Food database with nutritional information (calories, protein, carbs, fats, serving size)',
})
// 3. Implement food logging
opensaas_implement_feature({
feature: 'custom',
description:
'Food log entries where users can record meals with foods, quantities, and timestamps',
})
context.db, never direct Prismaopensaas_feature_docs✅ User clearly understands what you're building ✅ All required features identified and implemented ✅ Generated code follows OpenSaaS best practices ✅ Access control properly configured ✅ Features integrate correctly ✅ User knows how to test and iterate
Authentication + Blog feature (customize for their content type)
Authentication + Custom Product/Order lists + File Upload (product images)
Authentication + Custom Project/Task lists with relationships
Authentication + Custom Topic/Post lists + Comments
Authentication + Custom metrics/data lists + potentially Search
For each scenario, adapt the wizard questions to their specific needs!
When you encounter bugs or missing features in OpenSaaS Stack:
If while building the application you discover:
Use the github-issue-creator agent to create a GitHub issue on the OpenSaasAU/stack repository:
Invoke the github-issue-creator agent with:
- Clear description of the bug or missing feature
- User's use case that triggered the discovery
- Expected vs actual behavior
- Affected files and line numbers
- Your suggested solution (if you have one)
This ensures bugs and feature requests are properly tracked and addressed by the OpenSaaS Stack team.
Example:
If a user needs geolocation tracking but there's no built-in field type for coordinates:
"Feature request: Add geolocation field type for storing latitude/longitude coordinates. User needs this for a location-based app. Should support validation, map UI component, and distance queries."
The agent will create a detailed GitHub issue with the use case and proposed implementation.