Deploy a web application to production by exploring the codebase first, then walking one of three lanes the user picks: Vercel (managed, default for Next.js), Kubernetes (existing cluster, GitOps-aware), or a virtual machine over SSH (systemd + reverse proxy). Discovers the framework, build output, env contract, database/migration story, and any existing deploy config before proposing anything; asks the user for the target, then executes that lane end to end and smoke-tests the result. House-stack aware (Next.js 16 standalone, Drizzle + Neon, committed .npmrc date pin) but works for any Node web app.
Bootstrap a new web app from the kubeden `app-nextjs-01` template — Next.js 16 (App Router, src/, TS) with Neon Auth, Data API, Object Storage, and AI Gateway pre-wired as lazy typed clients, Drizzle schema FK'd into neon_auth, Tailwind v4 + shadcn/ui (neutral), and a proxy.ts route gate. Locates the template (local kubeden checkout, else GitHub), copies it into the target directory, re-identifies it (package name, PROJECT.md brief, metadata), installs, and verifies build + boot. Use to start any Neon-based project without re-scaffolding stage 1; the web-development set-* skills (landing, backend, dashboard) build on the result by reading the same PROJECT.md brief.
Passwordless, OTP-only email auth for a Next.js App Router app, with smtpfa.st as the mail rail. Installs the full loop: six-digit codes hashed at rest, one live code per email, attempt caps counted in the database, timing-safe verification, per-IP and per-email rate limits, DB-backed sessions behind an httpOnly cookie, and a two-step sign-in form with paste-aware code boxes. Login and signup collapse into one flow — the account is minted on the first verified code. Works locally with zero mail config (codes print to the server log). Use when an app wants email sign-in without passwords; not a bolt-on second factor, and not an OAuth replacement — it composes next to OAuth fine.
Wire the backend (stage 3) of a web app whose foundation already exists (see set-project-structure). Turns every placeholder seam — auth, calendar/data + quota, object storage, AI gateway + token metering, Stripe payments — into a working, server-authoritative backend, with a schema delta + migration for anything the foundation left out (AI usage, entry attachments, webhook idempotency). Reads project specifics from PROJECT.md. Mounts the drop-in auth UI on /login so auth is testable, but builds NO bespoke UI — it exposes clean endpoint + server-helper contracts that the dashboard stage (set-dashboard) consumes. STOPS at one plan gate before building. Use after the landing stage, before the dashboard UI. The correctness half of the app: money and limits must be exactly right.
Build the gated dashboard UI (stage 4) of a web app whose backend already works (see set-app-backend). Reads project specifics from PROJECT.md, studies the wired design tokens and reference sites, then builds the full-screen app shell (left sidebar + user block + dropup), the interactive weekly calendar with create/edit/delete entry modals, the shared glassmorphic settings/billing modal (3/5 × 3/5, centered, its own sub-sidebar), and a live streaming AI-chat view with per-user calendar context — all consuming the backend stage's endpoint + server-helper contracts. STOPS at a design-language gate before building and does a visual self-review after. Engineered to defeat generic "AI dashboard" output. Touches only the gated route + its components — never schema, env, lib clients, enforcement, or the marketing route.
Build the landing/marketing page (stage 2) of a web app whose foundation already exists (see set-project-structure). Reads project specifics from PROJECT.md, studies the brief's reference sites and wired design tokens, writes real copy from the brief, then builds the marketing route and components/landing/* with tasteful motion — STOPPING at a design-language gate before building and doing a visual self-review after. Engineered to defeat generic "AI landing page" output: enforces the project's specific voice and design language. Use after the foundation stage, before dashboard work. Touches only the marketing route and landing components — never schema, env, lib clients, or gated areas.
Scaffold the foundation (stage 1) of a modern web app — Next.js (App Router, src/, TS) with Neon (Auth / Data API / Storage / AI Gateway), Drizzle, Stripe, Tailwind + shadcn/ui, on Vercel. Reads project specifics from a PROJECT.md brief in the target repo (generates it via Q&A if missing), verifies current/compatible versions, lays the directory structure, DB schema, env keys, design tokens, and placeholder clients, then STOPS at an approval gate before building any UI. Use at the very start of a new web project, before landing/dashboard work. Does not build features — only the foundation/seams.
Install or adapt GitHub issue-driven Claude Code automation that creates Neon database branches, opens agent pull requests, deploys live preview environments, comments preview URLs, and cleans up previews across Argo CD/GitOps, Vercel, Cloudflare Pages, Railway, Fly.io, or Render.