gcp-nextjs-bootstrap

To bootstrap a full-stack Next.js app on GCP, this Skill generates browser agent instructions for setting up OAuth, Supabase, Cloud Storage, and Firebase provisioning, then scaffolds your project once environment variables are provided. It enforces a mandatory wait state before writing backend code.

Yes, you can add Firebase and Cloud Storage to an existing Next.js frontend. The Skill supports refactoring or upgrading existing full-stack Next.js codebases by specifying the scope for adding backend services and aligning the scaffolding with RouteGenius conventions.

Scaffolding a Next.js project on GCP requires collecting populated environment variables after the browser agent completes GCP setup, OAuth credentials, Supabase, Cloud Storage, and Firebase provisioning. The Skill enforces a hard wait state until these credentials are provided to ensure a safe start.

Yes, the GCP Next.js bootstrapping process supports OAuth configuration. It generates specific browser agent instruction sets for configuring OAuth credentials alongside Supabase, Cloud Storage, and Firebase provisioning within your GCP project setup.

Next.js backend scaffolding waits for GCP credentials because the Skill enforces a mandatory wait state before any backend code is written. This ensures all environment variables are collected and a safe start is guaranteed for the full-stack project.

The best way to provision a GCP project for a full-stack Next.js application is generating browser agent instruction sets for setup. This approach handles OAuth, Supabase, Cloud Storage, and Firebase provisioning before scaffolding the project to align with RouteGenius conventions.