Neon
CloudCommonly used with
Skills using Neon (3)
module-add
Wire a backend or infrastructure module (auth, database, payments, email, file storage, deploy config) into an already-scaffolded app. Reads `.workflow/meta.json#stack` for the chosen tech (better-auth, drizzle+neon, stripe, resend, vercel, etc.) and modifies the codebase at the project root to install + configure the module end-to-end. Always idempotent — running twice does not duplicate config. Use when the user says "add auth", "wire up the database", "set up Stripe", "add file uploads", "configure deploy", "module aggiungi auth", or the orchestrator routes here from phase `scaffolded` / `page_generated`. Not for: scaffolding the app (`design-md-to-app`) or building UI (`screenshot-to-page`).
architecture-and-stack
Cloudflare-first platform selection. Decision trees for Workers, D1, R2, KV, DO, Queues, Vectorize, Containers, Sandboxes, Flagship, Agent Memory, Workflows v2. Default stack, override conditions, auth, data patterns, reliability.
neon-cli
Operate Neon Postgres from a coding-agent terminal with the official neonctl CLI and psql, without relying on the Neon MCP server. Covers projects, local project linking, branches, databases, roles, connection strings, SQL execution, transactions, schema diffs, migrations, EXPLAIN, slow-query inspection, and Management API gaps. Use when the agent needs to inspect, query, or modify a Neon database; create, restore, reset, diff, or delete branches; run migrations; manage Neon projects or roles; or when the user says neon-cli, neonctl, query my Neon DB, create a Neon branch, or list my Neon projects. Do not use for application runtime integration with Neon, ORM schema design, continuous monitoring, or Neon MCP server configuration.
Integration detected automatically from skill content. Some results may be false positives.