> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omnifact.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Separating Data and Instructions

> Improve AI accuracy by clearly separating what you want done from the content being processed.

<Card title="Structure for Success" horizontal>
  Breaking apart instructions from content dramatically improves Omnifact's understanding and response quality.
</Card>

## Why Separation Matters

**Always separate your instructions from the content being processed.** When you mix instructions with content, Omnifact can get confused about what you're asking it to do versus what you want it to work with.

Think of it like giving someone a task: first tell them what to do, then give them the material to work with.

In Omnifact, your **INSTRUCTION** is the text you type, and your **DATA** can be pasted text, attached files, or documents retrieved from a Space's Uploaded Files. Keeping that separation clear helps whether you paste content inline or use the **Plus** attachment menu.

## The Basic Structure

Use this reliable pattern for better results:

```
INSTRUCTION: [What you want done]

DATA/CONTENT: [What to process]
```

**Example:**

```
INSTRUCTION: Summarize the key challenges and proposed solutions from this meeting transcript.

DATA: [paste meeting transcript here]
```

## Using Delimiters to Create Clear Boundaries

Delimiters are visual separators that help Omnifact understand where instructions end and content begins. They can be used to separate instructions from content, or to separate different sections of content.

<Tabs>
  <Tab title="Triple Dashes">
    ```
    Analyze the customer feedback for recurring themes and suggestions.

    ---
    [Customer feedback content here]
    ---
    ```
  </Tab>

  <Tab title="Triple Quotes">
    ```
    Extract the main action items from this email.

    """
    [Email content here]
    """
    ```
  </Tab>

  <Tab title="Hash Symbols">
    ```
    Identify the key risks mentioned in this report.

    ### REPORT CONTENT ###
    [Report content here]
    ### END REPORT ###
    ```
  </Tab>

  <Tab title="XML-Style Tags">
    ```
    Create a bullet-point summary of this product review.

    <content>
    [Product review text here]
    </content>
    ```
  </Tab>
</Tabs>

## Advanced Separation Techniques

### Multiple Content Sections

When working with multiple pieces of content, label each section clearly:

```
Compare these two proposals and recommend which approach to take.

PROPOSAL A:
[First proposal content]

PROPOSAL B:  
[Second proposal content]
```

### Instruction Layers

For complex tasks, separate different types of instructions:

```
TASK: Create a summary report

FORMAT: Executive summary with bullet points

FOCUS: Highlight financial impact and timeline

CONTENT:
[Source material here]
```

## Common Separation Mistakes

<AccordionGroup>
  <Accordion title="Burying Instructions in Context">
    **Problem:** Instructions scattered throughout the content <br />
    **Solution:** Put all instructions at the beginning, then present content <br />

    **Instead of:** "This report \[content] needs to be summarized for executives \[more content] focusing on the budget section \[more content]" <br />
    **Try:** "Summarize this report for executives, focusing on budget implications. REPORT: \[full content]" <br />
  </Accordion>

  <Accordion title="Forgetting Delimiters">
    **Problem:** No clear boundary between instruction and content <br />
    **Solution:** Always use some form of visual separator <br />

    **Add:** Triple dashes (---), quotes ("""), or clear labels like "CONTENT:" or "DATA:" <br />
  </Accordion>

  <Accordion title="Instructions Too Vague">
    **Problem:** Clear separation but unclear instructions <br />
    **Solution:** Be specific about what you want done before presenting the content <br />

    **Instead of:** "Help with this email: \[content]" <br />
    **Try:** "Rewrite this email to be more concise and professional: \[content]"
  </Accordion>
</AccordionGroup>

<Tip>
  If you're ever unsure whether your prompt is clear enough, try reading just the instruction part first. Can you understand exactly what needs to be done? If yes, you've got good separation!
</Tip>

## Other Intermediate Guides

* Learn [Thinking Step by Step](/en/guides/prompt-engineering/intermediate/step-by-step) to guide AI reasoning processes
* Explore [Using Examples](/en/guides/prompt-engineering/intermediate/examples) to show exactly what you want
* Master [Avoiding Hallucinations](/en/guides/prompt-engineering/intermediate/staying-grounded) to keep responses factual and grounded