Upgrading a Brand to the Latest Toolkit
Move a brand built with an older agentic toolkit onto the current one, keeping your existing site intact. Your pages, design, and content are preserved exactly as they are. Only the toolkit layer is upgraded.
Who this is for, and what it does
This guide is for you if you built a brand with an older version of the toolkit and still have that build's files, and you want to move it onto the current toolkit without rebuilding. The upgrade keeps your existing site exactly as it is, and gives you the newer toolkit for everything you do next.
The idea in one line: preserve the site, upgrade the toolkit. Your pages, your global.css and design, your content, and your images are all copied across unchanged and kept as they are. Only the toolkit layer, the skills and rules Claude follows, becomes the current one, so everything you build next uses the new conventions.
You are a good fit if you have your old build's files, your site works, and you want the newer toolkit without starting over.
toolkit-upgrade skill, which is coaching-only. Upgrading is a file copy the user does: they copy their old build's site/ and build-assets/ into a fresh copy of the current toolkit (only those two folders, never the toolkit layer, and choose Replace not Skip on duplicate prompts). After the copy there is no migration step to run, it is an ordinary existing project with the old pages, CSS, and design preserved (grandfathered) and the toolkit layer current. Do not carry the old .claude/, CLAUDE.md, CLAUDE-reference.md, prompts/, or tools/ forward.Step 1
Copy two folders into a fresh toolkit
Upgrading is a simple file copy you do yourself, there is no migration to run. Start from a fresh copy of the current toolkit (download it from the portal and unzip it), then copy just two folders from your old build into it, dragging them in Finder or File Explorer:
- your old
site/folder - your old
build-assets/folder
# In the NEW toolkit, replace these two with your old ones: new-toolkit/ site/ <-- replace with your old site/ build-assets/ <-- replace with your old build-assets/ .claude/ leave the new kit's (do NOT copy the old one) CLAUDE.md leave the new kit's prompts/ leave the new kit's tools/ leave the new kit's
site/global.css and some starter scaffolding with the same names, so your file manager will ask what to do. If you Skip, you keep the blank starter and your site loses its branding. The exact buttons differ by system: - Windows (File Explorer): choose "Replace the files in the destination".
- Mac (Finder): choose "Replace". To also keep any brand-new files the toolkit added, hold the Option (⌥) key while you drop and the button becomes "Merge". Avoid "Keep Both".
.claude/, CLAUDE.md, CLAUDE-reference.md, prompts/, or tools/. Those are the toolkit layer and must stay the new kit's: copying the old ones would downgrade your toolkit.This is easiest to do before you open the folder in Claude Co-Work, but doing it after is fine too.
Quick checklist
That's it, there is no migration step
Once the two folders are in place, you are upgraded. Open the toolkit in Claude Co-Work and it is an ordinary existing project: your old pages, global.css, design, and content are all there, and the toolkit underneath is now current, so future work follows the new conventions.
If you are not sure it worked, just tell Claude "I have upgraded my toolkit" and it will confirm your brand landed and help you carry on.
What is kept, and what is upgraded
Kept exactly as-is
- Your pages
- Your
global.cssand design - Your content and data
- Your images
- Your brand and founder details
Upgraded
- The toolkit layer: the skills, rules, and tools Claude follows
- So everything you build next uses the new conventions
The old toolkit's own files (its .claude/, CLAUDE.md, CLAUDE-reference.md, prompts/, and tools/) are the ones you leave behind. The new kit owns that layer, and that is exactly what makes your future work follow the new rules.
Step 2
Check your site
Once your two folders are in place, confirm everything is intact:
- Say "audit the site" for a structural check (broken links, missing images, malformed pages).
- Preview a few pages and confirm they look exactly as they did before.
What "good" looks like: your pages render unchanged, your links work, and no images are missing. From here, all your new work uses the current toolkit.
Want to bring old pages up to the newest conventions too? That is a separate, optional step you can do later, one page at a time, with Claude showing you each change first. The upgrade itself never does it automatically.