page:docs-blueprints
Babysitter Blueprints reference
Babysitter blueprints are version-managed instruction packages distributed through a marketplace. They were previously called Babysitter plugins; the old plugin: CLI commands remain as deprecated aliases for one release, but new documentation and command surfaces should use plugin:.
Babysitter Blueprints
Babysitter blueprints are version-managed instruction packages distributed through a marketplace. They were previously called Babysitter plugins; the old plugin:* CLI commands remain as deprecated aliases for one release, but new documentation and command surfaces should use plugin:*.
Blueprints are not conventional software plugins. A blueprint is a set of markdown instructions or deterministic Babysitter process files that an AI agent reads and executes to install, configure, update, or remove a modular capability.
What the SDK Manages
| Concern | How the SDK handles it |
|---|---|
| Distribution | Marketplaces are git repositories cloned with --depth 1. The SDK reads marketplace.json to list available blueprints. |
| Versioning | The registry tracks installed versions. Migration files describe upgrade steps, and the SDK finds the shortest migration path. |
| Registry | A JSON registry records what is installed, where it came from, and when. |
| Instruction delivery | The CLI reads install.md, configure.md, uninstall.md, or migration files from the blueprint package and hands them to the agent. |
Everything else, including project edits, tool installation, CI setup, and follow-up validation, is done by the agent interpreting the blueprint instructions.
Storage
Blueprint marketplaces are stored under .a5c/blueprints/marketplaces/ for the selected scope:
- Global scope:
~/.a5c/blueprints/marketplaces/<name>/ - Project scope:
<projectDir>/.a5c/blueprints/marketplaces/<name>/
The SDK still reads legacy .a5c/marketplaces/ clones for compatibility. New clones use the blueprint path.
Quick Start
# Add the official marketplace
babysitter blueprints:add-marketplace \
--marketplace-url https://github.com/a5c-ai/babysitter \
--marketplace-path blueprints/a5c/marketplace \
--global
# See what is available
babysitter blueprints:list --marketplace-name babysitter --global
# Install a blueprint
babysitter blueprints:install testing-suite --global
# Reconfigure later
babysitter blueprints:configure testing-suite --project
# Remove it
babysitter blueprints:uninstall testing-suite --globalCommand Reference
All commands accept --json for machine-readable output and --global|--project for scope selection.
| Command | Description |
|---|---|
blueprints:add-marketplace | Clone a marketplace repository. |
blueprints:update-marketplace | Pull the latest marketplace changes. |
blueprints:list | List available blueprints in a marketplace. |
blueprints:install | Read install instructions for a blueprint. |
blueprints:update | Resolve migration instructions for an installed blueprint. |
blueprints:configure | Read configuration instructions for a blueprint. |
blueprints:uninstall | Read uninstall instructions for a blueprint. |
blueprints:list-installed | List installed blueprints. |
blueprints:update-registry | Register or update an installed blueprint entry. |
blueprints:remove-from-registry | Remove a blueprint registry entry. |
Deprecated plugin:* aliases forward to these commands and print a deprecation warning in human-readable mode.
Package Structure
my-blueprint/
install.md
uninstall.md
configure.md
blueprint.json
migrations/
1.0.0_to_1.1.0.md
process/
main.jsAgent Plugins Stay Separate
Agent harness plugins are still called plugins. Do not rename CLAUDE_PLUGIN_ROOT, PI_PLUGIN_ROOT, .claude/plugins/, packages/adapters/hooks/, or packages/extensions-adapter/ when working on blueprints.