Patterns and Templates

You are a {role}. Classify the {input_type} below into exactly one of the
following categories.

Categories:
- {category_1}: {definition_1}
- {category_2}: {definition_2}
- {category_3}: {definition_3}

Rules:
- Pick the single best best category, even if more than one fits.
- If none of the categories fit, respond with "uncategorized".
- Do not invent new categories.

Examples:
{example_input_1}
Category: {example_category_1}

{example_input_2}
Category: {example_category_2}

{example_input_3}
Category: {example_category_3}

Now classify the following:

{input}
Category:

You are a {role}. Extract the following fields from the {input_type} below.

Fields:
- {field_1} ({type_1}): {description_1}
- {field_2} ({type_2}): {description_2}
- {field_3} ({type_3}): {description_3}

Rules:
- Use only information present in the input.
- If a field cannot be determined from the input, set it to null.
- Do not infer values that are not stated.

Output format:
Return a single JSON object matching the schema. No preamble, no explanation.

{input_type}:
<input>
{input}
</input>

You are a {role} producing summaries for {audience}.

Summarize the {input_type} below in {length}.

Requirements:
- Open with the {single_most_important_thing}.
- Cover {required_topic_1}, {required_topic_2}, and {required_topic_3}.
- Use plain English; define any acronym on first use.
- Do not editorialize. State what the source says, not what you think.

{input_type}:
<source>
{input}
</source>

You are a {role} writing for {publication_or_context}.

Brief:
{brief}

Constraints:
- Length: {word_count}.
- Voice: {voice_descriptor}.
- Reading level: {reading_level}.
- Audience: {audience_descriptor}.
- Required elements: {required_elements}.
- Avoid: {forbidden_elements}.

Reference materials (use these as facts, not as style models):
<references>
{references}
</references>

Produce the draft. Do not include a preamble or commentary; output the draft only.

Convert the {source_format} below into {target_format}.

Rules:
- Preserve all factual content.
- Do not add information that is not in the source.
- Do not omit information that is in the source.
- {format_specific_rule_1}
- {format_specific_rule_2}

Source:
<source>
{input}
</source>

Output:

You are a {role}. Answer the question using only the information in the source
documents below. If the answer is not in the documents, respond with "Not found
in the provided sources" and stop.

Process:
1. Extract every passage relevant to the question. Place each verbatim, with its
   document index, inside <quote> tags within a <quotes> wrapper.
2. Compose the answer based only on the extracted quotes. Place it inside
   <answer> tags.
3. Do not include information from outside the documents.

Question:
{question}

<documents>
<document index="1">
{document_1}
</document>
<document index="2">
{document_2}
</document>
</documents>

Compare {item_a} and {item_b} along the following dimensions:

- {dimension_1}
- {dimension_2}
- {dimension_3}

For each dimension, describe the position of each item in one sentence, then state
which is stronger and why.

Output format:
A Markdown table with columns: dimension, {item_a}, {item_b}, stronger, reason.

Source material:
<item_a>
{item_a_input}
</item_a>
<item_b>
{item_b_input}
</item_b>

You are a senior {role} reviewing the {artifact_type} below. Your job is to find
the weaknesses, not to praise the strengths.

For each weakness:
1. Quote the specific passage.
2. Name the type of issue (clarity, accuracy, structure, tone, evidence).
3. Explain why it is a problem in one sentence.
4. Propose a specific revision.

If the artifact is solid throughout, say so explicitly rather than inventing
weaknesses to find.

<artifact>
{input}
</artifact>

You are a routing assistant. Read the user request below and decide which of the
following specialists should handle it.

Specialists:
- {specialist_1}: {description_1}
- {specialist_2}: {description_2}
- {specialist_3}: {description_3}

Output a single JSON object with the keys "specialist" (one of the names above)
and "reason" (one sentence). If the request is ambiguous, set specialist to
"clarification_needed" and reason to a one sentence question for the user.

User request:
{input}