Choose backend language (TypeScript / C# / Python)
Choose Cosmos DB mode (Free Tier / Serverless)
Choose network security (VNet Integration / None)
Wait for initialization to complete (progress shown in notification)
Choose to open the project in the current or a new window
Create a Model
Run SwallowKit: Create Model from the command palette (or right-click a models folder)
Enter model name(s), comma-separated for multiple (e.g. User, Product)
The files will be created and automatically opened in the editor
Scaffold CRUD
Run SwallowKit: Scaffold CRUD from Model from the command palette
Select a model file from the QuickPick list
CRUD code (Azure Functions + Next.js BFF + UI components) will be generated
Or right-click directly on a model file in the explorer.
Dev Server
Click the ○ SwallowKit item in the status bar to start/stop the dev server.
The terminal 🐦 SwallowKit Dev will be created automatically.
If your project already has dev-seeds/<environment>/ folders, the extension will offer them before startup and run swallowkit dev --seed-env <environment>.
Dev Seeds Workflow
Run SwallowKit: Create Dev Seed Templates
Enter an environment name such as local
Edit the generated JSON files under dev-seeds/<environment>/
Run SwallowKit: Start Dev Server and choose that environment to seed the Cosmos DB Emulator before startup
Notes:
shared/models/todo.ts maps to dev-seeds/local/todo.json
Each JSON file can contain a single object or an array of objects
Every seed document must include a non-empty string id
If --seed-env is omitted, or the selected environment does not exist, current emulator data is preserved
Add External Connectors
Run SwallowKit: Add Connector from the command palette
Enter a connector name (e.g. mysql)
Select the connector type (RDB or API)
If RDB, select the provider (MySQL / PostgreSQL / SQL Server)
The connector is registered in swallowkit.config.js
Create connector-aware models with SwallowKit: Create Model — the extension will offer to associate the model with a connector
Add Authentication
Run SwallowKit: Add Authentication from the command palette
Select the auth provider (Custom JWT / Static Web Apps / SWA + Custom / None)
The authentication framework is added to the project
Dev Server with Mock Connectors
When connectors are defined in swallowkit.config.js, the Start Dev Server command will ask whether to use mock data (--mock-connectors) so you can develop locally without connecting to real external data sources.
Provision Azure Resources
Run SwallowKit: Provision Azure Resources
Enter resource group name
Optionally enter a subscription ID
The provision command starts in the terminal
Follow the CLI prompts to choose the primary Azure location and the Static Web App location