privy-production-release

Validates Privy, CSP, and CORS gates before Vercel and AWS production releases.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/IagoPrandi/ai-dealer --skill privy-production-release-iagoprandi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: privy-production-release
Source: https://github.com/IagoPrandi/ai-dealer/tree/main/.claude/skills/privy-production-release
Command: npx skills add https://github.com/IagoPrandi/ai-dealer --skill privy-production-release-iagoprandi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a Privy-enabled Solana DApp to production involves many security gates—dashboard settings, CSP headers, CORS origins, and app ID promotion—that are easy to miss and dangerous to get wrong. This Skill turns that release process into an explicit, evidence-based checklist so no gate is silently skipped. ## Core Features & Use Cases - Privy dashboard gating: Verifies allowed domains, email OTP, MFA, session duration, and embedded Solana wallet settings against official Privy security guidance. - CSP and anti-clickjacking enforcement: Requires an enforced Content-Security-Policy header, frame-ancestors 'none', and X-Frame-Options on every production route. - CORS and AWS edge validation: Checks Terraform web_origins, WEB_ORIGIN, and worker CORS origins against the exact player-web origin list with deny-by-default smoke tests. - Use Case: Before promoting a new build of the player web app to Vercel production, run this Skill to confirm the production Privy app ID is set on the Production scope only, then verify CSP, CORS, and wallet flows on the live domain. ## Quick Start Ask the AI to run the Privy production release gate checklist for the upcoming Vercel and AWS deployment and report each gate as passed, failed, or not verifiable.

Frequently Asked Questions about privy-production-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a Privy production release for a Next.js app?▼

Verify the production Privy dashboard settings, enforce a restrictive Content-Security-Policy, confirm exact CORS origins, then set NEXT_PUBLIC_PRIVY_APP_ID on the Vercel Production scope only. A fresh production build is mandatory because NEXT_PUBLIC variables are embedded at build time.

What Content-Security-Policy does Privy require for Next.js?▼

Privy's guidance requires default-src 'self', frame-ancestors 'none', and connect-src allowing auth.privy.io, WalletConnect hosts, and your Solana RPC. A meta tag is insufficient for frame-ancestors, so the policy must be emitted as an HTTP header on every route.

Can I reuse the development Privy app ID in production?▼

No. Privy has separate development and production apps, and the production app ID must come from the Privy dashboard. Never infer it from a development app, and confirm the values differ without printing either identifier in logs.

Why does my production deployment fail when NEXT_PUBLIC_PRIVY_APP_ID is missing?▼

The build intentionally fails because the resolvePrivyAppId production check requires the variable to be present. Set it on the web Vercel project Production scope and trigger a fresh build, since NEXT_PUBLIC variables are embedded at build time.

When should I not use this release checklist?▼

Do not use it for local, preview, or devnet-only development, since it targets user-facing production deployments. It also does not authorize deployments by itself and does not cover real-SOL mainnet value flow, which requires separate PRD M9 readiness gates.