Opensaasau Stack
- 2 repo stars
- Updated July 27, 2026
- OpenSaasAU/stack
opensaasau-stack is a Claude Code plugin marketplace that delivers OpenSaaS-focused development and migration assistants for Keystone, Prisma, and Next.js stacks.
About
opensaasau-stack is the official Claude Code plugin marketplace from OpenSaasAU/stack for developers shipping on the OpenSaaS stack. With two plugins spanning development and migration, it bundles AI-guided assistants that help you describe features, analyze requirements, generate code, and configure Keystone, Prisma, and related infrastructure without treating every task as a generic coding prompt. founders who chose OpenSaaS over rolling their own auth, admin, and data layer can register this marketplace once and pull plugins tuned to feature-driven workflows, schema evolution, and Next.js-aligned output. Use it during validation when you need a credible data model prototype and during build when migration and configuration dominate your calendar. It is not a general-purpose skill hub; it optimizes for OpenSaaS-specific generation and stack support so agent sessions stay aligned with your chosen SaaS foundation.
- Official marketplace with 2 plugins focused on development and migration for the OpenSaaS stack.
- Feature-driven and AI-guided analysis for describing applications and generating stack-appropriate code.
- Covers Keystone, Prisma, schema work, infrastructure configuration, and Next.js-oriented generation.
- Keywords emphasize complete build support, migration paths, and configuration instead of one-off snippets.
- Curated from OpenSaasAU/stack for solo builders standardizing on OpenSaaS rather than greenfield frameworks.
Opensaasau Stack by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install opensaasau-stack@OpenSaasAU/stackAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 27, 2026 |
| Repository | OpenSaasAU/stack ↗ |
What it does
Install when you are building or migrating an OpenSaaS (Keystone, Prisma, Next.js) product and want Claude Code plugins for AI-guided schema, migration, and stack configuration.
Who is it for?
Best when you're committed to OpenSaaS and want marketplace plugins for stack migration, schema, and feature-driven generation inside Claude Code.
Skip if: Skip if you're not using OpenSaaS, or anyone and only needs unrelated frontend snippets with no backend stack alignment.
What you get
After you add the marketplace, Claude Code can run OpenSaaS-tuned plugins for analysis, code generation, schema work, and migration steps in one workflow.
- Two installable plugins from the official OpenSaaS Stack marketplace
- Agent-assisted schema, migration, and configuration workflows aligned to OpenSaaS
- Feature-driven analysis and generation sessions scoped to your stack
By the numbers
- Plugin count: 2
- Repository: OpenSaasAU/stack
- Categories: development, migration
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
OpenSaaS-specific plugin marketplace, not a generic skills.sh discipline pack or a single MCP server.
FAQ
Who is Opensaasau Stack for?
and small-team developers on the OpenSaaS stack who want Claude Code plugins for migration, schema, and AI-guided development instead of ad hoc prompts.
When should I use Opensaasau Stack?
Use it when validating data models or actively building and migrating Keystone, Prisma, and Next.js pieces of an OpenSaaS application.
How do I add Opensaasau Stack to my agent?
In Claude Code, register the OpenSaasAU/stack plugin marketplace source, install the development or migration plugins you need, then invoke them in sessions tied to your repo.