auth

Authentication and social login integration is implemented by configuring Clerk or Supabase Auth, installing required packages, and scaffolding the UI for login flows. This helper defines the exact installation steps and configuration needed for reproducible auth setups.

Stripe subscriptions and one-time payments are set up by configuring the Stripe SDK, defining product tiers, and implementing webhook endpoints to handle payment events. This helper provides the required UI scaffolding and security guardrails for auditable payment processing.

Yes, the auth integration explicitly supports email verification and password reset flows alongside standard sign-up and login. It provides the necessary configuration and UI scaffolding to manage user profile data and session security across web or mobile projects.

Clerk and Supabase Auth are supported as distinct authentication providers for web and mobile projects requiring login and session management. The helper defines the required configuration for either provider to ensure security guardrails are met.

You should not use this helper for general UI work, database design, or non-auth features. It is strictly scoped to implementing authentication and payments integration using Clerk, Supabase Auth, or Stripe to ensure auditable and reproducible implementations.

Securing Stripe webhooks for subscription management involves defining security guardrails and verifying event signatures to ensure auditable payment processing. This helper outlines the required configuration to safely handle customer portal and webhook endpoints.