Building a strong set of instructions takes time. Once you have them, you should not have to rebuild them every time you start a new site.

A Shared Library lets you make those instructions available across multiple sites, alongside the components, variables, and assets your team already shares.

How it works

Instructions created on a source site can be shared as part of that site's library, along with its other library resources.

The basic flow looks like this:

1. Create and manage your instructions on the source site.
2. Share the site's library with your workspace.
3. Install the library on other sites that can use the same guidance.

Quick demo (no sound) → A library with updates to skills and rules is shared with the workspace.

Quick demo (no sound) → The shared library is installed on a new site, including skills, rules, and other design system resources.

You can use shared instructions alongside instructions created directly on the installed site. The main difference is where you manage them:

• Site-level instructions can be edited directly on that site.
• Library instructions are read-only on sites with the library installed.

For example, your library might include a brand voice rule or design system skill that should apply across several sites. An instruction about the CMS fields or page structure for one specific site should probably stay on that site.

Shared Libraries require a workspace plan with library access. Check Plans & pricing to compare availability by plan.

References in shared instructions

References point directly to a specific resource on your site, such as a component, variable, or asset. When an instruction and the resource it references are included in the same library, that connection stays intact when the library is installed on another site.

For example, your instruction might tell the agent to use a specific color variable for primary buttons. If both are part of the library, the instruction stays connected to that variable on every site with the library installed, instead of relying only on its name or description.

References to site-specific resources, such as pages, locales, or CMS collections that are not part of the library won't stay connected on another site. Keep that in mind when you write instructions you plan to share.

Keep shared instructions up to date

Like your other library resources, instruction updates start on the source site.

Once you publish the library again, sites with the library installed can accept the changes. That gives your team one place to manage the guidance instead of updating the same instruction on every site.

How many libraries you can create and which update features you have access to depends on your plan. See the Libraries Help Center article for details.

When a shared library makes sense

For agencies

Your shared library might hold a client's brand voice, naming conventions, and design system standards. You can install it on every site you manage for that client instead of recreating the same instructions each time.

For larger organizations

Your central brand or design system team might manage instructions that apply across product, marketing, and regional sites. Each team can install the same library, while the shared guidance stays managed from one source.

In both cases, your instructions stay connected instead of being copied into each site and maintained separately.

Other ways to share

Use a shared library when your instructions should stay connected and receive future updates.

For a one-time handoff, you can export:

• All instructions together as a zip file
• One instruction as a markdown file

You can also import a zip file or add individual .md files to another site. This works well for client deliverables, backups, or projects that do not need an ongoing library connection.

Almost there.

Click Complete & continue for a summary of best practices and where to go next.