Document / Snippet (Text Editor)

The Text Editor is a rich text workspace designed for writing structured, readable, and visually organized content inside Snack Prompt.

The Text Editor is a rich text workspace designed for writing structured, readable, and visually organized content inside Snack Prompt.

Unlike the Prompt Editor, the Text Editor does not execute instructions or generate dynamic forms. Its purpose is to author content, not logic.

It is optimized for documentation, descriptions, long-form text, and human-readable outputs.

What is it?

The Text Editor is a WYSIWYG (What You See Is What You Get) editor that allows users to format text with headings, lists, quotes, emphasis, and highlights.

It focuses on:

• Readability

• Structure

• Visual hierarchy

Core Capabilities

Headings

The editor supports multiple heading levels to create clear structure:

• Header 1 (Title)

• Header 2 (Section)

• Header 3 (Subsection)

Headings automatically appear in the Document Outline, enabling fast navigation.

Lists

The editor supports both list types:

• Bullet lists

• Numbered lists

Lists are essential for:

• Scannability

• Step-by-step instructions

• Feature breakdowns

---

Quotes

Blockquotes allow you to highlight:

• Important notes

• Warnings

• Emphasized statements

They visually separate contextual information from the main content.

---

Text Formatting

Supported inline formatting includes:

• Bold

• Italic

• Strikethrough

• Highlight

These tools help emphasize key information without breaking flow.

Reference

Formatting Toolbar

Toolbar

The toolbar provides quick access to:

• Headings

• Bold / Italic / Strikethrough

• Lists (bullet and numeric)

• Quotes

• Highlight

• Inline code and links

All formatting is preserved when content is displayed or reused.

Document Outline

The left-side outline:

• Reflects heading structure

• Updates automatically

• Allows fast section navigation

This is especially useful for long documents.

Rules

• Use headings to define structure

• Do not use the Text Editor for executable prompts

Do & Don’t

Do

• Use for documentation and explanations

• Structure content with headings

• Optimize for scanning

Don’t

• Use dynamic placeholders (#)

• Embed execution logic

• Treat it as a prompt field

---

Practical Example

Use cases:

• Documentation pages

• Elements descriptions

• Long-form explanations

• Context for AI

The Text Editor ensures content is clear, readable, and maintainable.