Use Cases

Generate {{ inputs.count }} email subject lines for the following email.

Tone: {{ inputs.tone | default: "professional" }}

Email content:
{{ inputs.email_body | truncate: 2000 }}

Requirements:
- Under 60 characters each
- Create curiosity or urgency
- No clickbait or misleading content

Return JSON: {"subjects": ["subject1", "subject2", ...]}

Create a detailed outline for a blog post.

Topic: {{ inputs.topic }}
Target audience: {{ inputs.audience }}
Target length: {{ inputs.word_count_target | default: 1500 }} words

Include:
- Engaging title options (3)
- Introduction hook
- 4-6 main sections with subpoints
- Conclusion with CTA
- SEO keywords to target

Return a structured JSON outline.

Classify this support ticket.

Subject: {{ inputs.ticket_subject }}
Body: {{ inputs.ticket_body }}

Available categories:
{% for cat in inputs.categories %}
- {{ cat }}
{% endfor %}

Determine:
1. Primary category
2. Priority (low, medium, high, urgent)
3. Sentiment (positive, neutral, negative)
4. Suggested response type (template, custom, escalation)

Return JSON with your classification.

Draft a support response for this customer inquiry.

Customer: {{ inputs.customer_name | default: "Customer" }}
Issue type: {{ inputs.issue_type }}
Tone: {{ inputs.tone | default: "friendly and professional" }}

Customer message:
{{ inputs.customer_message }}

Guidelines:
- Acknowledge their concern
- Provide clear next steps
- Offer additional help
- Keep under 200 words

{% include 'support-signature' %}

Extract entities from the following text.

Entity types to find:
{% for type in inputs.entity_types %}
- {{ type }}
{% endfor %}

Text:
{{ inputs.text }}

For each entity found, include:
- type: the entity type
- value: the extracted text
- normalized: standardized format (dates as ISO, amounts with currency)
- confidence: 0.0 to 1.0

Return: {"entities": [...]}

Summarize this document.

Format: {{ inputs.format | default: "bullets" }}
Max length: {{ inputs.max_length | default: 200 }} words

{% case inputs.format %}
{% when "executive" %}
Write for a busy executive: key findings, implications, recommended actions.
{% when "bullets" %}
Use bullet points for easy scanning.
{% when "paragraph" %}
Write a flowing paragraph summary.
{% endcase %}

Document:
{{ inputs.document | truncate: 15000 }}

{% include 'json-output-instructions' %}

Write a product description for:

Product: {{ inputs.product_name }}
Key features:
{% for feature in inputs.features %}
- {{ feature }}
{% endfor %}

Target audience: {{ inputs.target_audience | default: "general consumers" }}
Tone: {{ inputs.tone | default: "persuasive but honest" }}

Include:
- Attention-grabbing headline
- 2-3 paragraph description
- Bullet point benefits (5)
- Call to action

Return structured JSON with each section.

Analyze these customer reviews for {{ inputs.product_name | default: "this product" }}.

Reviews:
{% for review in inputs.reviews %}
---
{{ review }}
{% endfor %}
---

Provide:
1. Overall sentiment breakdown (% positive/neutral/negative)
2. Top 5 praised features
3. Top 5 complaints
4. Common suggestions for improvement
5. Key quotes (positive and negative)

Return comprehensive JSON analysis.

Explain this code to a developer.

[The user's code is inserted here via inputs.code]

Include:
- What the code does at a high level
- Step-by-step walkthrough
- Key concepts used
- Potential improvements
- Definitions of technical terms for beginners

Return structured JSON explanation.

Generate API documentation for this API endpoint.

[The user's code is inserted here via inputs.code]

Document:
- Endpoint URL and method
- Description
- Request parameters with types and requirements
- Request body schema
- Response schema
- Example request and response
- Error responses

Return in OpenAPI-compatible JSON format.