Website in Minutes
Describe your site in plain English and your clone builds it, with a live preview link and a downloadable zip.
The problem
Getting a first website live usually means weeks of back and forth or learning a site builder. A clone can turn a short description into a working, mobile-friendly site in minutes, so you can review, iterate and publish.
Website in Minutes
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 5–15 minutes
Describe your website in plain English. Your clone builds it with the Clone_Code skill and gives you a live preview link and a zip of the project files, usually in a few minutes.
1. Overview and value
You don't need a designer, a developer or a site-builder subscription to get a first version live. Tell the clone about your business, who it's for, how it should look, and which sections you want. It builds a real, working, mobile-friendly site.
| What you get | Details |
|---|---|
| Live preview link | Valid for about 30 days |
| Project files (zip) | Download and keep; publish anywhere |
| Change requests | Keep asking for changes on the same project for about 7 days |
| Cost | Often well under a few dollars in credits for a simple site; larger builds cost more |
No CRM, email or calendar connection is needed.
2. Who it's for
- Marketing: landing pages, campaign and event pages.
- Ops: simple internal or local-business sites, menus, info pages.
- Leadership: a quick consultant or company site to test an idea.
3. How it works
You: plain-English description (use the template)
│ "Use Clone_Code to build..."
▼
Clone + Clone_Code skill
│ builds the site (HTML/CSS/JS), optional logo via Image_Operator
▼
Live preview link (about 30 days) + Zip of project files
│
▼
You review on desktop and phone ──► "Change the main color to..."
│ (same project, about 7 days)
▼
Download zip ──► Publish yourself (GitHub Pages / Netlify / Vercel / host)
──► Optional custom domain via DNS4. What the clone does (and never does)
Does: builds the site from your description; gives a preview link and zip; makes the changes you ask for; can wire a simple form option; can make a simple logo or hero image with Image_Operator.
Never: invents prices, reviews or testimonials as if they were real (it uses clearly marked placeholders); publishes to your domain or hosting for you; asks for your passwords or hosting logins.
5. Setup walkthrough
Step 1: Open REQUIREMENTS.md and confirm Clone_Code is available to your clone. Step 2: Give CLONE-INSTRUCTIONS.md to your clone and say: "Please set up this use case. Show me a plan first." It checks for Clone_Code and optionally saves the small Website Builder skill. Step 3: Fill in the prompt template (below) and send it, starting with "Use Clone_Code". Step 4: Open the preview link, check desktop and phone. Step 5: Ask for changes. Step 6: Download the zip, then publish.
Prompt template
Use Clone_Code to build a website.
Business name: {BUSINESS_NAME}
Location: {LOCATION}
Who it's for: {AUDIENCE}
Style and colors: {STYLE_AND_COLORS}
Sections: hero (headline and button), services or menu with prices, opening hours, gallery, reviews, contact form, footer
Contact details: {PHONE_EMAIL_ADDRESS}
Logo or images: {IMAGE_LINKS} (or create a simple logo)
Must be mobile-friendly. Use placeholder text and images where I haven't given any, and tell me which they are.Example prompts
1. Local business
Use Clone_Code to build a website for "Maple Street Bakery", a family bakery in Portland. Audience: neighbors and office workers looking for breakfast and custom cakes. Warm, friendly style, cream and terracotta colors. Sections: hero with "Order a cake" button, menu with prices (bread $6, croissant $3.50, custom cake from $45), opening hours (Tue-Sun 7am-3pm), photo gallery, reviews, contact form, map placeholder. Mobile-friendly.2. Consultant or agency
Use Clone_Code to build a one-page site for "Northlake Advisory", a two-person operations consulting firm serving small manufacturers. Clean, professional style, navy and white with a green accent. Sections: hero with "Book a call" button, three services with short descriptions, about us, client results (placeholders), process in 4 steps, contact form. Mobile-friendly.3. Event or landing page
Use Clone_Code to build a landing page for "Spring Product Summit", a one-day online event on March 14. Audience: marketing managers. Bold, modern style, purple and yellow. Sections: hero with date and "Register" button, agenda, speakers (placeholders), FAQ, registration form, footer. Mobile-friendly.6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{BUSINESS_NAME} | Name shown on the site | "Maple Street Bakery" |
{LOCATION} | City or service area | "Portland, OR" |
{AUDIENCE} | Who visits | "Neighbors, office workers" |
{STYLE_AND_COLORS} | Look and feel | "Warm, cream and terracotta" |
{PHONE_EMAIL_ADDRESS} | Contact details to show | "hello@example.com" |
{IMAGE_LINKS} | Links to your logo or photos | "https://.../logo.png" |
{FORM_EMAIL} | Where form submissions should go | "hello@example.com" |
7. What to expect
- A first version usually in a few minutes.
- A preview link (about 30 days) and a zip of files.
- Placeholder text and images you must replace.
- Changes on the same project for about 7 days.
- Cost often well under a few dollars in credits for a simple site; larger builds cost more.
Iterating: reply in plain English, for example:
- "Change the main color to dark green."
- "Add an Order Online button in the hero linking to {ORDER_URL}."
- "Add a reviews section with three placeholder reviews."
- "Make the menu prices bigger and add a gallery of 6 images."
Logo and brand assets: pass image links in your prompt. Or say "create a simple logo and hero image" and the clone can use Image_Operator.
Publishing it yourself (your own steps)
Download the zip first and unzip it.
- Netlify (drag and drop): sign in to Netlify, go to Sites, drag the unzipped folder onto the deploy area, wait for the link.
- Vercel: create a new project from the folder (upload or connect a GitHub repository), then deploy.
- GitHub Pages: create a repository, upload the files, open Settings, then Pages, choose the main branch, save, and wait for the link.
- Your web host: upload the files to the site's public folder (often
public_html) with the host's file manager or FTP. - Custom domain: in your host (Netlify, Vercel or GitHub Pages) add your domain, then at your domain registrar add the DNS records the host shows you (usually a CNAME for www and an A record or ALIAS for the root). It can take from minutes to a day to start working.
8. Customizing
Add pages (about, pricing, blog), change language, add a booking or order button linking to your own tools, ask for a simpler or bolder design, or request a form option (see gotchas).
9. Known gotchas
- Say "use Clone_Code" explicitly. Otherwise the clone may pick another skill.
- Forms need a backend or a form service to actually send submissions. Use a form service or your host's forms feature (for example Netlify Forms). The clone can wire a simple option; tell it which.
- Replace placeholder images and text before launch.
- Check on your phone as well as the desktop.
- Download the zip before the preview expires (about 30 days).
- Change requests continue on the same project for about 7 days. After that, start a new build from the zip or a fresh prompt.
- Review accessibility and legal pages (privacy policy, terms) before launch.
- Cost is not fixed; larger builds use more credits.
10. FAQ
Do I need to know how to code? No. Can I edit the files later? Yes. They are standard web files in the zip. Can the clone publish it for me? No. Publishing and DNS are your own steps. Will the contact form work right away? Not by itself. See gotcha 2. Do I need to connect anything? No.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Clone does something other than build a site | Clone_Code not named | Start with "Use Clone_Code to build..." |
| Preview link doesn't open | Link expired | Re-upload the zip files to a host or ask for a new build |
| Form doesn't send | No form backend | Set up a form service or your host's forms feature |
| Images missing | Image links not public | Use public links or ask for Image_Operator images |
| Changes not applied | Over the ~7 day window | Start a new build using the zip |
| Looks wrong on phone | Layout issue | Ask: "fix the mobile layout, here is what's wrong..." |
Website in Minutes · v1.0.0 · 2026-10-22
Paste these instructions into clone chat
# Clone Instructions: Website in Minutes
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
---
## 1. Role and goal
You will help your user build a real, working website from a plain-English description using the **Clone_Code** skill, and return a live preview link and downloadable zip. Right now your job is **setup**: check Clone_Code, optionally save the small **Website Builder** skill, and run a first build after approval.
## 2. Safety rules
- **Plan first, then act.** Show a numbered plan and wait for an explicit "yes" before saving skills or starting a build.
- **Never ask for or handle passwords, API keys, tokens or hosting logins.** Publishing is done by the user.
- **Never email or contact anyone** as part of setup.
- **Don't invent facts.** Use clearly marked placeholders for prices, reviews or details the user didn't give.
- **Use exact skill names** from the catalog.
## 3. Discovery
Use the `platform` tool and `describeOperator`.
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Clone_Code (required) | ✅ / ⚠️ / ❌ / ❓ | … | … |
| Image_Operator (optional) | … | … | … |
| Website Builder skill (optional) | … | … | … |
Mark "❓ Couldn't check" if you can't verify.
## 4. Collect placeholders
Ask once:
> 1. **Business name** (`{BUSINESS_NAME}`)
> 2. **Location** (`{LOCATION}`)
> 3. **Audience** (`{AUDIENCE}`)
> 4. **Style and colors** (`{STYLE_AND_COLORS}`)
> 5. **Sections and details**: services/menu with prices, hours, contact details (`{PHONE_EMAIL_ADDRESS}`)
> 6. **Logo or image links** (`{IMAGE_LINKS}`), or should I create a simple logo?
> 7. **Contact form**: where should submissions go (`{FORM_EMAIL}`) and which form service or host feature will you use?
Confirm in a table.
## 5. What you can do yourself (after approval)
> **Proposed plan (nothing changes until you say yes):**
> 1. Confirm Clone_Code is available.
> 2. (Optional) Save the **Website Builder** skill so I always use Clone_Code.
> 3. Build your site with Clone_Code and share the preview link and zip.
>
> Reply **yes** to proceed.
After "yes":
1. Attach any missing item (Clone_Code, Image_Operator) via `platform`.
2. Save **Website Builder** (section 7). If you can't create custom skills, give the full markdown in one copy-paste block with steps: settings → **Skills** → **New skill** → name it exactly **Website Builder** → paste → read it → **Save** → tell me "saved".
3. Build using Clone_Code. **No scheduled task is needed** for this use case.
4. Report the preview link (valid about 30 days), how to download the zip, and the about 7 day window for changes on the same project.
## 6. What the user must do
1. **Review the site** on desktop and phone.
2. **Replace placeholders** (text, images, prices).
3. **Download the zip** before the preview expires.
4. **Publish it yourself:**
- Netlify: sign in, Sites, drag the unzipped folder onto the deploy area.
- Vercel: new project, upload the folder or connect a GitHub repository, deploy.
- GitHub Pages: create a repository, upload files, Settings, Pages, select main branch, save.
- Your host: upload the files to the public folder.
- Custom domain: add the domain in your host, then add the DNS records it shows at your domain registrar.
5. **Set up form delivery** with a form service or your host's forms feature.
6. **Review accessibility and add legal pages** (privacy policy) before launch.
## 7. Build prompt and optional skill
### Ready-to-paste build prompt
```
Use Clone_Code to build a website.
Business name: {BUSINESS_NAME}
Location: {LOCATION}
Who it's for: {AUDIENCE}
Style and colors: {STYLE_AND_COLORS}
Sections: hero, services or menu with prices, opening hours, gallery, reviews, contact form, footer
Contact details: {PHONE_EMAIL_ADDRESS}
Logo or images: {IMAGE_LINKS}
Must be mobile-friendly. Use clearly marked placeholders where I gave no content.
```
### Optional skill: Website Builder
~~~~markdown
# Website Builder
## Purpose
Build a real, working website from a plain-English description. Always use the Clone_Code skill. Return a live preview link and a downloadable zip.
## Settings
- Default style: clean, modern, mobile-friendly
- Form delivery: {FORM_EMAIL} through the form service or host feature the user names
## Tools
| Tool | Used for |
|---|---|
| Clone_Code | Always, to build and modify the site |
| Image_Operator | Optional simple logo or hero image |
| platform | Check skills when asked |
## Guardrails
1. Always use Clone_Code for building or changing sites, even if another skill seems possible.
2. Never invent prices, reviews, hours or contact details. Use clearly marked placeholders and list them at the end.
3. Never ask for passwords, hosting logins or API keys.
4. A contact form needs a backend or form service to send submissions. Say so, and wire a simple option only if the user chooses one.
5. If a tool call fails, retry ONCE, then mark it unavailable and report it.
6. Don't publish to the user's domain or host. Publishing is the user's step.
## Steps
1. Collect: business name, location, audience, style and colors, sections, contact details, images.
2. Ask at most 3 short questions if something essential is missing; otherwise proceed with placeholders.
3. Build with Clone_Code, mobile-friendly, with the requested sections.
4. If asked, create a simple logo or hero image with Image_Operator.
5. Share the preview link and zip.
6. Apply change requests on the same project.
## Output format
- Preview link (valid about 30 days)
- How to download the zip
- Placeholders to replace (list)
- Reminders: check on phone, form setup, accessibility and privacy page, change requests for about 7 days
~~~~
## 8. Test plan
Use made-up business details.
| Check | Done |
|---|---|
| Clone started the build with Clone_Code | ☐ |
| Preview link opens | ☐ |
| Hero, services/menu, hours, gallery, reviews, contact form present | ☐ |
| Looks right on a phone | ☐ |
| Change request ("change the main color to...") worked | ☐ |
| Zip downloaded | ☐ |
| Placeholders listed by the clone | ☐ |
## 9. Final status checklist
**✅ Done by me:** *(Clone_Code confirmed, skill saved if chosen, first build and preview link)*
**⏳ Waiting on you:** review, replace placeholders, set up form delivery, download the zip, publish, add legal pages
**💡 Optional next steps:** custom domain via DNS; logo and hero image with Image_Operator; more pages; a second version for another audience
Requirements
Requirements: Website in Minutes
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 5–15 minutes
1. Required skills / operators
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
| # | Skill / operator (exact name) | What it's used for | Notes |
|---|---|---|---|
| 1 | Clone_Code | Builds the website, preview link and zip | Required |
| 2 | Image_Operator | Simple logo or hero image | Optional |
| 3 | Website Builder (optional custom skill in CLONE-INSTRUCTIONS.md) | Makes the clone always use Clone_Code | Optional |
2. Connections and minimum permissions
None required for the build. Publishing needs your own account on the host you choose (the clone never needs those logins).
3. Optional add-ons
Image_Operator for a logo or hero image; a form service or your host's forms feature so the contact form sends submissions. No CRM mapping needed.
4. Data prerequisites
- Business name, location, audience
- Style and colors
- Services or menu with prices
- Opening hours and contact details
- Logo or image links (optional)
- Where form submissions should go
5. Roles and permissions
| Role | Use |
|---|---|
| Marketing | Landing and campaign pages |
| Ops | Simple business and info sites |
| Leadership | Quick company or consultant site |
6. Estimated setup time
| Task | Time |
|---|---|
| Check Clone_Code | 2 min |
| Write the prompt | 5 min |
| First build | A few minutes |
| Review and changes | 10+ min |
| Publishing (your own) | 10–30 min |
Cost: often well under a few dollars in credits for a simple site; larger builds cost more. No scheduled task is needed.
7. Pre-flight checklist
- Clone_Code is available to my clone
- I have my content ready
- I know where I will publish
- I will download the zip within 30 days
8. You're ready when...
- ✅ Clone_Code is confirmed
- ✅ The prompt template is filled in
- ✅ You know your publishing option
Was this use case helpful?
Thanks!