@dboio/cli 0.11.4 → 0.15.0

package/README.md

@@ -181,13 +181,26 @@ All configuration is **directory-scoped**. Each project folder maintains its own
 | `metadata_templates.json` | Column templates per entity/descriptor (auto-generated by `dbo clone`) | Committable (shared) |
 | `synchronize.json` | Pending deletions and sync state (updated by `dbo rm` and `dbo push`) | Committable (shared) |
 | `.app_baseline.json` | Server-state snapshot for delta detection — stores column values at last clone/push so `dbo push` can detect which columns changed locally. Read-only (chmod 444); auto-migrated from legacy root `.app.json`. | Committable (shared) |
+| `scripts.json` | Build/push lifecycle hooks (see [Script Hooks](#script-hooks)) | Committable (shared) |
+| `scripts.local.json` | Per-user hook overrides | Gitignored (per-user) |
 
-`dbo init` automatically adds `.dbo/credentials.json`, `.dbo/cookies.txt`, `.dbo/config.local.json`, and `.dbo/ticketing.local.json` to `.gitignore` (creates the file if it doesn't exist).
+`dbo init` automatically adds `.dbo/credentials.json`, `.dbo/cookies.txt`, `.dbo/config.local.json`, `.dbo/ticketing.local.json`, and `.dbo/scripts.local.json` to `.gitignore` (creates the file if it doesn't exist).
 
 > **Upgrading from pre-0.9.9**: The baseline file `.app.json` in the project root has moved to `.dbo/.app_baseline.json`. Running any `dbo` command will auto-migrate the file. You can also manually remove the `.app.json` entry from your `.gitignore`.
 
 > **Upgrading from pre-0.11.0**: `TransactionKeyPreset` now applies only to records that carry a `UID` column (core assets). Data records without a UID are always submitted with `RowID` regardless of the preset. Migration 001 runs automatically on first command after upgrade and logs a one-time notice.
 
+> **Upgrading to 0.13.3+**: Entity and extension companion files no longer include `~UID` in the filename. Migration 007 automatically renames legacy `name~uid.Column.ext` files to `name.Column.ext` and updates `@references` in metadata.
+
+> **Upgrading to 0.14.0+**: Metadata files now use `name.metadata~uid.json` instead of `name~uid.metadata.json`. The UID has moved from the base name into the `.metadata~uid` suffix. Migration 008 automatically renames all metadata files. Output child companions use index-based naming (`Sales.column.CustomSQL.sql`, `Sales.column-1.CustomSQL.sql`) instead of UID-based naming.
+>
+> | Record type | Example metadata file |
+> |---|---|
+> | Content | `colors.metadata~abc123.json` |
+> | Media | `logo.png.metadata~def456.json` |
+> | Output | `Sales.metadata~ghi789.json` |
+> | Extension | `MyExtension.metadata~jkl012.json` |
+
 #### Automatic migrations
 
 When the CLI version is upgraded, one-time migration scripts in `tools/cli/src/migrations/` run automatically on the first command invocation in a project directory. Completed migration IDs are recorded in `.dbo/config.local.json` under `_completedMigrations` (per-user, gitignored) so each developer runs them independently and they never re-fire.
@@ -411,6 +424,7 @@ The project's reference domain is stored in `app.json._domain` (committed to git
 8. **Processes entity-dir records** — entities matching project directories (`extension`, `app_version`, `data_source`, `site`, `group`, `integration`, `automation`) are saved as `.metadata.json` files in their corresponding directory (e.g., `extension/`, `data_source/`)
 9. **Processes other entities** — remaining entities with a `BinID` are placed in the corresponding bin directory
 10. **Saves `app.json`** — clone of the original JSON with processed entries replaced by `@path/to/*.metadata.json` references
+11. **Orphan cleanup** — any local `.metadata.json` files whose UID is absent from the server response are automatically moved to `trash/` along with their companion content and media files. This prevents stale records (deleted server-side) from causing false positives in `dbo push`. Skipped during `--entity-filter` clones
 
 #### Clone source tracking
 
@@ -495,6 +509,8 @@ For each entity type, the CLI prompts to choose which column becomes the filenam
 
 If any columns contain base64-encoded content, the CLI prompts to extract them as companion files. Extracted columns produce files named `<name>.<Column>.<ext>` alongside the metadata, with `@reference` entries in the metadata and a `_contentColumns` array.
 
+**Companion file naming convention:** Only `.metadata.json` files carry the `~UID` suffix (e.g. `Add-Asst-Execute-Security~wxl6ivcwfkix3zgantszjg.metadata.json`). Companion content files use the natural base name without `~UID` (e.g. `Add-Asst-Execute-Security.String16.js`). If two records share the same name within a directory, the second gets a `-1` suffix (e.g. `Add-Asst-Execute-Security-1.String16.js` with metadata `Add-Asst-Execute-Security-1~otheruid.metadata.json`). Migration 007 automatically renames legacy `~UID` companion files to the natural convention.
+
 Use `-y` to skip prompts (uses `Name` column, no content extraction).
 
 #### Extension descriptor sub-directories
@@ -1237,7 +1253,10 @@ The push command finds `assets/js/main.metadata.json`, reads the UID and entity,
 #### Directory (recursive)
 
 ```bash
-# Push all records in a directory
+# Push all changed records in the current directory
+dbo push
+
+# Push all records in a specific directory
 dbo push assets/
 
 # Push with auto-accept for all prompts
@@ -1280,7 +1299,7 @@ The `@colors.css` reference tells push to read the content from that file. All o
 
 | Flag | Description |
 |------|-------------|
-| `<path>` | File or directory to push |
+| `[path]` | File or directory to push (default: current directory) |
 | `-C, --confirm <true\|false>` | Commit (default: `true`) |
 | `--ticket <id>` | Override ticket ID |
 | `--modify-key <key>` | Provide ModifyKey directly (skips interactive prompt) |
@@ -1289,6 +1308,8 @@ The `@colors.css` reference tells push to read the content from that file. All o
 | `--content-only` | Only push file content, skip metadata |
 | `-y, --yes` | Auto-accept all prompts |
 | `--toe-stepping <true\|false>` | Check server for conflicts before pushing (default: `true`). Set to `false` to skip the check and push unconditionally |
+| `--no-scripts` | Bypass all script hooks; run default push pipeline |
+| `--no-build` | Skip the build phase; run push phase only |
 | `--json` | Output raw JSON |
 | `--jq <expr>` | Filter JSON response |
 
@@ -1300,6 +1321,31 @@ You can then choose to overwrite the server changes or cancel and pull first. Us
 
 ---
 
+### `dbo tag`
+
+Apply macOS Finder color tags or Linux gio emblems to companion files based on their sync status relative to the server. Tags are automatically refreshed after `dbo clone` and `dbo push`.
+
+| Tag | Color | Meaning |
+|-----|-------|---------|
+| `dbo:Synced` | 🟢 Green | File matches server — no local changes |
+| `dbo:Modified` | 🔵 Blue | Local edits not yet pushed |
+| `dbo:Untracked` | 🟡 Yellow | No metadata — not yet added with `dbo add` |
+| `dbo:Trashed` | 🔴 Red | File is in the `trash/` directory |
+
+```bash
+dbo tag                  # Refresh tags for all project files
+dbo tag --clear          # Remove all dbo:* tags (preserves other Finder tags)
+dbo tag --status         # Show counts per category
+dbo tag --verbose        # Log each file and its status
+dbo tag path/to/dir      # Tag a specific file or directory subtree
+dbo tag --enable         # Enable automatic tagging after clone/push (default)
+dbo tag --disable        # Disable automatic tagging
+```
+
+Tagging is silently skipped on Windows and unsupported platforms. Only macOS (Finder color tags via `xattr`) and Linux (gio emblems) are supported. The `--clear` flag only removes `dbo:*` prefixed tags, preserving any user-applied Finder tags.
+
+---
+
 ### `dbo rm`
 
 Remove a file or directory locally and stage server deletions for the next `dbo push`. Similar to `git rm`.
@@ -1765,6 +1811,25 @@ Create a `.dbo/deploy_config.json` file to define named deployments:
 
 This replaces the curl commands typically embedded in `package.json` scripts.
 
+#### Automatic deploy config generation
+
+When you run `dbo clone` or `dbo add`, each companion file (CSS, JS, HTML, SQL, etc.) is automatically registered in `.dbo/deploy_config.json` under an `<extension>:<name>` key — no manual authoring needed:
+
+```bash
+dbo clone   # → .dbo/deploy_config.json auto-populated with one entry per companion file
+```
+
+Keys are derived as `<extension>:<basename>` from the companion file path. If two files share the same key, a parent directory segment is appended to disambiguate (`css:colors` and `css:admin/colors`). Entries include `entity` and `column` from the record metadata.
+
+Once generated, you can deploy by name or by UID:
+
+```bash
+dbo deploy css:colors                   # deploy by key name
+dbo deploy cdlftyk2lkg21whojzqqoa       # deploy by UID (scans manifest values)
+```
+
+Entries are updated automatically on re-clone (path changes are reflected in place) and removed when you run `dbo rm`. When you `dbo mv` a file, the old entry is removed and a new entry is inserted with the correct key for the new path.
+
 #### Non-interactive mode (npm scripts)
 
 When running `dbo deploy` (or any submission command) inside npm scripts or piped commands where stdin is not a TTY, the CLI automatically skips all interactive prompts and uses stored credentials:
@@ -1794,6 +1859,121 @@ To set up for non-interactive use:
 
 ---
 
+## Script Hooks
+
+Script hooks let you define build and push lifecycle commands in `.dbo/scripts.json`. Hooks run automatically during `dbo push` and can also be triggered independently with `dbo build` and `dbo run`.
+
+### Configuration Files
+
+| File | Tracked | Purpose |
+|------|---------|---------|
+| `.dbo/scripts.json` | Yes | Shared hook definitions (committed to git) |
+| `.dbo/scripts.local.json` | No | Per-user overrides (gitignored) |
+
+### Top-level Keys
+
+| Key | Description |
+|-----|-------------|
+| `scripts` | Global hooks and named scripts (apply to all targets) |
+| `targets` | Per-file or per-directory hooks (highest priority) |
+| `entities` | Per-entity-type hooks (e.g., `content`, `extension.control`) |
+
+### Example `.dbo/scripts.json`
+
+```json
+{
+  "scripts": {
+    "prepush": "echo pushing $DBO_TARGET"
+  },
+  "targets": {
+    "lib/bins/app/assets/js/operator.js": {
+      "build": "rollup -c src/rollup_config.mjs",
+      "push": false
+    }
+  },
+  "entities": {
+    "extension.control": {
+      "prebuild": "npm run compile-controls"
+    }
+  }
+}
+```
+
+### Lifecycle Hooks
+
+| Hook | Phase | Description |
+|------|-------|-------------|
+| `prebuild` | Build | Runs before build |
+| `build` | Build | Main build step |
+| `postbuild` | Build | Runs after build |
+| `prepush` | Push | Runs before push |
+| `push` | Push | Custom push (replaces default HTTP submit) |
+| `postpush` | Push | Runs after push |
+
+### Resolution Order
+
+Hooks resolve per-hook from lowest to highest priority:
+
+1. **Global** (`scripts`) — applies to all targets
+2. **Entity** (`entities`) — applies to targets matching the entity type
+3. **Target** (`targets`) — applies to a specific file or directory
+
+A target can override `build` while the global `prepush` still applies.
+
+### Hook Value Types
+
+| Value | Behavior |
+|-------|----------|
+| `"command"` | Run as shell command |
+| `["cmd1", "cmd2"]` | Run sequentially; fail-fast on first non-zero exit |
+| `false` | Skip (for `push`: skip HTTP submit) |
+| `true` / omitted | Use default behavior |
+
+### Environment Variables
+
+These env vars are injected into all hook processes:
+
+| Variable | Description |
+|----------|-------------|
+| `DBO_TARGET` | Relative file path being processed |
+| `DBO_ENTITY` | Entity type (e.g., `content`, `extension`) |
+| `DBO_DOMAIN` | Configured domain |
+| `DBO_APP` | App short name |
+| `DBO_APP_UID` | App UID |
+
+### Push Flags
+
+| Flag | Description |
+|------|-------------|
+| `--no-scripts` | Bypass all script hooks; run default push pipeline |
+| `--no-build` | Skip build phase; run push phase only |
+
+### `dbo build [path]`
+
+Runs the build lifecycle (`prebuild` → `build` → `postbuild`) without pushing.
+
+```bash
+# Build a specific target
+dbo build lib/bins/app/assets/js/operator.js
+
+# Build all targets with a build hook
+dbo build
+```
+
+### `dbo run [script-name]`
+
+Runs a named global script from `.dbo/scripts.json` (like `npm run`). Automatically runs `pre<name>` and `post<name>` scripts if defined.
+
+```bash
+# List all available scripts
+dbo run
+
+# Run a specific script
+dbo run prepush
+```
+
+---
+
 ## Global Flags
 
 These flags are available on most commands:

package/bin/dbo.js

@@ -31,6 +31,9 @@ import { diffCommand } from '../src/commands/diff.js';
 import { rmCommand } from '../src/commands/rm.js';
 import { mvCommand } from '../src/commands/mv.js';
 import { syncCommand } from '../src/commands/sync.js';
+import { buildCommand } from '../src/commands/build.js';
+import { runCommand } from '../src/commands/run.js';
+import { tagCommand } from '../src/commands/tag.js';
 
 // First-run welcome message
 function checkFirstRun() {
@@ -91,6 +94,9 @@ program.addCommand(diffCommand);
 program.addCommand(rmCommand);
 program.addCommand(mvCommand);
 program.addCommand(syncCommand);
+program.addCommand(buildCommand);
+program.addCommand(runCommand);
+program.addCommand(tagCommand);
 
 // Show welcome message on first run
 checkFirstRun();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dboio/cli",
-  "version": "0.11.4",
+  "version": "0.15.0",
   "description": "CLI for the DBO.io framework",
   "type": "module",
   "bin": {

package/plugins/claude/dbo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "dbo",
-  "version": "0.6.8",
+  "version": "0.8.0",
   "description": "DBO.io CLI integration for Claude Code",
   "author": {
     "name": "DBO.io"

package/plugins/claude/dbo/commands/dbo.md

@@ -1,274 +1,97 @@
-# DBO CLI Command
-
-The dbo CLI interacts with DBO.io — a database-driven application framework.
-
-**STEP 1: Check if `$ARGUMENTS` is empty or blank.**
-
-If `$ARGUMENTS` is empty — meaning the user typed just `/dbo` with nothing after it — then you MUST NOT run any bash command. Do NOT run `dbo`, `dbo --help`, or anything else. Instead, respond ONLY with this text message:
-
 ---
-
-Hi there! I can help you with running dbo commands. What would you like to do?
-
-Here are the available commands:
-
-| Command   | Description                                      |
-|-----------|--------------------------------------------------|
-| init      | Initialize .dbo/ configuration                   |
-| login     | Authenticate with a DBO.io instance              |
-| logout    | Clear session                                    |
-| status    | Show config, domain, and session info            |
-| input     | Submit CRUD operations (add/edit/delete records)  |
-| output    | Query data from outputs or entities              |
-| content   | Get or deploy content                            |
-| media     | Get media files                                  |
-| upload    | Upload a file                                    |
-| message   | Send messages (email, SMS, chatbot)              |
-| pull      | Pull records to local files                      |
-| push      | Push local files back to DBO.io                  |
-| add       | Add a new file to DBO.io                         |
-| clone     | Clone an app to local project structure           |
-| diff      | Compare local files with server versions          |
-| rm        | Remove a file and stage server deletion           |
-| deploy    | Deploy via manifest                              |
-| cache     | Manage cache                                     |
-| install   | Install or upgrade CLI, plugins, Claude commands (shorthand: `i`) |
-
-Just tell me what you'd like to do and I'll help you build the right command!
-
+name: cli
+description: Run DBO.io CLI commands for local file sync, project management, and deployment (push/pull/clone/add/rm/diff/build/deploy). NOT for direct API operations — use docs/ for that.
+allowed-tools: Read, Write, Glob, Bash(git status:*), Bash(git branch:*), Bash(git diff:*), Bash(ls:*), Bash(dbo init:*), Bash(dbo login:*), Bash(dbo status:*), Bash(dbo deploy:*), Bash(dbo add:*), Bash(dbo clone:*), Bash(dbo push:*), Bash(dbo pull:*), Bash(dbo diff:*), Bash(dbo rm:*), Bash(dbo mv:*), Bash(dbo run:*), Bash(dbo install:*), Bash(git stash:*), Bash(grep:*), Bash(which dbo:*)
+user-invokable: true
 ---
 
-Then STOP. Wait for the user to respond. Guide them step by step — asking about entities, UIDs, file paths, flags, etc. to construct the correct `dbo` command. Run `dbo status` proactively to check if the CLI is initialized and authenticated before suggesting data commands.
-
-**STEP 2: If `$ARGUMENTS` is NOT empty, run the command:**
-
-```bash
-dbo $ARGUMENTS
-```
-
-## Command Reference
+# DBO CLI Skill
 
-Available subcommands:
-- `init` — Initialize .dbo/ configuration for the current directory
-- `login` — Authenticate with a DBO.io instance
-- `logout` — Clear session
-- `status` — Show config, domain, and session info
-- `input -d '<expr>'` — CRUD operations (add/edit/delete records)
-- `output -e <entity>` — Query data from entities
-- `output <uid>` — Query custom outputs
-- `content <uid>` — Get content, `content deploy <uid> <file>` to deploy
-- `pull [uid]` — Pull records to local files (default: content entity)
-- `pull -e <entity> [uid]` — Pull from any entity
-- `push <path>` — Push local files back to DBO using metadata
-- `add <path>` — Add a new file to DBO (creates record on server)
-- `media <uid>` — Get media files
-- `upload <file>` — Upload binary files
-- `message <uid>` — Send messages (email, SMS, chatbot)
-- `cache list|refresh` — Manage cache
-- `clone [source]` — Clone an app to local project (from file or server)
-- `clone --app <name>` — Clone by app short name from server
-- `diff [path]` — Compare local files against server and selectively merge changes
-- `diff -y` — Accept all server changes without prompting
-- `diff --no-interactive` — Show diffs without prompting to accept
-- `rm <file>` — Remove a file locally and stage server deletion for next push
-- `rm <directory>` — Remove a directory, all files, and sub-directories recursively
-- `rm -f <path>` — Remove without confirmation prompts
-- `rm --keep-local <path>` — Stage server deletions without deleting local files/directories
-- `deploy [name]` — Deploy via .dbo/deploy_config.json manifest
-- `install` (alias: `i`) — Install or upgrade CLI, plugins, or Claude commands
-- `i dbo` or `i dbo@latest` — Install/upgrade the CLI from npm
-- `i dbo@0.4.1` — Install a specific CLI version
-- `install /path/to/src` — Install CLI from local source
-- `install plugins` — Install/upgrade Claude command plugins
-- `install plugins --global` — Install plugins to `~/.claude/commands/` (shared across projects)
-- `install plugins --local` — Install plugins to `.claude/commands/` (project only)
-- `install claudecommands` — Install/upgrade Claude Code commands
-- `install claudecode` — Install Claude Code CLI + commands
-- `install --claudecommand dbo --global` — Install a specific command globally
+Run `dbo` CLI commands for local file sync, project management, and deployment.
 
-## Change Detection (pull, clone, diff)
+## When to use this skill
 
-When pulling or cloning records that already exist locally, the CLI compares file modification times against the server's `_LastUpdated` timestamp. If the server has newer data, you'll be prompted with options:
+Use this skill when the user wants to:
+- Run a local workflow command (push, pull, clone, add, rm, diff, build, deploy)
+- Set up a project (`dbo init`, `dbo login`, `dbo clone`)
+- Deploy files to the server (`dbo push`, `dbo deploy`)
 
-1. **Overwrite** — Replace local files with server version
-2. **Compare** — Show a line-by-line diff and selectively merge
-3. **Skip** — Keep local files unchanged
-4. **Overwrite all** — Accept all remaining server changes
-5. **Skip all** — Skip all remaining files
+## When NOT to use this skill
 
-Use `dbo diff [path]` to compare without pulling. Use `-y` to auto-accept all changes.
+Do NOT use this skill for direct API operations. The following CLI commands are thin wrappers around REST endpoints — use the `docs/` reference instead for the canonical API syntax:
+- `dbo input` wraps `POST /api/input/submit` — use `docs/dbo-cheat-sheet.md`
+- `dbo output` wraps `GET /api/output/` — use `docs/dbo-output-query.md`
+- `dbo content` wraps `GET /api/content/` — use `docs/dbo-cheat-sheet.md`
+- `dbo media` wraps `GET /api/media/` — use `docs/dbo-cheat-sheet.md`
+- `dbo upload` wraps `POST /api/upload/submit` — use `docs/dbo-cheat-sheet.md`
+- `dbo message` wraps `GET /api/message/` — use `docs/dbo-cheat-sheet.md`
+- `dbo cache` wraps `/api/cache/` — use `docs/dbo-cheat-sheet.md`
 
-## Smart Command Building
+Also do NOT use this skill for:
+- **Entity schemas / column names** — use `docs/dbo-core-entities.md`
+- **Token/tag syntax** (`#{...}`, `<#_embed>`, etc.) — use `docs/dbo-cheat-sheet.md`
+- **Building server-side templates or content records** — use `docs/`
 
-When helping the user build a command interactively:
+All doc files are bundled in the `docs/` subdirectory of this plugin (copied during npm publish). When working in the repo, the API docs are at the repo root `docs/` and the CLI README is at `tools/cli/README.md`.
 
-1. **Check readiness first**: Run `dbo status` to see if initialized and authenticated. If not, guide them through `dbo init` and `dbo login` first.
-2. **Understand intent**: Ask what they want to do (query data, deploy a file, add a record, etc.)
-3. **Gather parameters**: Ask for the specific values needed (entity name, UID, file path, filters, etc.)
-4. **Build the command**: Construct the full `dbo` command with proper flags and syntax
-5. **Execute**: Run it and explain the results
+For detailed CLI command flags, options, and behavior — read `docs/dbo-cli-readme.md`.
 
-### Common workflows to suggest:
+## Running commands
 
-- **"I want to query data"** → Guide toward `dbo output -e <entity>` with filters
-- **"I want to deploy/update a file"** → Check if `.metadata.json` exists → `dbo push` or `dbo content deploy`
-- **"I want to add a new file"** → `dbo add <path>` (will create metadata interactively)
-- **"I want to pull files from the server"** → `dbo pull` or `dbo pull -e <entity>`
-- **"I want to delete/remove a file"** → `dbo rm <file>` (stages deletion for next `dbo push`)
-- **"I want to delete a directory"** → `dbo rm <directory>` (removes all files + sub-dirs, stages bin deletions)
-- **"I want to see what's on the server"** → `dbo output -e <entity> --format json`
-- **"I need to set up this project"** → `dbo init` → `dbo login` → `dbo status`
-- **"I want to clone an app"** → `dbo clone --app <name>` or `dbo clone <local.json>`
-- **"I want to set up and clone"** → `dbo init --domain <host> --app <name> --clone`
+**If `$ARGUMENTS` is empty**, show the command table and guide interactively.
 
-## Add Command Details
-
-`dbo add <path>` registers a new local file with the DBO server by creating an insert record.
+**If `$ARGUMENTS` is provided**, check if command exists in the command table in the available commands (use best guess, eg: initialize => init), then on match run the command:**:
 
 ```bash
-# Add a single file (interactive metadata wizard if no .metadata.json exists)
-dbo add assets/css/colors.css
-
-# Add with auto-accept and ticket
-dbo add assets/css/colors.css -y --ticket abc123
-
-# Scan current directory for all un-added files
-dbo add .
-
-# Scan a specific directory
-dbo add assets/
-```
-
-Flags: `-C/--confirm <true|false>`, `--ticket <id>`, `-y/--yes`, `--json`, `--jq <expr>`, `-v/--verbose`, `--domain <host>`
-
-### How add works
-
-1. Checks for a companion `<basename>.metadata.json` next to the file
-2. If metadata exists with `_CreatedOn` → already on server, skips (use `push` instead)
-3. If metadata exists without `_CreatedOn` → uses it to insert the record
-4. If no metadata → interactive wizard prompts for: entity, content column, AppID, BinID, SiteID, Path
-5. Creates `.metadata.json`, submits insert to `/api/input/submit`
-6. Writes returned UID back to metadata file
-7. Suggests running `dbo pull -e <entity> <uid>` to populate all server columns
-
-### Non-interactive add (for scripting)
-
-To add without prompts, create the `.metadata.json` first, then run `dbo add <file> -y`:
-
-```json
-{
-  "Name": "colors",
-  "Path": "assets/css/colors.css",
-  "Content": "@colors.css",
-  "_entity": "content",
-  "_contentColumns": ["Content"]
-}
+dbo $ARGUMENTS
 ```
 
-Optional fields like `AppID`, `BinID`, `SiteID` are only included if the user provides values — they have no defaults and are omitted when left blank.
-
-The `@colors.css` value means "read content from colors.css in the same directory".
-
-### Directory scan (`dbo add .`)
+## Command overview
 
-Finds files that have no `.metadata.json` or whose metadata lacks `_CreatedOn`. Skips `.dbo/`, `.git/`, `node_modules/`, dotfiles, and `.metadata.json` files. When adding multiple files, defaults from the first file are reused.
+These are the local workflow commands this skill covers:
 
-## Push Command Details
+| Command | Description |
+|---------|-------------|
+| `init` | Initialize .dbo/ configuration |
+| `login` / `logout` | Authenticate / clear session |
+| `status` | Show config, domain, session info |
+| `clone` | Clone an app to local project |
+| `pull` | Pull records to local files |
+| `push` | Push local changes (default: current dir) |
+| `add` | Add a new file to DBO.io |
+| `diff` | Compare local vs server |
+| `rm` | Remove file, stage server deletion |
+| `deploy` | Deploy via .dbo/deploy_config.json manifest |
+| `build` | Run build hooks (.dbo/scripts.json) |
+| `run` | Run named script (.dbo/scripts.json) |
+| `install` | Install/upgrade CLI, plugins (alias: `i`) |
 
-`dbo push <path>` pushes local file changes back to existing DBO records using their `.metadata.json`.
+## Common workflows
 
 ```bash
-dbo push assets/css/colors.css          # single file
-dbo push assets/                         # all records in directory
-dbo push assets/ --content-only          # only file content, skip metadata
-dbo push assets/ --meta-only             # only metadata columns, skip files
-dbo push assets/ -y --ticket abc123      # auto-accept + ticket
-```
-
-Flags: `-C/--confirm`, `--ticket <id>`, `--meta-only`, `--content-only`, `-y/--yes`, `--json`, `--jq`, `-v/--verbose`, `--domain`
-
-## Column Filtering (add & push)
+# Setup
+dbo init --domain my-domain.com --app myapp --clone
+dbo login
 
-These columns are **never submitted** in add or push payloads:
-- `_CreatedOn`, `_LastUpdated` — server-managed timestamps
-- `_LastUpdatedUserID`, `_LastUpdatedTicketID` — session-provided values
-- `UID` — server-assigned on insert; used as identifier on push (not as column value)
-- `_id`, `_entity`, `_contentColumns`, `_mediaFile` — internal/metadata fields
+# Edit and push
+dbo push                          # push all changes in current dir
+dbo push lib/bins/app/assets/     # push specific directory
+dbo push colors.css               # push single file
 
-## Pull → Edit → Push/Add Workflow
+# Build and push (with script hooks)
+dbo build                         # run build hooks only
+dbo push                          # build + push (hooks run automatically)
+dbo push --no-build               # push without build phase
+dbo push --no-scripts             # push without any hooks
 
-```bash
-# Pull existing records
+# Pull
 dbo pull -e content --filter 'AppID=10100'
 
-# Edit files locally, then push changes back
-dbo push assets/css/colors.css
-
-# Or add a brand new file
+# Add new files
 dbo add assets/css/newstyle.css
-```
-
-## Clone Command Details
+dbo add .                         # scan for un-added files
 
-`dbo clone` scaffolds a local project from a DBO.io app export JSON, creating directories, files, metadata, and config.
-
-```bash
-# Clone from a local JSON export file
-dbo clone /path/to/app_export.json
-
-# Clone from server by app short name (requires login)
-dbo clone --app myapp
-
-# Clone using AppShortName already in config
-dbo clone
-
-# Init + clone in one step
-dbo init --domain my-domain.com --app myapp --clone
+# Compare and merge
+dbo diff                          # compare all local vs server
+dbo diff -y                       # auto-accept all server changes
 ```
-
-Flags: `--app <name>`, `--domain <host>`, `-y/--yes`, `-v/--verbose`
-
-### What clone does
-
-1. Loads app JSON (local file, server API, or prompt)
-2. Updates `.dbo/config.json` with `AppID`, `AppUID`, `AppName`, `AppShortName`
-3. Updates `package.json` with `name`, `productName`, `description`, `homepage`, and `deploy` script
-4. Creates directory structure from `children.bin` hierarchy → saves `.dbo/structure.json`
-5. Writes content files (decodes base64) with `*.metadata.json` into bin directories
-6. Downloads media files from server using fallback chain: FullPath (`/media/{app}/{path}`) → `/dir/` route → `/api/media/{uid}`, with `*.metadata.json`. Errors logged to `.dbo/errors.log`
-7. Processes entity-dir records (`extension`, `app_version`, `data_source`, `site`, `group`, `integration`, `automation`) into `lib/` project directories as `.metadata.json` files with optional companion content files
-8. Processes remaining entities with BinID into corresponding bin directories
-9. Saves `app.json` to project root with `@path/to/*.metadata.json` references
-
-### Placement preferences
-
-When a record has both `Path`/`FullPath` and `BinID`, clone prompts the user to choose placement. Preferences are saved to `.dbo/config.json` and reused on future clones:
-
-- `ContentPlacement`: `bin` | `path` | `ask` — for content and other entities
-- `MediaPlacement`: `bin` | `fullpath` | `ask` — for media files
-
-Pre-set these in config.json to skip prompts. `.dbo/config.json` and `.dbo/structure.json` are shared via git; `.dbo/credentials.json` and `.dbo/cookies.txt` are gitignored (per-user).
-
-### AppID awareness (add & input)
-
-After cloning, the config has an `AppID`. When running `dbo add` or `dbo input` without an AppID in the data, the CLI prompts:
-1. Yes, use AppID from config
-2. No
-3. Enter custom AppID
-
-### Init flags for clone
-
-`dbo init` now supports `--app <shortName>` and `--clone` flags to combine initialization with app cloning.
-
-## Error Handling
-
-- If the command fails with a session/authentication error, suggest: `dbo login`
-- If it fails with "No domain configured", suggest: `dbo init`
-- If a command is not found, suggest: `dbo --help`
-
-## Output
-
-When showing results:
-- Format JSON output readably
-- For pull/push/add operations, list the files created or modified
-- For query operations, summarize the row count and key fields