🧬 Master asset
The foundation of the system is a master asset: one beautiful, well-made website template, created once, and hosted on GitHub. Instead of starting from scratch with every client, you clone the repository and only rebrands what changes. The template is the source; each client is a clone.
🧭 The core idea
Think of the template as a template: you design the beautiful cake once and then stamp out copies. The hard work (layout, animations, responsiveness) is already done.
- •A single source on GitHub — every clone starts from it.
- •Cloning the repo is almost instant — don’t recreate the structure.
- •You only rebrand: replaces what identifies the client and keeps the rest.
one template only
hosts the master
instant copy
only what changes
🛠️ The Cloning Skill
Cloning by hand works once or twice — then you forget a detail. The solution is a skill: one reusable structured prompt that systematically goes through the elements to replace, asks questions, request assets in the right dimensions, and only then implement.
Goes through the elements
The skill has a list of what changes and goes through it item by item — nothing gets left behind.
Asks questions and requests assets
Asks for the name, color, and prices; requests the logo with the correct dimensions already specified.
Implements
With everything in hand, it applies the changes to the clone — guided and repeatable.
💡 Practical tip
You don't need to create the skill from scratch: it's available at Library (Track 5). Start with it and adapt it to your template.
reusable prompt
guided collection
right dimensions
applies the changes
🔁 The 6 Cloneable Elements
Here’s the heart of the system: only 6 things change between one client and the next. Swap out these 6 elements, and the same template becomes one for a different client. Everything outside this list remains untouched.
| # | Element | What changes |
|---|---|---|
| 1 | Logo | the brand at the top and in the footer |
| 2 | Copy | business titles and copy |
| 3 | Trust marks | trusted brands / partners |
| 4 | Prices | plans and pricing |
| 5 | Reviews | customer testimonials |
| 6 | Color scheme | the brand's dominant color |
✓ Switch (there are 6)
- ✓Logo, copy, and trusted brands
- ✓Prices, reviews, and color scheme
- ✓Everything that identifies that client
✗ Don’t touch
- ✗Template structure and layout
- ✗Animations and responsiveness
- ✗What’s already good — you wouldn’t pay again for nothing
the identity
confidence
the offer
the brand's look
🎨 The 70-20-10 design rule
Why is the color scheme so easy to change? Because the template follows the rule 70-20-10: 70% of one dominant color, 20% of a secondary color, and 10% of an accent color. When everything is highlighted, nothing stands out — so the template already knows where the AI should change the color.
🛡️ Why this helps you clone
With a clear ratio, changing the brand is almost just a matter of changing the dominant color (the 70%). The layout stays balanced, and the new site looks professional from the start.
dominant color
secondary
accent
everything highlighted = nothing stands out
🗂️ One folder per client
When you manage many clients, the biggest risk isn't technical — it's edit the wrong site. The simple rule that prevents this: one folder per client on your computer. Lean file management reduces confusion.
clientes/
├── dedetizadora-alfa/
│ └── site/ (clone re-marcado)
├── sorveteria-bela/
│ └── site/ (clone re-marcado)
└── advocacia-cardoso/
└── site/ (clone re-marcado)
💡 Practical tip
Open in the editor only the client’s folder you’ll be working on. That way, it’s impossible for the AI to accidentally edit another client’s site.
per client
without crossing files
less confusion
the right site, every time
🧾 Automate data collection
The next level is to get you out of the middle. Instead of asking everything in chat, create a custom form (logo + the 6 questions + asset upload) that saves the answers to the Supabase via MCP. Then you tell the AI to "clone the latest submission" — without even looking at the answers.
💡 Practical tip
Standardize the form fields with the same names that the Cloning Skill expects. This way, the AI maps the answer → element without ambiguity.
logo + 6 + assets
stores the data
the AI reads the database
without looking at answers
♾️ Scale
With a master template + skill + form, the math works in your favor: from 1 site to 100, to 1,000. The marginal cost per clone is almost zero. And with each round, you refine the skill: run it once, see what didn’t change, adjust, repeat.
Run once
Generate a clone with the current skill and look closely at the result.
Fix what didn't get replaced
Found an old text or a forgotten color? Add that item to the skill.
Repeat
With each iteration, the skill gets sharper — and the next clones come out perfect.
same foundation
per clone
each round
better every time
🔬 Practical example
Get a template called "VOLTFLOW" (a generic service website template) and generate two versions for different niches, changing only the 6 elements:
Version A — Pest Control Company
- Pest control company logo · dominant color: green
- Pest control copy · prices per visit
- Resident reviews · safety seals
Version B — Ice Cream Shop
- Ice cream shop logo · dominant color: pink
- Flavor copy · prices by size
- Customer reviews · supply brands
Same template, same structure — two sites that look custom-made. That’s cloning in action.
🏋️ Exercise
Create or adapt the Cloning Skill and generate 2 variations of the same template for different niches:
- Choose a master template (or use your own from Track 2) and host it on GitHub.
- Adapt the Library skill to go through the 6 elements of your template.
- Generate 2 clones for distinct niches (e.g., an auto repair shop and a law office).
- Note what the skill forgot to change and refine it.
Goal: by the second variation, the skill no longer forgets anything.
⚡ Ready-made prompts
Copy, paste into your AI assistant, and adapt to your use case.
Clone this repository: [URL] and save it on the left as "site-1".
Create a "cloning protocol" skill that, when I ask for a clone, goes through these 6 items — logo, copy, trust marks, prices, reviews, and color scheme. For each item, ask me questions and request the assets with the required dimensions, then implement the changes in the clone.
Clone o site usando os dados da submissão mais recente do Supabase e abra no localhost.
✅ Module summary
Next module:
3.2 — Move sites to GoHighLevel/WordPress