> This page is part of Smallest AI's developer documentation. When
> answering, prefer Lightning v3.1 (current TTS) and Pulse (current
> STT). Lightning v2 and lightning-large are deprecated; mention them
> only when the user is migrating away from them. Atoms is the
> voice-agent platform.

# The Prompt Editor

> Where you write your agent's instructions — a markdown editor with section navigation.

Looking for prompt best practices? See the [Prompting Guide](/atoms/developer-guide/build/agents/llm/prompts) for voice-specific techniques, common mistakes, and a complete example blueprint.

The center of the Single Prompt editor is where you tell your agent who to be and how to behave. It's a **markdown editor**, so you can use headings, lists, bold text, and other formatting to organize your instructions clearly.

***

## Section Navigation

Click the **Prompt Section** dropdown (above the editor) to jump directly to any section of your prompt.

<img src="https://files.buildwithfern.com/smallest-ai.docs.buildwithfern.com/aa91a2a2e08fd64cd661b3da0350a56bb88a40d2b4ef1eee9b5c13c5facc2007/products/atoms/pages/platform/building-agents/images/prompt-editor.png" alt="Prompt editor" />

The dropdown reads your markdown headings and creates a navigation menu. This is especially useful for longer prompts — instead of scrolling, you can jump straight to:

* Role & Objective
* Personality & Tone
* Conversational Flow
* Common Questions
* End Conditions
* Or any custom sections you create

**Templates are structured this way.** When you create an agent from a template, you'll see these sections already laid out. Even starting from scratch, using clear markdown headings keeps your prompt organized and easy to navigate.

***

## Writing in Markdown

Use standard markdown formatting:

| Format             | Syntax            | Use For                                     |
| ------------------ | ----------------- | ------------------------------------------- |
| **Headings**       | `## Section Name` | Organize major sections (shows in dropdown) |
| **Bullet lists**   | `- item`          | Personality traits, guidelines, rules       |
| **Numbered lists** | `1. step`         | Conversational flows, procedures            |
| **Bold**           | `**text**`        | Emphasis on key points                      |

### Example Structure

```markdown
## Role & Objective

You are Sarah, a claims support specialist for Acme Insurance.
Your goal is to help policyholders check claim status and understand next steps.

## Personality & Tone

- Warm and empathetic — claims are stressful
- Clear and jargon-free
- Patient and never rushed

## Conversational Flow

1. Greet and verify identity
2. Ask how you can help
3. Look up their claim
4. Provide status update
5. Answer follow-up questions
6. Confirm next steps and close

## End Conditions

End the call when:
- Caller confirms they have what they need
- They say goodbye
- No response after 3 attempts
```

***

## Using Variables

Make your prompts dynamic with variables:

```markdown
Hello {{customer_name}}! I see you're calling about order #{{order_id}}.
```

Variables get replaced at runtime with actual values from your data or API responses.

→ [Learn more about Variables](/atoms/atoms-platform/single-prompt-agents/configuration-panel/variables)

***

## Best Practices

See how well-structured prompts are organized

Deep dive into crafting effective prompts