Orchestre

Appearance

MakerKit Recipe Prompts ​

Commercial License Required

MakerKit requires a commercial license. While Orchestre can help you build with it, you must obtain a valid license from MakerKit for commercial use.

Overview ​

MakerKit v2.11.0 provides 8 specialized recipe prompts that implement common SaaS patterns. These recipes go beyond basic features to provide production-ready implementations of advanced functionality.

How Recipes Work ​

  1. Context Analysis: Examines your project structure
  2. Dependency Check: Ensures prerequisites are met
  3. Code Generation: Creates files and modifications
  4. Integration: Connects with existing features
  5. Documentation: Updates CLAUDE.md files

Available Recipes ​

Authentication & Security ​

/template recipe-otp-verification ​

Access: /template recipe-otp-verification or /t recipe-otp-verification

Implements OTP (One-Time Password) verification for sensitive actions.

What It Creates:

  • OTP generation and verification system
  • Email delivery integration
  • Rate limiting and security measures
  • UI components for OTP input
  • Verification flows for critical actions

Use Cases:

  • Account deletion confirmation
  • Payment method changes
  • Team ownership transfers
  • API key generation
  • Data export requests

Example:

bash
/template recipe-otp-verification delete-account
# Creates OTP verification for account deletion with:
# - Email notification
# - 6-digit code generation
# - 10-minute expiration
# - 3 attempt limit

Billing Models ​

/template recipe-credit-billing ​

Access: /template recipe-credit-billing or /t recipe-credit-billing

Implements a credit/token-based billing system for AI and API services.

What It Creates:

  • Credit tracking database schema
  • Purchase and usage flows
  • Credit balance management
  • Usage metering integration
  • Billing dashboard components

Features:

  • Pre-paid credit packages
  • Usage-based deduction
  • Low balance alerts
  • Auto-recharge options
  • Usage analytics

Example:

bash
/template recipe-credit-billing ai-tokens
# Creates credit system with:
# - Token packages ($10 = 1000 tokens)
# - Per-request deduction
# - Balance checking middleware
# - Purchase flow integration

/template recipe-per-seat-billing ​

Access: /template recipe-per-seat-billing or /t recipe-per-seat-billing

Implements team member-based pricing with tiered discounts.

What It Creates:

  • Seat management system
  • Tiered pricing calculator
  • Billing sync with Stripe
  • Team invitation limits
  • Seat adjustment flows

Pricing Tiers Example:

  • 1-5 seats: $10/seat
  • 6-20 seats: $8/seat
  • 21-50 seats: $6/seat
  • 51+ seats: $5/seat

Example:

bash
/template recipe-per-seat-billing tiered
# Creates per-seat billing with:
# - Automatic tier calculation
# - Proration for mid-cycle changes
# - Seat limit enforcement
# - Upgrade/downgrade flows

/template recipe-metered-billing ​

Access: /template recipe-metered-billing or /t recipe-metered-billing

Implements usage-based billing for APIs, bandwidth, or compute resources.

What It Creates:

  • Usage tracking infrastructure
  • Stripe metered billing integration
  • Real-time usage dashboard
  • Usage alerts and limits
  • Billing period reports

Use Cases:

  • API call billing
  • Bandwidth usage
  • Storage consumption
  • Compute minutes
  • Email sends

Example:

bash
/template recipe-metered-billing api-calls
# Creates metered billing for API usage with:
# - Real-time usage tracking
# - Hourly sync to Stripe
# - Usage analytics dashboard
# - Overage notifications

Team & Organization Features ​

/template recipe-super-admin ​

Access: /template recipe-super-admin or /t recipe-super-admin

Implements a comprehensive admin panel for SaaS management.

What It Creates:

  • Super admin role and permissions
  • Admin dashboard with metrics
  • User management interface
  • Organization oversight tools
  • System configuration panel

Features:

  • User impersonation
  • Organization switching
  • Billing overrides
  • Feature flags management
  • System health monitoring

Example:

bash
/template recipe-super-admin full
# Creates complete admin system with:
# - Protected admin routes
# - Analytics dashboard
# - User/org management
# - System settings
# - Audit logging

/template recipe-projects-model ​

Access: /template recipe-projects-model or /t recipe-projects-model

Implements multi-project support within organizations.

What It Creates:

  • Projects database schema
  • Project-level permissions
  • Project switching UI
  • Resource scoping
  • Project settings

Architecture:

Organization
  └── Projects
       ├── Members (inherited + project-specific)
       ├── Resources (scoped to project)
       └── Settings (project-level)

Example:

bash
/template recipe-projects-model workspace
# Creates project system with:
# - Project CRUD operations
# - Member management
# - Resource isolation
# - Activity tracking
# - Project templates

/template recipe-team-only-mode ​

Access: /template recipe-team-only-mode or /t recipe-team-only-mode

Disables personal accounts, requiring all users to be part of organizations.

What It Creates:

  • Modified authentication flow
  • Automatic organization creation
  • Team-first onboarding
  • Removed personal workspace UI
  • Organization-only guards

Use Cases:

  • B2B SaaS applications
  • Enterprise software
  • Team collaboration tools
  • Corporate platforms

Example:

bash
/template recipe-team-only-mode b2b
# Configures team-only mode with:
# - Organization creation on signup
# - No personal workspace option
# - Team invitation flows
# - Organization-scoped data

Analytics & Monitoring ​

/template recipe-analytics ​

Access: /template recipe-analytics or /t recipe-analytics

Integrates privacy-friendly analytics with multiple providers.

What It Creates:

  • Analytics provider abstraction
  • Event tracking system
  • Conversion tracking
  • Custom event definitions
  • Privacy compliance

Supported Providers:

  • Plausible
  • Fathom
  • Matomo
  • PostHog
  • Google Analytics (with consent)

Example:

bash
/template recipe-analytics multi-provider
# Creates analytics system with:
# - Provider switching
# - Event tracking API
# - Goal conversions
# - User properties
# - GDPR compliance

Using Recipe Prompts ​

Basic Usage ​

bash
# Using full path
/template recipe-[name] [options]

# Using shorthand
/t recipe-[name] [options]

Intelligent Adaptation ​

Each recipe prompt:

  1. Analyzes your current project structure
  2. Identifies integration points
  3. Adapts to your existing patterns
  4. Maintains consistency with your codebase
  5. Updates relevant documentation

Composition ​

Recipes can be combined for complex features:

bash
# AI SaaS with credit billing and projects
/t recipe-credit-billing
/t recipe-projects-model
/t recipe-analytics

# B2B platform with seat billing
/t recipe-team-only-mode
/t recipe-per-seat-billing
/t recipe-super-admin

Best Practices ​

1. Order of Implementation ​

For new projects:

  1. Authentication recipes first
  2. Organization/team structure
  3. Billing model
  4. Additional features

2. Testing Recipes ​

Each recipe includes:

  • Unit tests for core logic
  • Integration tests for flows
  • E2E tests for critical paths

3. Customization ​

Recipes are starting points:

  • Modify generated code to fit your needs
  • Extend with additional features
  • Adapt UI to your design system

4. Documentation ​

After implementing a recipe:

  • Update your project README
  • Document any customizations
  • Add to your team playbook

Technical Details ​

File Structure ​

Recipes typically create:

app/
  ├── (recipe-name)/
  │   ├── components/
  │   ├── actions/
  │   └── page.tsx
  ├── api/
  │   └── (recipe-name)/
packages/
  └── (recipe-name)/
      ├── src/
      ├── package.json
      └── tsconfig.json

Database Impact ​

Most recipes include:

  • Migration files
  • RLS policies
  • Indexes for performance
  • Seed data for development

Troubleshooting ​

Common Issues ​

"Recipe prerequisites not met"

  • Ensure MakerKit is properly initialized
  • Check that required features are enabled
  • Verify database migrations are current

"Integration conflicts detected"

  • Review existing implementations
  • Use --force to override (carefully)
  • Manually resolve conflicts

"Recipe partially applied"

  • Check error logs
  • Review generated files
  • Re-run with --continue flag

Getting Help ​

  1. Check recipe-specific documentation
  2. Review generated TODO comments
  3. Consult MakerKit documentation
  4. Use /discover-context to understand integration

Next Steps ​

Built with ❤️ for the AI Coding community, by Praney Behl

Copyright © 2025 Orchestre