Build & Setup

Describe the tool you wish you had. Your clone builds it.

Plain-English requirements in, a working internal tool out, with a preview link, the code and a README.

Your clone walks you through a short requirements template, then uses Clone Code to build the tool: a scorecard, calculator, intake form, tracker or cleanup script. You get a live preview, a zip of the code and a README, and your clone keeps improving the same project as you ask for changes.

What your clone does

Why it matters

Small internal tools never make it onto the engineering roadmap, so you live with spreadsheets. Your clone builds a working first version in minutes.

Most teams have a list of small tools they wish they had: a deal scorecard, a pricing calculator, a simple intake form with a summary view, an inventory lookup. None is worth an engineering ticket. With this card your clone builds a working first version in minutes, and you refine it by chatting.

What you getDetails
Live preview linkValid for about 30 days
Zip of the codeDownload and keep; host or run it yourself
A READMEExplains what the tool does and how to run it
Change requestsKeep asking for changes on the same project for about 7 days
CostNot fixed; small tools are often modest in credits, larger builds cost more

Good first projects: deal evaluation scorecard, pricing calculator, intake form with summary dashboard, inventory lookup, project tracker, data-cleanup script.

The built app runs on its own. It does not call your CRM live unless you build that yourself. No scheduled task is needed for this use case.

Who it helps

OpsRevOpsSalesLeadership
  • Ops: intake forms, inventory lookups, trackers, cleanup scripts.
  • Rev Ops: deal scorecards, pricing calculators, data-cleanup scripts.
  • Sales: quick deal evaluation and quoting helpers.
  • Leadership: simple dashboards and trackers to test an idea.

How it runs

code
 You: "Use Clone_Code to build an internal tool..."
   │
   ▼
 Clone walks you through the requirements template
   │  purpose · users · inputs · outputs · rules · data · look · must-haves
   ▼
 Clone + Clone_Code builds the tool (+ README)
   ▼
 Live preview link (about 30 days)  +  Zip of code  +  README
   │
   ▼
 You test with made-up data and known examples
   │      "Change X" / "Add Y"  (same project, about 7 days)
   ▼
 Download zip  ──►  Host it yourself (GitHub Pages / Netlify / Vercel)
                    or run the script locally
                    (IT review first if it will touch sensitive data)

Set it up, step by step

  1. Open REQUIREMENTS.md and confirm Clone Code is available to your clone
  2. Give CLONE-INSTRUCTIONS.md to your clone and say: "Please set up this use caseShow me a plan first." It checks for Clone Code and optionally saves the small Internal App Builder skill
  3. Say what you want to build, starting with "Use Clone Code"The clone walks you through the requirements template
  4. Open the preview link and test with made-up data
  5. Check the calculations against known examples
  6. Ask for changes
  7. Download the zip, then host or run it yourself

The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.

Before you start

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 forNotes
1Clone CodeBuilds the tool, preview link, zip and READMERequired
2Image OperatorSimple logo or iconsOptional
3Internal App Builder (optional custom skill in CLONE-INSTRUCTIONS.md)Makes the clone always use Clone Code and walk you through requirementsOptional

Good to know

  1. Say "use Clone Code" explicitly. Otherwise the clone may choose another skill.
  2. Start small, then add features. One must-have list first; add nice-to-haves one at a time.
  3. Never put passwords, API keys or real customer data into prompts or preview builds. Use made-up or anonymized sample data. Preview links may be reachable by anyone who has the link.
  4. Review calculations against known examples. Work 2 or 3 cases by hand and compare. You are responsible for the numbers.
  5. Preview links expire (about 30 days). Download the zip.
  6. Change requests continue on the same project for about 7 days. After that, start a new build from the zip.
  7. Get IT review before using it with sensitive data. Especially before connecting to real systems or hosting it where others can reach it.
  8. It's a build helper, not managed hosting. You host, secure and maintain the result. No automatic backups, logins or uptime.
  9. Browser-stored data stays in that browser. If a tool saves to the browser, clearing it or switching computers loses the data. Export CSV regularly.

Questions, answered

Do I need to know how to code?

No for the build; running a script locally needs a few terminal steps.

Does it connect to Salesforce or HubSpot?

Not live by default. Export a CSV and load it. Anything live is a separate build.

Can my whole team use it?

Yes, once you host it. You manage access and updates.

Can the clone host it?

No. The preview is temporary. Hosting is your own step.

Can I edit the code later?

Yes, it is standard code in the zip.

Is a scheduled task needed?

No.

Ready when you are. So is your clone.

Build your clone, paste in the Custom Internal App Builder instructions, and approve the plan it shows you.

Build my cloneBook a demo
Download