API Request Variable Builder
Turns a reusable API request prompt into a clean variable set covering endpoint, method, auth, payload, response format, and error handling.
Prompt Builders
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.
Rename, change the type, or skip any suggestion. The template updates as you go.
Turns a reusable API request prompt into a clean variable set covering endpoint, method, auth, payload, response format, and error handling.
Documents variables in candidate evaluation prompt templates — candidate name, role, interview notes, strengths, concerns, and recommendation.
Documents variables in case study prompt templates — client, industry, challenge, solution, results, metrics, and quote.
Extracts and documents variables in technical documentation prompt templates — feature name, purpose, setup, usage, limitations, and troubleshooting.
Documents variables in job description prompt templates — role title, seniority, responsibilities, required skills, benefits, location, and hiring process.
Cleans up variables in landing page prompt templates — headline, audience, pain point, offer, social proof, CTA, and objections.
Documents variables in product launch prompt templates — product name, audience, launch date, positioning, benefits, channels, and CTA.
Documents variables in standard operating procedure prompt templates — process name, owner, steps, exceptions, validation checks, handoff rules, and review cadence.
Extracts and documents variables from SQL query prompt templates — table names, columns, filter conditions, joins, sort order, and result limits.
Documents and exports variables from user story and acceptance criteria prompt templates — persona, goal, outcome, constraints, and definition of done.
Turn a prompt that worked once into one you can reuse — pull the winning prompt out of the chat, mark the parts that change as variables, and lock it into a clean template.
Generate many intent-matched SEO pages from a template without the thin-content spam — map the search intents, define the page variables, build the template, and QA before publishing at scale.
Turn a fuzzy business need into requirements a team can build from — interrogate the need into concrete requirements, shape them as user stories, and write the PRD.
Run hiring the same way for every role — build a reusable job-description template, lay out a consistent screening sequence, and extract structured data from resumes instead of eyeballing each one.
The full path to pages that rank at scale, not penalty bait — map the intents, build the data set, structure it, template the page, then QA before publishing hundreds.
The full path to an applicant tracking system — model jobs, candidates, and hiring stages, generate job descriptions and screening prompts, parse résumés into structured data, design the hiring API, set roles, review security, then ship.
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.
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.
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.
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.
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.
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.
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.
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.