{
  "id": "page:docs-blueprints",
  "_kind": "Page",
  "_file": "wiki/docs/blueprints.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/blueprints.md",
    "sourceKind": "repo-docs",
    "title": "Babysitter Blueprints",
    "displayName": "Babysitter Blueprints",
    "slug": "docs/blueprints",
    "articlePath": "wiki/docs/blueprints.md",
    "article": "\n# Babysitter Blueprints\n\nBabysitter 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:*`.\n\nBlueprints 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.\n\n## What the SDK Manages\n\n| Concern | How the SDK handles it |\n| --- | --- |\n| Distribution | Marketplaces are git repositories cloned with `--depth 1`. The SDK reads `marketplace.json` to list available blueprints. |\n| Versioning | The registry tracks installed versions. Migration files describe upgrade steps, and the SDK finds the shortest migration path. |\n| Registry | A JSON registry records what is installed, where it came from, and when. |\n| Instruction delivery | The CLI reads `install.md`, `configure.md`, `uninstall.md`, or migration files from the blueprint package and hands them to the agent. |\n\nEverything else, including project edits, tool installation, CI setup, and follow-up validation, is done by the agent interpreting the blueprint instructions.\n\n## Storage\n\nBlueprint marketplaces are stored under `.a5c/blueprints/marketplaces/` for the selected scope:\n\n- Global scope: `~/.a5c/blueprints/marketplaces/<name>/`\n- Project scope: `<projectDir>/.a5c/blueprints/marketplaces/<name>/`\n\nThe SDK still reads legacy `.a5c/marketplaces/` clones for compatibility. New clones use the blueprint path.\n\n## Quick Start\n\n```bash\n# Add the official marketplace\nbabysitter blueprints:add-marketplace \\\n  --marketplace-url https://github.com/a5c-ai/babysitter \\\n  --marketplace-path blueprints/a5c/marketplace \\\n  --global\n\n# See what is available\nbabysitter blueprints:list --marketplace-name babysitter --global\n\n# Install a blueprint\nbabysitter blueprints:install testing-suite --global\n\n# Reconfigure later\nbabysitter blueprints:configure testing-suite --project\n\n# Remove it\nbabysitter blueprints:uninstall testing-suite --global\n```\n\n## Command Reference\n\nAll commands accept `--json` for machine-readable output and `--global|--project` for scope selection.\n\n| Command | Description |\n| --- | --- |\n| `blueprints:add-marketplace` | Clone a marketplace repository. |\n| `blueprints:update-marketplace` | Pull the latest marketplace changes. |\n| `blueprints:list` | List available blueprints in a marketplace. |\n| `blueprints:install` | Read install instructions for a blueprint. |\n| `blueprints:update` | Resolve migration instructions for an installed blueprint. |\n| `blueprints:configure` | Read configuration instructions for a blueprint. |\n| `blueprints:uninstall` | Read uninstall instructions for a blueprint. |\n| `blueprints:list-installed` | List installed blueprints. |\n| `blueprints:update-registry` | Register or update an installed blueprint entry. |\n| `blueprints:remove-from-registry` | Remove a blueprint registry entry. |\n\nDeprecated `plugin:*` aliases forward to these commands and print a deprecation warning in human-readable mode.\n\n## Package Structure\n\n```text\nmy-blueprint/\n  install.md\n  uninstall.md\n  configure.md\n  blueprint.json\n  migrations/\n    1.0.0_to_1.1.0.md\n  process/\n    main.js\n```\n\n## Agent Plugins Stay Separate\n\nAgent 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.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs",
      "to": "page:docs-blueprints",
      "kind": "contains_page"
    }
  ]
}