Does Skene work with Remix?

Yes! Skene is framework-agnostic and works with Remix, Supabase, and your auth provider. The Skene SDK integrates with your existing codebase by analyzing your database schema, API routes, and authentication setup. After running `npx skene init`, Skene automatically detects your stack and generates the appropriate configuration.

Is the manual implementation code secure?

The manual code shown above is a simplified example and has several security concerns: it lacks proper input validation, doesn't handle SQL injection risks, and has no rate limiting. Additionally, the polling approach creates unnecessary database load. Skene handles all of these concerns automatically with built-in security best practices, proper error handling, and optimized queries.

How long does it take to implement Retention Loops manually vs with Skene?

Implementing Retention Loops manually typically takes 2-3 days of development time, including setting up workers, writing database queries, handling edge cases, and testing. With Skene, you can install the same functionality in under 5 minutes by copying the prompt into Cursor or Claude Code. Skene automatically generates the `skene.config.ts` file and integrates with your existing infrastructure.

How to Fix Retention Loops in Remix + Supabase Applications | Skene Growth Audit

What's Missing in Standard Remix + Supabase Architecture

Supabase's real-time subscriptions are powerful, but without custom event tracking, you can't identify when users become inactive. Unlike Firebase, Supabase doesn't have built-in analytics, so you need to implement your own activity monitoring. RLS policies can also complicate event tracking if not configured correctly.

Standard Remix + Supabase Flow vs Optimized Skene Flow

Standard Flow

1

User completes onboarding

2

User activity tracked manually (if at all)

3

No automated re-engagement when activity drops

Skene Flow

1

Monitor Supabase 'events' table for user activity patterns via real-time subscriptions

2

Detect when user becomes dormant (no activity for 7 days)

3

Trigger re-engagement email sequence with personalized content

4

Track re-engagement success and adjust campaigns

Visual comparison of the flows:

Loading diagram...

How Skene Fixes This

We created a Skene Prompt that installs retention infrastructure into Remix + Supabase. It uses Supabase's real-time subscriptions to monitor user activity and automatically triggers re-engagement campaigns when users become dormant.

Implementation Comparison

Using Skene Infrastructure

Auto-managed state. Installed via Prompt.

Install via Prompt

cursor.mdc

@task: Initialize Skene.
@action: Analyze my local code, validating subscription via `npx skene login`, and generate `skene.config.ts` to implement the Retention Loop pattern for Remix + Supabase.

Copy Skene Prompt for Cursor

Generated skene.config.ts

skene.config.ts

// skene.config.ts - The Automated Way
import { defineLoop } from '@skene/sdk';

export default defineLoop({
  type: 'retention',
  opinion: 'Detect dormant users and trigger personalized re-engagement campaigns',
  steps: [
    {
      trigger: {
        type: 'schedule',
        cron: '0 9 * * *' // Daily at 9 AM
      },
      condition: {
        type: 'query',
        query: `SELECT * FROM users WHERE last_activity_at < NOW() - INTERVAL '7 days' AND re_engagement_sent = false`,
        timeout: '10m'
      },
      action: {
        type: 'email',
        provider: 'resend',
        template: 're_engagement',
        personalization: {
          name: '{{user.name}}',
          lastActivity: '{{user.last_activity_at}}'
        }
      }
    }
  ],
  recovery: {
    retries: 3,
    backoff: 'exponential'
  }
});