iblai-vibe-cli-maintenance

# /iblai-vibe-cli-maintenance Maintainer-facing reference for the `iblai` command-line tool (`iblai-app-cli`). It captures **how the CLI is built**, not how to use it day-to-day — the user-facing behavior of each command lives with the skill that owns the feature: - `iblai add <feature>`, `iblai startapp`, `iblai config`, and the template system → [`/iblai-vibe-scaffold`](../iblai-vibe-scaffold/SKILL.md) - `iblai builds …` (Tauri desktop/mobile) → [`/iblai-vibe-ops-build`](../iblai-vibe-ops-build/SKILL.md) - `iblai deploy …` → [`/iblai-vibe-ops-deploy`](../iblai-vibe-ops-deploy/SKILL.md) > This skill is the authoritative record of how the `iblai` CLI is built — > so it can be rebuilt, forked, or its logic ported. The references below > are the source of truth. ## What's here | Reference | Covers | |---|---| | [`references/iblai-vibe-cli-add-command.md`](references/iblai-vibe-cli-add-command.md) | How `iblai add` detects an existing project and generates feature files (`commands/add.py`) | | [`references/iblai-vibe-cli-startapp.md`](references/iblai-vibe-cli-startapp.md) | How `iblai startapp` scaffolds a new app from the `base`/`agent` templates (`commands/startapp.py`) | | [`references/iblai-vibe-cli-templates.md`](references/iblai-vibe-cli-templates.md) | The Jinja2 template system — directory layout, variables, rendering | | [`references/iblai-vibe-cli-builds.md`](references/iblai-vibe-cli-builds.md) | How the `iblai builds` group wraps `@tauri-apps/cli` with prereq...