Install the Buying Buddy IDX Plugin on a Claude-Built Site With AI

How it works

Each install step below is a complete prompt. You copy the whole prompt and paste it into Claude, which reads the instructions and makes the changes. This builder cannot open links, so you paste the full text rather than a link to it.

The prompts on this page are the demo versions, so you can read exactly what your AI will be told before you sign up. When you install from your own Buying Buddy dashboard, the same prompts arrive with your activation key and your page addresses already filled in - there is nothing to edit by hand.

The install prompts

Run these in order. Each one is small and checks that the previous step finished before it does anything.

Before you do anything, ask me for my Buying Buddy Activation Key (also called my ACID) and wait for my answer. It is on the Add Plugin tab of my Buying Buddy dashboard. Do NOT guess it or proceed without it. Everywhere the instructions below show [YOUR_ACTIVATION_KEY], use exactly the key I give you.

You are installing the Buying Buddy real-estate IDX plugin on this website, which is built with Claude and published as static HTML that supports <bb-widget> web components. This is the STEP-1 prompt of a 5-step install - it ONLY adds the Buying Buddy loader script to the site head. Do NOT create any pages or place any widgets yet; those come in the next prompts.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", "Update", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

ACTIVATION KEY: [YOUR_ACTIVATION_KEY]

BEFORE YOU START - check the existing setup and STOP if any of these are true:
1. This install path is only for a plain static HTML/JavaScript site - real .html files, or a static index.html whose page content lives in the HTML source - served as static files (for example on Netlify). Claude can build many other kinds of site, so confirm the environment FIRST, before changing anything. Inspect the project and treat it as NOT SUPPORTED if any of these is true:
- A package.json (or equivalent) declares a front-end framework as the rendering layer - React, Next.js, Vue, Nuxt, Svelte or SvelteKit, Astro, Angular, Remix, Gatsby, or similar - or there is a framework build/bundling step that generates the site.
- The main HTML file has no real page content: its body is essentially an empty mount point such as a lone div with id "root" or "app" that a JavaScript bundle fills in at runtime (a single-page app), rather than containing the actual page markup.
- The site is server-rendered, producing each page's HTML from server-side application logic at request time.
If any of the above is true, STOP: make no changes, and tell me this site is not a plain static HTML site, so this is not the correct Buying Buddy install path - I need to contact Buying Buddy support to choose the right method. Do not attempt the install and do not improvise a different approach.

If NONE of the above is true - the project is plain static HTML with JavaScript - continue. One rule for the whole install, starting now and applying to every later step: when a step tells you to create a page, create a REAL page at its own URL/path (its own .html file or route), and add a normal navigation link to it. Never satisfy a "create a page" instruction with an in-page #anchor section on an existing page - Buying Buddy widgets need their own page URLs to work (property-detail links, search redirects, and so on).
2. The Buying Buddy loader is ALREADY installed - a Buying Buddy <script> (one that sets window.__MBB_INSTALLED__ or loads my-buying-buddy.5.0.js) is already present in the site head. If so, STOP: do not add anything or change any files. Tell me Buying Buddy is already installed, and that I should use the "Update" prompt to update it, or continue with the later step prompts in my Buying Buddy dashboard.
If any case above applies, output only that message and do nothing else. If none apply, continue with the install below.

Do ALL of the following (mandatory):
1. Add the Buying Buddy loader to the <head> of the site, as high in the head as possible and NOT deferred. Add this exact block, unchanged:

<!-- Buying Buddy plugin (run-once loader). Safe to evaluate more than once: it injects the Buying Buddy scripts a single time. Do not defer; keep in the head. -->
<script>
(function () {
  if (window.__MBB_INSTALLED__) return;
  window.__MBB_INSTALLED__ = true;

  window.MBB = window.MBB || { seo: "false", data: { acid: "[YOUR_ACTIVATION_KEY]" } };

  var head = document.head || document.getElementsByTagName("head")[0];
  function addSrc(src, id) {
    var s = document.createElement("script");
    s.src = src;
    if (id) s.id = id;
    head.appendChild(s);
  }

  addSrc("https://www.mbb2.com/version3/css/theme/acid/[YOUR_ACTIVATION_KEY]");
  addSrc("https://d2w6u17ngtanmy.cloudfront.net/scripts/my-buying-buddy.5.0.js.gz", "buyingbuddy-library-js");
})();
</script>

   - Add it to the site-wide <head> (the shared head/layout used by EVERY page), so it loads on all pages - not just the home page. If your project has a single shared HTML head or head component, add it there once.
   - Do NOT modify any line of the block - not the URLs, the activation key, the guard variable, or the tag order. It is written so that if the page evaluates it more than once it still injects the Buying Buddy scripts only once; that behavior is intentional and must be preserved.
   - Do NOT add any other Buying Buddy <script> tags, and do NOT hand-write a <script src=".../my-buying-buddy.5.0.js.gz"> tag directly in the head - the loader adds that itself. A second copy would break the plugin.
2. Confirm the page still previews with no JavaScript errors in the browser console. If you see an error that names Buying Buddy or the loader, tell me exactly what it is and STOP - do not refactor anything else to fix it. For ANY OTHER build or runtime error, tell me what it is and STOP.

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

End your reply with this exact line:
➡️ Next Step! Wait until the builder has fully finished and gone idle (some builders keep working for a moment after this line appears), then copy the Step-2 prompt from the Add Plugin tab in your Buying Buddy dashboard and paste it here.

You are continuing the Buying Buddy plugin install on this website, built with Claude and published as static HTML that supports <bb-widget> web components. This is the STEP-2 prompt of a 5-step install - it creates the four foundation pages, the footer disclaimer, and one navigation dropdown. The Buying Buddy loader was added by the Step-1 prompt.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", "Update", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

SCOPE NOTE for this step only: Rules R2 and R3 forbid changing the site navigation. This step contains ONE explicitly permitted exception - creating the single "See More.." dropdown described in step 6 and putting the Communities page in it. Make that one navigation addition and nothing else: do not add, remove, rename, or reorder any other menu item, and do not change any layout, page template, or existing page.

Widget snippets: each numbered step below gives a Buying Buddy widget element AND names its type in plain words. If any widget element below reaches you empty, or a tag looks stripped or altered, STOP and tell me - never guess a widget type or substitute one from memory.

BEFORE YOU START - verify the Step-1 prompt was completed. Check that this is true:
1. The Buying Buddy loader <script> (setting window.__MBB_INSTALLED__ and loading my-buying-buddy.5.0.js) is present in the site head.
If it is missing, STOP: make no changes, and tell me to run the Step-1 prompt from my Buying Buddy dashboard first.
Also STOP (make no changes, and tell me this prompt has already been run) if a page already exists at "/listing-results", "/listing-details", "/market-area-report", or "/featured-communities" rendering a Buying Buddy widget.
If no STOP case applies, continue with the steps below.

Do ALL of the following (mandatory):
1. Create a Search Results foundation page at the path "/listing-results". Render it inside the site's existing page layout so the normal header, navigation, and footer still appear (use the same layout / template as the rest of the site - do NOT produce a bare standalone page). Add a page heading - an <h1> such as "Search Results" - inside a normal constrained container. Immediately below the heading, place the widget inside a FULL-WIDTH container so it can span 100% of the viewport, and add standard responsive horizontal padding to that container so the widget does not bleed to the screen edges. This widget is the only Buying Buddy / listing component on the page - do not hand-build any listing UI around it. Use the ListingResults widget (do NOT use the legacy SearchResults type):
   <bb-widget data-type="ListingResults"></bb-widget>
2. Create a Property Details foundation page at the path "/listing-details" the same way - inside the existing site layout (header, navigation, footer), with an <h1> such as "Property Details" inside a normal constrained container, and the widget placed immediately below it within that same standard constrained container (do NOT use a full-width container for this page - keep it constrained). This widget (the SearchDetails widget) is the only Buying Buddy / listing component on the page:
   <bb-widget data-type="SearchDetails"></bb-widget>
3. Create a Market Report foundation page at the path "/market-area-report" the same way - inside the existing site layout (header, navigation, footer), with an <h1> such as "Market Report" inside a normal constrained container, and the widget placed immediately below it within that same standard constrained container (do NOT use a full-width container for this page - keep it constrained). This widget (the MarketReport widget) is the only Buying Buddy component on the page:
   <bb-widget data-type="MarketReport"></bb-widget>
4. Create a Communities Hub foundation page at the path "/featured-communities" the same way - inside the existing site layout (header, navigation, footer), with an <h1> such as "Communities" inside a normal constrained container, and the widget placed immediately below it within that same standard constrained container (do NOT use a full-width container for this page - keep it constrained). This widget (the Communities widget) is the only Buying Buddy component on the page:
   <bb-widget data-type="Communities"></bb-widget>
5. Add the disclaimer to the site footer so it shows on every page (the Disclaimer widget):
   <bb-widget data-type="Disclaimer"></bb-widget>
6. Add ONE new top-level navigation menu item labeled exactly "See More.." as a dropdown (submenu), and put the Communities page (from step 4) in it as the first entry. Do NOT add the Search Results, Property Details, or Market Report pages to any menu - widgets navigate to those pages directly, so they stay out of the navigation. If this template genuinely cannot render a dropdown/submenu, instead add Communities as a single top-level link with a meaningful label ("Communities") - never a numeric-suffixed label like "Communities2".

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

End your reply with this exact line:
➡️ Next Step! Wait until the builder has fully finished and gone idle (some builders keep working for a moment after this line appears), then copy the Step-3 prompt from the Add Plugin tab in your Buying Buddy dashboard and paste it here.

You are finishing the Buying Buddy plugin install on this website, built with Claude and published as static HTML that supports <bb-widget> web components. This is the STEP-3 prompt of a 5-step install - it adds the home-page search form, measures the header offsets, and ends with the settings I must enter in my Buying Buddy dashboard.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", "Update", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

BEFORE YOU START - verify the Step-1 and Step-2 prompts were completed. Check that ALL of these are true:
1. The Buying Buddy loader <script> (setting window.__MBB_INSTALLED__ and loading my-buying-buddy.5.0.js) is present in the site head.
2. The two foundation pages exist (a Search Results page rendering <bb-widget data-type="ListingResults"></bb-widget> and a Property Details page rendering <bb-widget data-type="SearchDetails"></bb-widget>).
If anything is missing, STOP: make no changes, and tell me which earlier step prompt I need to run first.
If everything is present, continue with the steps below.

Do ALL of the following (mandatory):
1. Add a property search form to the existing home page, rendered inside the normal site layout (header, navigation, footer). Use the QuickSearch widget:
   <bb-widget data-type="QuickSearch" data-filter="formType:simple1+formBackground:204,204,204,0.17+formBorder:204,204,204,0.40+advancedSearch:on"></bb-widget>
   - You MAY change ONLY the RGBA values of formBackground and formBorder inside the data-filter string above, so the search panel visibly stands out against the home page background. Do NOT add any CSS, styled wrappers, or any other visual changes to the home page - placing this widget and tuning those two filter values is the entire scope of this step.
2. Determine whether this site has a STICKY or FIXED header (a header/nav bar that stays pinned to the top of the screen while scrolling - typically position:fixed or position:sticky).
   - If it does NOT, no header offset is needed - you will omit the Widget Header Offset item from the final block below, exactly as its instructions describe.
   - If it DOES, get the rendered height of that header in pixels at three viewport widths: Mobile (viewport < 768px), Tablet (viewport 768px-991px), Desktop (viewport >= 992px). Where you can render the site in a browser, MEASURE the real rendered height. Where you cannot actually measure it (no browser available), ESTIMATE the height from the header's CSS and, in your reply, clearly tell me these header offset values are estimates that I should verify on the published site. Never present an estimate as if it were a real measurement. If the height is the same at all sizes, use the same number three times. These values prevent map widgets (which are sticky) from being hidden under the header. Do NOT report these numbers separately or inline anywhere - report them ONLY inside the final block described below.

Do NOT ask me any questions - perform the steps above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

The Buying Buddy widgets only load on authorized domains, so my preview will show blank widgets until I finish setup in my Buying Buddy dashboard.

You MUST end your response with the block below - this is required, not optional. If you measured Widget Header Offset values above, replace [MOBILE_OFFSET], [TABLET_OFFSET], [DESKTOP_OFFSET] with the real numbers - do NOT print the placeholder text itself, and do NOT wrap the values in any kind of brackets in your output. If this site has NO sticky or fixed header, omit item 3 entirely and show only items 1 and 2.

⚠️ Important: Action Required Before Previewing
The Buying Buddy widgets only load on authorized domains, so your preview will show blank widgets until you complete these steps. Because you host this site yourself, your deploy-preview domain and your live/published domain are authorized SEPARATELY - add whichever one you are viewing now, and add the other when you deploy. Blank widgets on a domain mean that exact domain still needs authorizing. In your Buying Buddy dashboard, open "Website Options" and set the following:

1. Website Type
   Set this to: Built with Claude

2. Deploy Preview URL (no https://):
   Add the domain you use to preview or stage this site - for example the deploy-preview URL your host gives you (such as your-site.netlify.app). Add your live domain here too, as a separate entry, once you deploy the site to it.

3. Widget Header Offset values:
   Mobile: [MOBILE_OFFSET], Tablet: [TABLET_OFFSET], Desktop: [DESKTOP_OFFSET]

➡️ Next Step! Enter the settings above in your Buying Buddy dashboard. Then, once this builder has fully finished and gone idle, copy the Step-5 "Add Recommended Widgets" prompt from the Add Plugin tab and paste it here. You will be able to select which widgets to add.

You are adding recommended Buying Buddy widgets to a website that ALREADY has the Buying Buddy plugin installed (the Buying Buddy loader <script> is in the site head). This site is built with Claude and published as static HTML that supports <bb-widget> web components. This is the FINAL (Step-5) prompt of the install - do NOT reinstall the loader or repeat the base install.

BEFORE YOU START: confirm the Buying Buddy loader is installed - check the site head for a Buying Buddy <script> (one that sets window.__MBB_INSTALLED__ or loads my-buying-buddy.5.0.js). If it is NOT present, STOP and tell me to run the Step-1 install prompt from my Buying Buddy dashboard first. Do not make any changes.

Widget snippets: each numbered item below gives a Buying Buddy widget element AND names its type and purpose in plain words. If any widget element below reaches you empty, or a tag looks stripped or altered, STOP and tell me - never guess a widget type or substitute one from memory.

Important - how Buying Buddy widgets are styled (read before touching any CSS): Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles, so there is NO styling conflict to prevent. Do NOT rename, remap, prefix, scope, or modify any site CSS, design tokens, CSS variables, Tailwind config, theme, or shared UI components. In THIS prompt you MAY add new pages, add them to the Buying Buddy "See More.." dropdown menu, and add one small bar to the site header - and nothing else structural. If this project has no conventional navigation menu or site header to edit (for example a bare page), do NOT invent one - tell me which item you could not place, skip it, and continue with the rest.

ASK ME which widgets to add before making any changes. Present the choice exactly as follows - do not design your own format:
- If your chat environment can render interactive checkboxes, show a checkbox list with one checkbox per widget, ALL PRE-CHECKED, using exactly these six labels in this order: Search Page / Featured Listings / Home Value Form / Contact Me Form / About Me Page / Register & Login Bar. Add these two lines above the list: "These are all recommended - uncheck any you don't want, then confirm." and "If the checkboxes are not clickable in your chat, just reply in text with \"all\" or the numbers/names you want."
- If interactive checkboxes are NOT available, show the same six labels as a numbered list (1-6) and ask me to reply with "all" or the numbers/names I want.
Wait for my selection, then add ONLY the widgets I selected and skip the others entirely.

For EACH PAGE widget (items 1-5), follow these rules every time:
- Create a NEW page, rendered inside the existing site layout (header, navigation, footer). Add a page heading - an <h1> equal to the page title shown in quotes - and place the widget directly below it inside the normal CONSTRAINED page container (NOT full-width).
- Add the new page INTO the Buying Buddy "See More.." dropdown menu that the Step-2 prompt created, as an entry after Communities. Do NOT add it as a top-level menu item. If the "See More.." dropdown does not exist for any reason, create it as a single top-level dropdown first, then add the page into it. If this template genuinely cannot render a dropdown/submenu, fall back to a top-level link with a meaningful distinct label - never a numeric suffix like "Featured Listings2".
- PAGE/PATH CONFLICT: never modify or overwrite an existing page or path. If a page with the same URL/path already exists (for example the template ships its own stub at that path), create the Buying Buddy page at a bb- prefixed path instead (for example "/featured-listings" -> "/bb-featured-listings"), and if a page with the same TITLE already exists, give the new page a distinct title too (for example "Contact Me" -> "Contact Me (Buying Buddy)"). Add THAT page into the "See More.." dropdown. The dropdown keeps menu labels from clashing, but it does not stop two pages fighting over the same path, so this rename still matters.

1. Page title "Search" - a property search page. This is IN ADDITION TO the search form already on the home page; do NOT remove or change the home page search form:
   <bb-widget data-type="SearchForm"></bb-widget>
2. Page title "Featured Listings":
   <bb-widget data-type="FeaturedGallery"></bb-widget>
3. Page title "Home Value" - a home valuation lead-capture form:
   <bb-widget data-type="LcForm" data-filter="form:cmashort+title:Do You Know What Your Home Is Worth+description:Values have increased in your area. Find out how much your home is worth now!"></bb-widget>
4. Page title "Contact Me" - a contact lead-capture form:
   <bb-widget data-type="LcForm" data-filter="form:contactme+title:Send A Message"></bb-widget>
5. Page title "About Me" - shows the agent bio, profile and listings:
   <bb-widget data-type="Brokers"></bb-widget>

6. Register / Login bar - this is NOT a page. Add it to the site header:
   <bb-widget data-type="LoginPanel" data-filter="layout:registerlinks"></bb-widget>
   - Create a small top utility bar as a NEW ROW above the existing header content and place this widget in it (typically aligned to the right). It shows a "Register | Login" link.
   - The font-size of the container you place this widget in must be no larger than the font-size of the main menu items.

After making the changes:
- If you added the top utility bar (item 6) and it changed the height of the site header, recalculate the Widget Header Offset values. Where you can render the site in a browser, MEASURE the rendered header height in pixels at three viewport widths - Mobile (viewport < 768px), Tablet (viewport 768px-991px), Desktop (viewport >= 992px) - and give me the three numbers to enter in my Buying Buddy dashboard. Where you cannot actually measure it (no browser available), ESTIMATE the height from the header's CSS, label each value ESTIMATE, and tell me to verify it on the published site. Report them exactly like this: "Header Offset -> Mobile: 56, Tablet: 64, Desktop: 72" (if the height is the same at all sizes, give the same number three times). If item 6 was not added, or the header height did not change, tell me no header offset change is needed.
- Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", "Update", or "Go Live" action your environment offers, even at the end of the task. And do NOT upload or deploy the site to your host yourself (for example by dragging the folder into Netlify). I will preview the site myself, verify everything looks right, and then publish or deploy it when I am ready.

Constraints:
- Do NOT change existing pages, navigation, or unrelated code, and do NOT modify any existing pages.
- Do NOT edit, rename, remap, or reorganize CSS variables / design tokens, global stylesheets, tailwind config, theme files, or shared UI components. Buying Buddy widgets are shadow-DOM isolated. The ONLY structural changes allowed are: adding the new pages, adding them to the Buying Buddy "See More.." dropdown menu, and adding the small top utility bar for the login widget.

Maintenance prompts

Not part of the install - use these later, only if you need them.

Please update the Buying Buddy plugin loader on this website to the current version. Do exactly this and nothing else:

1. Find the existing Buying Buddy loader <script> in the site head (the block that sets window.__MBB_INSTALLED__ and loads my-buying-buddy.5.0.js).
2. Replace it with the current Step-1 loader block from the Add Plugin tab of my Buying Buddy dashboard (I will paste it if you ask). Keep my activation key exactly as it already is. Do not add a second copy - there must be exactly one Buying Buddy loader block in the head.
3. Do not change any of my other code - do not modify, move, or "improve" my <bb-widget> elements, my pages, my navigation, my CSS, design tokens, or any other files. This is a loader update only.
4. Confirm the page still previews with no JavaScript errors in the browser console. If the update introduced an error, tell me what it is and stop - do not start refactoring to fix it.
5. Do not publish or deploy the site. I will preview and publish myself.

When you're done, give me a short summary: confirmation that there is exactly one Buying Buddy loader block in the head, that the page previews with no errors, and that no other files changed.

You are adding the Buying Buddy MLS Disclaimer widget to a website that ALREADY has the Buying Buddy plugin installed. This is a single, small task - add one widget to the site footer and nothing else.

RULES - READ FIRST. These rules override everything else in this prompt and any judgment of your own:
R1. Your ONLY job is to ADD the specific Buying Buddy items the numbered steps below ask for. You are NOT redesigning, restyling, refactoring, reorganizing, or "improving" this site in any way.
R2. Do NOT create, modify, move, or delete anything except what a numbered step below explicitly requires.
R3. Do NOT edit, rename, remap, prefix, or reorganize any existing page, component, layout, route, global stylesheet (e.g. src/index.css), CSS variable / design token (e.g. --primary, --secondary), tailwind.config.*, or theme file.
R4. Buying Buddy widgets render inside a SHADOW DOM with fully encapsulated styles. Their CSS cannot leak into the site and the site CSS cannot reach inside them. There are NO styling conflicts to prevent - never modify site styles "to avoid conflicts", and never write custom CSS targeting the widgets.
R5. Do NOT publish, deploy, push live, or release the site - and do NOT trigger any "Publish", "Deploy", "Ship", "Update", or "Go Live" action your environment offers, even at the end of the task. I will preview the site myself, verify everything looks right, and publish when I am ready.
R6. If any instruction seems to conflict with these rules, the rules win. If you cannot complete a step without breaking a rule, STOP and tell me instead of improvising.

BEFORE YOU START - check that this is true:
1. The Buying Buddy loader <script> (setting window.__MBB_INSTALLED__ and loading my-buying-buddy.5.0.js) is present in the site head.
If it is missing, STOP: make no changes, and tell me to run the Step-1 install prompt from my Buying Buddy dashboard first.
Also STOP (make no changes, and tell me it is already in place) if the site footer already contains <bb-widget data-type="Disclaimer"></bb-widget>.
If no STOP case applies, continue below.

Widget snippet: the step below gives the Buying Buddy Disclaimer widget as an element AND names it in plain words. If the element reaches you empty, or its tag looks stripped or altered, STOP and tell me - never guess a widget type or substitute one from memory.

Do the following (mandatory):
1. Add the disclaimer (the Disclaimer widget) to the site footer so it shows on every page:
   <bb-widget data-type="Disclaimer"></bb-widget>

Do NOT ask me any questions - perform the step above automatically.

FINAL CHECK (required): before you finish, list every file you created and every file you modified. If anything in that list was not required by the numbered steps above, revert it now and tell me you did.

Other website types

See all supported website types, or read the full list of supported platforms.