Prompt Builders

Prompt Variable Builder

Paste a prompt you already use. The tool finds the fixed values inside it — names, numbers, dates, audiences — and turns them into {{variable}} placeholders, so you can reuse the same prompt with different values.

Paste a normal prompt — no special syntax needed. Tip: select any value and click Make Variable to convert it by hand.

AI Resource Library

Resources for this tool

View All Resources →

Workflows

Workflows that use this tool

All Workflows →

Projects

Projects that use this tool

Browse the project catalogue →

How it works

Paste a prompt you already use — plain prose, no special syntax. Click Detect Variables and the tool scans it for fixed values (names, companies, dates, prices, URLs, emails, quoted phrases, and labelled fields) and suggests a {{variable}} for each. Every suggestion appears as a row showing the detected value, an editable variable name, and a type — review it, rename it, change the type, or skip it. Accepted values are replaced with {{name}} placeholders everywhere they appear; any {{variables}} already in your prompt are detected as locked and kept as-is. You can also select any text in the prompt and click Make Variable to convert it by hand. When the suggestions look right, copy the reusable template from the Standard tab, or export the template plus its variable manifest as Markdown, JSON, XML, or Structured. Everything runs in your browser — the tool never rewrites the rest of your prompt and never invents a value; the example values in the manifest are taken straight from the text you pasted.

Best for

  • Turning a one-off prompt you already like into a reusable template
  • Auto-detecting the names, numbers, and audiences that should become {{variables}}
  • Exporting the parameterized version for reuse

Not for

  • Building a template from scratch with a live preview — start in the Prompt Template Builder
  • Just tidying a messy prompt — that is the Prompt Formatter

Use cases

  • A welcome email hardcoded with a customer's name, plan, price, and trial-end date that you want to reuse for every new signup
  • A monthly client report where the client name, reporting period, and headline metrics change each time but the structure stays the same
  • A refund or support SOP with a specific order number, amount, and email address that should become fillable fields
  • A prompt that already uses {{customer_name}} but still has a plan, a date, and a ticket number hardcoded — detection locks the existing variable and turns the rest into placeholders
  • A renewal reminder with a company, seat count, renewal date, and amount that goes out to different accounts

Pro tips

  • Detection is a starting point, not a rule to variable-ize everything. Skip any number or name that should stay fixed — a skipped value is left as normal text.
  • Rename the suggestions to clear, consistent names like customer_name, launch_date, or budget_amount before you export.
  • Existing {{variables}} in your prompt are locked and kept as-is, so you can safely paste a half-templated prompt and let the tool fill in the rest.
  • The JSON export includes each variable's type and an example value taken from your prompt — a ready-made schema to hand to teammates. Review the examples before sharing.

FAQ

Does the tool invent variable values?

No. Every suggestion comes from a literal value already in the text you pasted, and the example shown for each variable is that exact detected value. The tool only turns accepted spans into {{placeholders}} — it never fills in a value you did not provide.

What happens to variables my prompt already uses?

Any existing {{variable}} is detected as a locked row and kept exactly as-is. It is never renamed or replaced, so you can mix placeholders you already wrote with newly detected values in the same prompt.

Can I skip a suggested variable?

Yes. Each suggestion has an accept/skip toggle. Skip leaves that value as ordinary text in the template instead of replacing it with a placeholder, so you stay in control of what becomes reusable.

What counts as a valid variable name?

A valid name starts with a letter or underscore, then contains only letters, digits, and underscores. No spaces, hyphens, or special characters. {{productName}}, {{api_key}}, and {{step1}} are valid. {{product-name}}, {{ topic }}, and {{123id}} are not.

Which export formats are available?

Five: Standard (the reusable template), Markdown, JSON, XML, and Structured. The JSON and XML exports also carry each variable's name, type, and example value. Copy any tab, or use Download .txt for the active tab and Download .md for the Markdown version.

Is this the same as Prompt Template Builder?

No. Prompt Variable Builder starts from an existing prompt and detects the fixed values inside it. Prompt Template Builder starts from a blank template you write yourself with {{placeholders}} and a live preview. Use this tool to convert a prompt you already have; use Template Builder to author one from scratch.

Is the prompt I paste sent anywhere, or does detection run in my browser?

No — variable detection runs entirely in your browser, so the prompt you paste is not sent to a server or an AI model by this tool. That matters when a prompt hardcodes customer names, emails, order numbers, prices, or renewal dates. The tool never rewrites the rest of your prompt, and you choose where to paste the finished template.