Builder Code sub-agent for Builder Content

The Builder Code sub-agent for Publish is a built-in AI agent that understands how to work with Builder Content. It removes the need for manual configuration, bespoke engineering scripts, or CMS-specific domain knowledge.

Anyone with access to Builder Code can direct it using plain language, and it handles the technical work.

The sub-agent can do three things:

Install the Builder Content SDK into an existing web app.
Migrate components, tokens, and branding to be compatible with Publish CMS.
Build new components that are registered and configurable within Publish.

When to use Builder Code Preview

Use the Builder Code sub-agent any time the work involves setting up or extending Publish at a code level. For example:

"Set up Publish in my Next.js app."
"Migrate my existing site so it works with Builder code."
"Build a new hero banner component and make it available in Builder Code."
"Register this component with Builder Code and make the headline and CTA configurable."
"Map my existing components to Builder Code content models."

Get started

Before using the Builder Code sub-agent, confirm the following:

Both Builder Code and Builder Content products are active on your Builder account.
Publish is set up and configured. Content models, entries, and the component registry are ready. For more details, visit Get started with Builder Code.
Builder Code is connected to your web app's repository. For more details, visit Get started with Builder Code.

The sub-agent comes pre-built with Builder Code and requires no additional configuration to work with your Builder Content CMS.

Install the Builder Content SDK into an existing web app

Use this when you have an existing web app connected to Builder Code and want to add Builder Content as the content management layer.

The sub-agent scaffolds the integration, wires up the component registry, and connects your content models. No manual setup is required.

Step 1: Tell Builder Code to install the Builder Content SDK

Open a new branch in Builder Code and tell the sub-agent to install the Builder Content SDK into your app. For more details, visit Create and duplicate branches.

Example Prompt

Install Builder Content into this web application.

You don't need to specify your framework or existing setup, as Builder Code already knows.

If you have existing content models or component patterns you want the sub-agent to follow, mention them here. It will use them as a reference during setup.

Step 2: review the scaffolded integration

The sub-agent sets up the Builder Content SDK, wires the component registry, and connects your existing components where possible. Review the changes on the branch before merging.

For more details on how to create a pull request from Fusion, visit Create a pull request.

Step 3: verify in Builder Content

Once the branch is merged and deployed, confirm that your components appear correctly in the Publish visual editor and that content models are mapped as expected.

For more details on Publish, visit:

Step 4: merge and go live

Submit a PR from Builder Code through your normal review and deploy process. Once deployed, your app is live with Publish as the content management layer.

Migrate components, tokens, and branding to Publish

Use this when you have an existing site, such as a site built on another CMS, and want to migrate it to be compatible with Builder Content. The sub-agent maps your existing components and content models to the Publish structure and handles the re-wiring.

Step 1: tell Builder Code to migrate to Builder Content

Open a new branch in Builder Code and tell the sub-agent to migrate your existing setup to Builder Content. For more details, visit Create and duplicate branches.

Example Prompt

Migrate my existing site to work with Builder Publish.

Step 2: review the component and model mapping

The sub-agent produces a mapping of your existing components and content models to their Builder Content equivalents. Review this before proceeding. If something is wrong, share the issue with Fusion.

Step 3: optionally tell Builder Code to register design tokens from existing app styles

The subagent can also register your app styles as Builder Design Tokens that are then used in the Builder Content Visual Editor. This is an optional step, but can help to ensure that content created in Builder Content matches your app’s styles.

Example Prompt

Step 4: validate in Builder Content

With the migration branch active, open the Builder Content visual editor and confirm that components render correctly and content models are mapped as expected. Iterate in Builder Code if adjustments are needed.

For more details on Builder Content, visit:

Step 5: merge and go live

Submit a PR from Builder Code through your normal review and deploy process. Once deployed, your app is live with Builder Content as the content management layer.

Build new components for Builder Content

Use this when you need a new component that doesn't exist yet — or when an existing component needs to be updated and made available in Builder Content. This is the same capability used in the Fusion Preview for Builder Content workflow.

For example:

"Build me a new product wizard component."
"Update this existing banner to include a fade-in animation."
"Create a new mega menu with product categories and hover states."
"Build a carousel that swipes differently on mobile."

The sub-agent builds the component, registers it with the Builder Content component registry, and surfaces the properties you specify as configurable fields in the visual editor. No manual registration required.

For more details, visit Builder Code Preview for Builder Content.

What's next

Was this article helpful?