What problem does it solve? Setting up a cloud backend requires stitching together a database, authentication, file storage, serverless compute, and LLM access across multiple vendors. This Skill guides an AI agent through provisioning and operating Neon's complete set of backend primitives around Lakebase Postgres from a single platform, using the CLI, MCP server, or a no-signup Claimable path. ## Core Features & Use Cases - Backend Primitive Selection: Maps app requirements (login, files, APIs, LLM calls, SQL) to the right Neon primitive — Lakebase Postgres, Managed Better Auth, Object Storage, Functions, or AI Gateway — while preserving existing providers like Clerk, Supabase Auth, or a supplied DATABASE_URL. - Branch-First Development: Drives a copy-on-write branch workflow with neon checkout, env pull, and schema diff so every feature gets an isolated database clone. - Infrastructure as Code: Declares services in a type-safe neon.ts config file and reconciles them with neon status, plan, and deploy, including Function Triggers on cron or storage events. - Use Case: A developer asks an agent to add login and file uploads to a new app. The Skill checks credentials, runs neon init or the Claimable flow, declares auth and buckets in neon.ts, deploys, and verifies the sign-in and upload flow end to end. ## Quick Start Ask the agent to set up a Neon backend with Postgres and authentication for your app, and it will check the CLI, link or claim a project, and provision the services.