Claude-skill-registry base44-cli
Use for Base44 CLI operations and project initialization. Triggers: user wants to create/initialize a new Base44 project; user mentions CLI commands (npx base44, yarn base44, create, login, logout, whoami, deploy, entities push, site deploy, functions deploy); directory is empty or missing base44/config.jsonc; user says 'create a Base44 app/project', 'setup Base44', 'deploy to Base44', 'push entities'. This skill is the PREREQUISITE for base44-sdk - always use this first for new projects before building features.
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/base44-cli" ~/.claude/skills/majiayu000-claude-skill-registry-base44-cli && rm -rf "$T"
skills/data/base44-cli/SKILL.mdBase44 CLI
Create and manage Base44 apps (projects) using the Base44 CLI tool.
⚡ IMMEDIATE ACTION REQUIRED - Read This First
This skill activates on ANY mention of "base44" or when a
base44/ folder exists. DO NOT read documentation files or search the web before acting.
Your first action MUST be:
- Check if
exists in the current directorybase44/config.jsonc - If NO (new project scenario):
- This skill (base44-cli) handles the request
- Guide user through project initialization
- Do NOT activate base44-sdk yet
- If YES (existing project scenario):
- Transfer to base44-sdk skill for implementation
- This skill only handles CLI commands (login, deploy, entities push)
Critical: Local Installation Only
NEVER call
base44 directly. The CLI is installed locally as a dev dependency and must be accessed via a package manager:
(npm - recommended)npx base44 <command>
(yarn)yarn base44 <command>
(pnpm)pnpm base44 <command>
WRONG:
base44 login
RIGHT: npx base44 login
MANDATORY: Authentication Check at Session Start
CRITICAL: At the very start of every AI session when this skill is activated, you MUST:
-
Check authentication status by running:
npx base44 whoami -
If the user is logged in (command succeeds and shows an email):
- Continue with the requested task
-
If the user is NOT logged in (command fails or shows an error):
- STOP immediately
- DO NOT proceed with any CLI operations
- Ask the user to login manually by running:
npx base44 login
- Wait for the user to confirm they have logged in before continuing
This check is mandatory and must happen before executing any other Base44 CLI commands.
Overview
The Base44 CLI provides command-line tools for authentication, creating projects, managing entities, and deploying Base44 applications. It is framework-agnostic and works with popular frontend frameworks like Vite, Next.js, and Create React App, Svelte, Vue, and more.
When to Use This Skill vs base44-sdk
Use base44-cli when:
- Creating a NEW Base44 project from scratch
- Initializing a project in an empty directory
- Directory is missing
base44/config.jsonc - User mentions: "create a new project", "initialize project", "setup a project", "start a new Base44 app"
- Deploying, pushing entities, or authenticating via CLI
- Working with CLI commands (
)npx base44 ...
Use base44-sdk when:
- Building features in an EXISTING Base44 project
already existsbase44/config.jsonc- Writing JavaScript/TypeScript code using Base44 SDK
- Implementing functionality, components, or features
- User mentions: "implement", "build a feature", "add functionality", "write code"
Skill Dependencies:
is a prerequisite forbase44-cli
in new projectsbase44-sdk- If user wants to "create an app" and no Base44 project exists, use
firstbase44-cli
assumes a Base44 project is already initializedbase44-sdk
State Check Logic: Before selecting a skill, check:
- IF (user mentions "create/build app" OR "make a project"):
- IF (directory is empty OR no
exists): → Use base44-cli (project initialization needed)base44/config.jsonc - ELSE: → Use base44-sdk (project exists, build features)
- IF (directory is empty OR no
Project Structure
A Base44 project combines a standard frontend project with a
base44/ configuration folder:
my-app/ ├── base44/ # Base44 configuration (created by CLI) │ ├── config.jsonc # Project settings, site config │ ├── entities/ # Entity schema definitions │ │ ├── task.jsonc │ │ └── board.jsonc │ └── functions/ # Backend functions (optional) │ └── my-function/ │ ├── function.jsonc │ └── index.ts ├── src/ # Frontend source code │ ├── api/ │ │ └── base44Client.js # Base44 SDK client │ ├── pages/ │ ├── components/ │ └── main.jsx ├── index.html # SPA entry point ├── package.json └── vite.config.js # Or your framework's config
Key files:
- Project name, description, site build settingsbase44/config.jsonc
- Data model schemas (see Entity Schema section)base44/entities/*.jsonc
- Pre-configured SDK client for frontend usesrc/api/base44Client.js
config.jsonc example:
{ "name": "My App", "description": "App description", "entitiesDir": "./entities", "functionsDir": "./functions", "site": { "installCommand": "npm install", "buildCommand": "npm run build", "serveCommand": "npm run dev", "outputDirectory": "./dist" } }
Installation
Install the Base44 CLI as a dev dependency in your project:
npm install --save-dev base44
Important: Never assume or hardcode the
base44 package version. Always install without a version specifier to get the latest version.
Then run commands using
npx:
npx base44 <command>
Note: All commands in this documentation use
npx base44. You can also use yarn base44, or pnpm base44 if preferred.
Available Commands
Authentication
| Command | Description | Reference |
|---|---|---|
| Authenticate with Base44 using device code flow | auth-login.md |
| Logout from current device | auth-logout.md |
| Display current authenticated user | auth-whoami.md |
Project Management
| Command | Description | Reference |
|---|---|---|
| Create a new Base44 project from a template | create.md ⚠️ MUST READ |
| Link an existing local project to Base44 | link.md |
| Open the app dashboard in your browser | dashboard.md |
Deployment
| Command | Description | Reference |
|---|---|---|
| Deploy all resources (entities, functions, site) | deploy.md |
Entity Management
| Action / Command | Description | Reference |
|---|---|---|
| Create Entities | Define entities in folder | entities-create.md |
| Push local entities to Base44 | entities-push.md |
Entity Schema (Quick Reference)
ALWAYS follow this exact structure when creating entity files:
File naming:
base44/entities/{kebab-case-name}.jsonc (e.g., team-member.jsonc for TeamMember)
Schema template:
{ "name": "EntityName", "type": "object", "properties": { "field_name": { "type": "string", "description": "Field description" } }, "required": ["field_name"] }
Field types:
string, number, boolean, array
String formats: date, date-time, email, uri, richtext
For enums: Add "enum": ["value1", "value2"] and optionally "default": "value1"
For complete documentation, see entities-create.md.
Function Management
| Action / Command | Description | Reference |
|---|---|---|
| Create Functions | Define functions in folder | functions-create.md |
| Deploy local functions to Base44 | functions-deploy.md |
Site Deployment
| Command | Description | Reference |
|---|---|---|
| Deploy built site files to Base44 hosting | site-deploy.md |
SPA only: Base44 hosting supports Single Page Applications with a single
index.html entry point. All routes are served from index.html (client-side routing).
Quick Start
-
Install the CLI in your project:
npm install --save-dev base44 -
Authenticate with Base44:
npx base44 login -
Create a new project (ALWAYS provide name and
flag):--pathnpx base44 create my-app -p . -
Build and deploy everything:
npm run build npx base44 deploy -y
Or deploy individual resources:
- Push entities onlynpx base44 entities push
- Deploy functions onlynpx base44 functions deploy
- Deploy site onlynpx base44 site deploy -y
Common Workflows
Creating a New Project
⚠️ MANDATORY: Before running
, you MUST read create.md for:base44 create
- Template selection - Choose the correct template (
vsbackend-and-client
)backend-only - Correct workflow - Different templates require different setup steps
- Common pitfalls - Avoid folder creation errors that cause failures
Failure to follow the create.md instructions will result in broken project scaffolding.
Linking an Existing Project
# If you have base44/config.jsonc but no .app.jsonc npx base44 link --create --name my-app
Deploying All Changes
# Build your project first npm run build # Deploy everything (entities, functions, and site) npx base44 deploy -y
Deploying Individual Resources
# Push only entities npx base44 entities push # Deploy only functions npx base44 functions deploy # Deploy only site npx base44 site deploy -y
Opening the Dashboard
# Open app dashboard in browser npx base44 dashboard
Recommended package.json Scripts
Add these scripts to your
package.json for easier CLI usage:
{ "scripts": { "base44:login": "base44 login", "base44:push": "base44 entities push", "base44:functions": "base44 functions deploy", "base44:site": "base44 site deploy -y", "base44:deploy": "base44 deploy -y", "deploy": "npm run build && npm run base44:deploy" } }
Then use them like:
npm run base44:login npm run base44:push npm run deploy # Builds and deploys everything in one command
Authentication
Most commands require authentication. If you're not logged in, the CLI will automatically prompt you to login. Your session is stored locally and persists across CLI sessions.
Troubleshooting
| Error | Solution |
|---|---|
| Not authenticated | Run first |
| No entities found | Ensure entities exist in directory |
| Entity not recognized | Ensure file uses kebab-case naming (e.g., not ) |
| No functions found | Ensure functions exist in with valid configs |
| No site configuration found | Check that is configured in project config |
| Site deployment fails | Ensure you ran first and the build succeeded |