Prompt Template

Write prompts with {{variables}} and fill from JSON keys. Reuse system prompts, batch generation, and A/B copy.

Privacy: processed locally, never uploaded.

↓ Paste in the input area below to see results instantly

Prompt template

Use {{name}} or {name} placeholders.

Variables (JSON)

Keys must match template variable names.

Detected variables: role, task, constraints

Filled prompt

Notes

Template syntax

Supports {{name}} or {name}. Missing keys stay as placeholders and are listed below.

Write prompts with {{variables}} and fill from JSON keys. Reuse system prompts, batch generation, and A/B copy.

Quick start

  1. Write template

    Supports {{name}} or {name} placeholders.

  2. Add JSON

    Keys match variable names; missing keys stay as placeholders.

Typical structure

Split role, task, and constraints in the template; variables cover what changes.

Features and use cases

Fill variable placeholders into prompt templates for summarization, translation, code review, and more.

Use for team prompt reuse, onboarding, batch test cases, and support playbooks.

Typical Workflow

1. Design template: Create a base prompt with {{variables}} like 'Explain {{concept}} in {{tone}} style'. Use descriptive names (e.g. 'topic' not 't') for readability. Supports nested variables ({{user.name}}) if JSON has matching structure.

2. Prepare data: Build JSON objects with keys matching template variables, e.g. {'tone':'humorous','concept':'quantum physics'}. Save frequent presets or generate dynamically via API for batch processing.

3. Batch generate: Paste template and JSON for live preview. Supports sequential filling with multiple datasets. Ideal for A/B test copies or role-specific prompts without manual errors.

Examples

Role template

Input

{{role}} + task JSON

Output

Filled system prompt

FAQ

Nested JSON?

Flat string values only; flatten nested objects first.

Can I use conditionals/loops in templates?

Current version only supports simple variable substitution. For complex logic, pre-process in JSON (e.g. using different keys like {{response_zh}} and {{response_en}}). Future versions may support templating engines like Handlebars.