What's Missing in Standard Next.js + RevenueCat Architecture
While Next.js + RevenueCat handles billing correctly, it doesn't monitor feature usage or trigger upgrade prompts when free users hit limits. Payment processing works, but usage tracking is separate.
Standard Next.js + RevenueCat Flow vs Optimized Skene Flow
User subscribes via RevenueCat
Subscription status stored in your database
Features accessible but no usage limits enforced
Track usage in your database 'subscriptions' and 'usage' tables
Detect when free tier user hits limit (e.g., 1GB storage used)
Block feature access and trigger upgrade prompt email
Track conversion from free to paid
Visual comparison of the flows:
Loading diagram...
How Skene Fixes This
This Skene Prompt installs usage tracking that correlates your database feature usage with RevenueCat subscription tiers. When free users hit limits (like 100 API calls), it automatically blocks features and sends upgrade prompts.
Implementation Comparison
Using Skene Infrastructure
Install via Prompt
@task: Initialize Skene.
@action: Analyze my local code, validating subscription via `npx skene login`, and generate `skene.config.ts` to implement the Freemium Gating pattern for Next.js + RevenueCat.Copy Skene Prompt for Cursor
Generated skene.config.ts
// skene.config.ts - The Automated Way
import { defineLoop } from '@skene/sdk';
export default defineLoop({
type: 'freemium',
opinion: 'Enforce usage limits for free tier users and trigger upgrade prompts',
steps: [
{
trigger: {
type: 'api',
endpoint: '/api/features/*',
method: 'POST'
},
condition: {
type: 'usage',
limit: {
free: 100,
paid: Infinity
},
period: '30d'
},
action: {
type: 'block',
message: 'You've reached your free tier limit. Upgrade to continue.',
upgradePrompt: {
type: 'email',
provider: 'resend',
template: 'upgrade_prompt'
}
}
}
],
recovery: {
retries: 0 // No retries for blocking actions
}
});