Bring the modular seed suite (prisma/seed.ts + prisma/seedFiles/N*-create-*.ts) back in sync with the Prisma schema and generate realistic consultation-platform mock data — after schema changes, when seeds fail to compile, or when new models need coverage. Validates with tsc + eslint and only ever seeds a database the user has confirmed is disposable (DATABASE_URL here points at remote Supabase — never reset it unprompted). Use when the user says "update the seeds", "sync seed data with the schema", "my seed file won't compile", or "add seed data for <model>".
Audit and synchronize environment variables from the local .env to the Netlify production deployment — diff the two sets, categorize every variable (missing / localhost-valued / dev-only / wrong / Netlify-only / in-sync), present a masked report, PAUSE for approval, then apply the fixes scoped to the production context and verify. Use when the user says "sync env vars to Netlify", "check the Netlify env vars", "did I push that key to prod", or after adding a new service key to .env.
Triage every review comment on a pull request into legit / BS / already-fixed / partly-fixed / incorrectly-fixed by checking each claim against the CURRENT code, then plan and apply fixes for the legit-pending ones, validate them against a running dev server with MOCK data (never the shared/real DB), pause for the user to review, and on approval commit, push, and resolve the bot review threads (without replying) in a background agent. Use when the user says "triage the PR comments", "are these review comments legit", "go through the PR feedback", "address the Gemini/CodeRabbit comments", or "fix the actionable review comments on PR
Set up local Razorpay testing — test keys, ngrok tunnel, webhook registration, end-to-end test flow. Use when the user asks to "test locally", "set up ngrok", "test razorpay webhooks", "get test card numbers", or needs to verify their Razorpay integration before going live.
Query and manage your Razorpay account directly — check payments, subscriptions, invoices, refunds, customers. Use when the user asks to "check payment status", "query razorpay", "list subscriptions", "look up a customer", "verify an invoice", or needs to run admin operations against the Razorpay API.
Build a self-service billing portal — view subscription, download invoices, cancel, update payment method. Use when the user asks to "build a billing page", "create a customer portal", "add self-service billing", "let users manage subscriptions", or needs a customer-facing account settings page.
Handle failed payments and recover revenue — grace periods, dunning emails, involuntary churn prevention. Use when the user asks about "failed payment handling", "payment recovery", "reduce churn", "dunning emails", "grace period", or needs to recover revenue from declined cards and payment failures.
Production-ready checklist and security hardening for Razorpay integration — rate limiting, error monitoring, compliance. Use when the user asks to "launch to production", "go live", "run the security checklist", "harden my integration", or is preparing a Razorpay integration for real customers.