Skip to main content Inicio Creadores oyi77 1ai-skills ai-saas-builder
ai-saas-builder Takes a problem statement and produces a deployable micro-SaaS product — landing page, auth, payments, database, API, and billing. Use when building micro-SaaS products solo.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/oyi77/1ai-skills --skill ai-saas-builderEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
name ai-saas-builder description Takes a problem statement and produces a deployable micro-SaaS product — landing page, auth, payments, database, API, and billing. Use when building micro-SaaS products solo. domain development license Apache-2.0 tags ["api","builder","coding","saas","software-engineering","testing","money","passive-income"] version 2.0.0 author oyi77 subdomain type dev
Money-Making Overview
This skill ships micro-SaaS products that generate recurring revenue. Each product targets $50-500/mo MRR. At 2-4 products/month × $200 avg MRR = $400-800/mo new MRR. Products compound: 12 months at 3/month with 80% retention = ~$6K/mo portfolio.
Revenue Streams
Your Own SaaS ($50-5K/mo/product) — build and launch your ownSaaS Building Service ($5K-15K/build) — build for clientsSaaS Templates/Source Code ($97-497/sale) — sell the boilerplate
First Action in 60 Minutes
#!/usr/bin/env bash
PROBLEM="$1 "
[[ -z "$PROBLEM " ]] && echo "Usage: $0 'problem statement'" && exit 1
echo "=== Micro-SaaS Generator ==="
echo "Problem: $PROBLEM "
echo ""
echo "Phase 1: Spec Generation"
echo "Phase 2: Tech Stack (Next.js + Stripe + Supabase)"
echo "Phase 3: Scaffold (npx create-t3-app)"
echo "Phase 4: Payment Integration"
echo "Phase 5: Deploy (Vercel)"
echo "Phase 6: Launch Checklist"
echo ""
echo "Target: Ship in 7 days"
echo "Pricing: $19 -49/mo for individuals, $99 -199/mo for teams"
Overview
An end-to-end pipeline for shipping micro-SaaS products as a solo operator. Takes a problem statement and produces a fully deployed, monetizable SaaS with landing page, authentication, payment integration, and billing. Designed for one-person companies to ship 2-4 products per month.
Required Tools
CLI : npx create-t3-app, npx create-next-app, railway, flyctl, vercelPayments : Stripe API key or Lemon Squeezy API keyDatabase : Supabase (PostgreSQL), PlanetScale, or NeonAuth : Clerk, Auth.js, or Supabase AuthDeployment : Vercel (frontend), Railway/Fly.io (backend)Environment : Node.js 18+, npm/pnpm
Capabilities
Generate product spec from a one-line problem statement
Select optimal tech stack based on product type
Scaffold full-stack project with auth, payments, DB
Generate landing page with pricing tiers
Integrate Stripe Checkout or Lemon Squeezy for payments
Deploy to production with CI/CD
Generate launch checklist (Product Hunt, Twitter, IndieHackers)
When to Use
"ai saas builder"
"Takes a problem statement and produces a deployable micro-SaaS product — landing"
You have a business idea and want to ship a working product fast
You need to validate a market before investing weeks of development
You want to build a portfolio of micro-SaaS products for passive income
A client requests a custom SaaS solution
When NOT to Use
Task is about deployment, not development (use deploy skills)
Task is about code review, not writing (use review skills)
You need to understand existing code first (use research skills)
Task is about testing only (use test skills)
Requirements are unclear (clarify first)
Task is trivially simple (single line fix)
Pseudo Code The ai-saas-builder workflow follows a standard pipeline pattern.
# ai-saas-builder primary flow
input = prepare(raw_data)
result = process(input, config={auth, billing, builder, database, deployable})
validate(result)
deliver(result)
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
Phase 1: Spec Generation
cat << 'SPEC' > spec.md
{one_sentence_problem}
{one_sentence_solution}
{user_persona}
1. {feature_1} - must have
2. {feature_2} - must have
3. {feature_3} - nice to have
- Free tier: {limits}
- Pro: ${price} /mo
- Enterprise: custom
- Frontend: {framework}
- Backend: {api_type}
- Database: {db}
- Auth: {auth_provider}
- Payments: {payment_provider}
- Hosting: {platform}
SPEC
Phase 2: Tech Stack Selection def select_stack (product_type, requirements ):
"""Select optimal stack based on product characteristics."""
stacks = {
"crud_app" : {
"framework" : "Next.js 14 (App Router)" ,
"api" : "tRPC or Next.js API Routes" ,
"db" : "Supabase (PostgreSQL)" ,
"auth" : "Clerk" ,
"payments" : "Stripe Checkout" ,
"hosting" : "Vercel"
},
"ai_app" : {
"framework" : "Next.js 14" ,
"api" : "Next.js API Routes + streaming" ,
"db" : "Supabase + pgvector" ,
"auth" : "Clerk" ,
"payments" : "Lemon Squeezy" ,
"hosting" : "Vercel"
},
"marketplace" : {
"framework" : "Next.js 14" ,
"api" : "tRPC" ,
"db" : "Supabase" ,
"auth" : "Supabase Auth" ,
"payments" : "Stripe Connect" ,
"hosting" : "Vercel"
},
"api_product" : {
"framework" : "None (API only)" ,
"api" : "Hono or Fastify" ,
"db" : "PlanetScale (MySQL)" ,
"auth" : "API keys + JWT" ,
"payments" : "Stripe metered billing" ,
"hosting" : "Fly.io or Railway"
}
}
return stacks.get(product_type, stacks["crud_app" ])
Phase 3: Scaffolding
npx create-t3-app@latest my-saas --tailwind --trpc --prisma --nextAuth
npx create-next-app@latest my-saas --typescript --tailwind --app
cd my-saas
npx supabase init
pnpm add stripe @stripe/stripe-js
pnpm add @clerk/nextjs
pnpm add zod react-hook-form @tanstack/react-query
my-saas/
├── src/
│ ├── app/
│ │ ├── (marketing)/
│ │ ├── (app)/
│ │ ├── api/
│ │ └── layout.tsx
│ ├── components/
│ │ ├── ui/
│ │ ├── landing/
│ │ └── billing/
│ ├── lib/
│ │ ├── stripe.ts
│ │ ├── db.ts
│ │ └── auth.ts
│ └── server/
│ ├── routers/
│ └── stripe-webhook.ts
├── prisma/
│ └── schema.prisma
└── .env.local
Phase 4: Payment Integration
import Stripe from 'stripe' ;
const stripe = new Stripe (process.env .STRIPE_SECRET_KEY !);
export async function POST (req : Request const { priceId } = await req.json ();
const session = await stripe.checkout .sessions .create ({
mode : 'subscription' ,
payment_method_types : ['card' ],
line_items : [{ price : priceId, quantity : 1 }],
success_url : `${process.env.NEXT_PUBLIC_URL} /dashboard?success=true` ,
cancel_url : `${process.env.NEXT_PUBLIC_URL} /pricing` ,
});
return Response .json ({ url : session.url });
}
export async function POST (req : Request const body = await req.text ();
const sig = req.headers .get ('stripe-signature' )!;
const event = stripe.webhooks .constructEvent (body, sig, webhookSecret);
switch (event.type ) {
case 'checkout.session.completed' :
await db.subscription .create ({
data : {
userId : event.data .object .metadata .userId ,
stripeCustomerId : event.data .object .customer ,
stripeSubscriptionId : event.data .object .subscription ,
status : 'active' ,
}
});
break ;
case 'customer.subscription.deleted' :
await db.subscription .update ({
where : { stripeSubscriptionId : event.data .object .id },
data : { status : 'cancelled' }
});
break ;
}
return Response .json ({ received : true });
}
Phase 5: Deploy
npx vercel --prod
railway login
railway init
railway up
flyctl launch
flyctl deploy
Phase 6: Launch Checklist ## Launch Checklist
- [ ] Landing page live with pricing
- [ ] Stripe/Lemon Squeezy checkout working
- [ ] Webhook handling subscription events
- [ ] Auth flow (signup, login, logout)
- [ ] Dashboard with core feature
- [ ] Error pages (404, 500)
- [ ] SEO meta tags + OG image
- [ ] Analytics (Plausible/PostHog)
- [ ] Submit to Product Hunt
- [ ] Post on Twitter/X with demo
- [ ] Post on IndieHackers
- [ ] Submit to relevant directories
- [ ] Set up customer support (Crisp/Intercom)
Error Handling Error Cause Fix Stripe webhook 400 Signature mismatch Verify STRIPE_WEBHOOK_SECRET matches Stripe dashboard Auth callback fails Wrong redirect URI Check NEXTAUTH_URL or Clerk allowed redirects DB connection timeout Connection pool exhausted Use Supabase connection pooler (port 6543) Deploy fails Missing env vars Check all required env vars are set in platform Payment succeeds but no access Webhook not firing Test with stripe listen --forward-to localhost
Common Patterns
Freemium with Usage Limits
const usage = await db.usage .findUnique ({ where : { userId } });
if (usage.count >= FREE_TIER_LIMIT ) {
throw new TRPCError ({ code : 'FORBIDDEN' , message : 'Upgrade to Pro' });
}
Multi-Tenant SaaS
const org = await db.organization .findUnique ({
where : { id : input.orgId },
include : { members : { where : { userId : session.user .id } } }
});
if (!org.members .length ) throw new TRPCError ({ code : 'FORBIDDEN' });
Landing Page Template
Hero section with problem/solution
Feature grid (3-6 features)
Pricing table (Free/Pro/Enterprise)
Social proof (testimonials, logos)
CTA with email capture
FAQ section
How to Use
Understand the requirement and existing codebase patterns
Design the solution with error handling and testability in mind
Implement incrementally with tests for each change
Verify against expected outcomes (manual and automated)
Document usage, edge cases, and integration points
Review with team before merging to shared branches
Red Flags
Skipping tests to ship faster : Untested code breaks in production when you least expect itNo error handling in production code : Unhandled errors crash services and lose user dataHardcoded configuration values : Hardcoded values prevent environment switching and leak secretsIgnoring security implications : Missing input validation, auth bypasses, and injection vulnerabilitiesOver-engineering simple solutions : Premature abstraction adds complexity without proportional benefit
Verification
Process
Analyze the task requirements
Apply domain expertise
Verify output quality
Anti-Rationalization Table Excuse Truth "The market is saturated" 99% of SaaS products have <100 customers "I need a co-founder" Solo founders ship 2x faster "It needs more features first" Your first 10 customers will tell you what to build
Output Format On completion: "[Product name] shipped in [N] days, $[N]/mo pricing, $[N] projected MRR at 50 customers"
