# Blueprints import { Aside } from "@astrojs/starlight/components" A **blueprint** is a complete Ren setup packaged as one installable unit. It captures [agents](/docs/deep-dives/concepts/agents/agents/), [skills](/docs/deep-dives/concepts/agents/skills/), MCPs, projects, triggers, and the wiring between them: everything someone needs to reproduce a working setup in their own organization. Instead of recreating an agent, attaching its skills and MCPs, and configuring projects by hand, you install a blueprint and let it do the wiring. ## What a blueprint contains A blueprint declares the resources that should exist and how they connect: - **Projects**: name, permissions, bound agents, and cron triggers. - **Agents**: at a specific version, with their prompt, model, skills, MCPs, and permissions. - **Skills** and **MCPs**: the capabilities the agents use. - **Replays**: recorded sessions that show how the setup is used. ## How installation works When you install a blueprint, Ren handles each resource one of three ways: - **Link**: the resource is already in your organization or published on the [registry](/docs/deep-dives/concepts/sharing/registry/), so Ren references it directly without copying. - **Fork**: the resource isn't reachable from your org, so Ren copies it into your organization. The copy is independent: changes to the original don't affect it. - **Skip**: the resource can't be linked or forked (for example, it was archived). Skips are reported so you can decide how to handle them. Installation is all-or-nothing: if any copy fails, the whole install rolls back. You never end up with a half-installed blueprint. ## Publishing Before others can install a blueprint, you publish it. Publishing also publishes every resource it references (agents, skills, MCPs, and replays), so the blueprint is never missing a dependency. Publishing again is a no-op. ## Visibility Blueprints follow the same [scopes](/docs/deep-dives/concepts/sharing/scopes/) as other resources: **private**, **org**, or **public** (registry). The scope of each resource inside a blueprint decides whether installers link it (public/shared) or fork it (private/cross-org). ## Discovering and installing You browse published blueprints in the [registry](/docs/deep-dives/concepts/sharing/registry/) and install one by slug or ID. The install process links what it can, forks what it must, and reports anything it skipped.