lakebase-app-dev-kit

lakebase-app-dev-kit

Lakebase-backed application development kit. The shared foundation that the lakebase-scm-extension (VS Code/Cursor) and coding agents – Claude Code (terminal), Claude Desktop, OpenAI Foundry, Cursor, and Databricks Genie Code – all consume. One canonical implementation; multiple presentation layers and workflow-domain skills.

Workflow domains (kit-authored, one skill each, hosted under skills/):

• lakebase-scm-workflows – paired-branch source control, schema diff, PR flow, runner setup.
• lakebase-release-workflows – branching + release methodology for Lakebase-paired projects.
• lakebase-sftdd-workflows – Spec-First Test-Driven Development (SFTDD) with evolutionary design, against paired branches: Spec Driven Development (SDD) for the design lane (/design) and Test Driven Development (TDD) for the build lane (/build), with a deterministic orchestrator and HITL gates at every phase boundary. Specs, architecture, and database all evolve increment over increment.
• Future domains include deploying to Databricks Apps and beyond.

Shared canon (kit-authored, unprefixed because not Lakebase-specific):

• software-design-principles – SOLID, DRY, clean code, layered architecture, cross-cutting concerns, NFRs. Imported by the workflow domain skills.

Vendored upstream skills (also under skills/, synced from databricks/devhub):

• databricks-core – CLI basics, authentication, profile selection. Parent skill referenced by databricks-lakebase.
• databricks-lakebase – canonical agent reference for the databricks postgres CLI surface (project / branch / endpoint / database resource shapes, name formats, "never delete the production branch" rule, discovery via -h).

The vendored skills are read-only mirrors of upstream. To pull the latest, run npm run sync:devhub (check drift with npm run check:devhub) and commit any diff in a focused PR. Kit-authored skills wrap the operations; vendored skills document the CLI surface those operations are built on. Agents that consume the kit (e.g. via install.sh) inherit both layers.

The "app dev" framing covers applications, services, libraries, and any other software that uses Lakebase – including projects deployed to Databricks Apps.

What this is

• scripts/ – Node/TypeScript modules that implement the operations: GitHub auth + repo + runner + secrets, Lakebase get-connection + branch lifecycle + schema-diff + create-project + scaffold, git wrappers, and shared utilities. Each has CLI and module entry points.
• skills/<domain>/SKILL.md – Per-workflow-domain agent surface. A coding agent reads this and drives the same scripts the extension does.
• apps/mcp-server/ – Single MCP server exposing every skill's tools to MCP-capable agents (Claude Desktop, OpenAI Codex, Cursor-via-MCP).
• tools/openai-foundry/ – Pre-rendered OpenAI Foundry / Codex tool spec covering the same tool surface.
• templates/ – Project templates the kit ships into newly-bootstrapped Lakebase-paired projects.
• tests/ – Vitest BDD tests. Live Lakebase paths skip cleanly when LAKEBASE_TEST_* env vars aren't set.

Single-seam credential handoff

Two narrow auth seams, both enforced by CI grep guards:

• scripts/lakebase/get-connection.ts is the only path that mints Lakebase credentials. Every other workflow op calls getConnection(). See skills/lakebase-scm-workflows/references/get-connection.md.
• scripts/github/auth.ts is the only path that resolves a GitHub token. Fallback chain: GITHUB_TOKEN env → VS Code getSession (in the extension host only) → gh auth token. See skills/lakebase-scm-workflows/references/github-auth.md.

Install

Prerequisites