obsidian-promptfire/docs/advanced.md
Luca G. Oelfke e7243e3cc1
docs: slim down README and extract detailed docs to docs/
Move comprehensive documentation (settings, templates, output targets,
frontmatter presets, etc.) from the 510-line README into 9 focused files
under docs/. README is now a scannable overview with links to each doc.
Replace GitHub links with Codeberg equivalents.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 12:46:15 +01:00

56 lines
1.3 KiB
Markdown

# Advanced Usage
## Truncation Strategies
When content exceeds a target's token limit, Promptfire applies one of three strategies:
| Strategy | Behavior |
|----------|----------|
| **summarize-headers** | Keep headers, summarize content. Best for structure preservation. |
| **drop-sections** | Remove low-priority sections entirely. Keeps high-priority content complete. |
| **truncate** | Simple cut-off. Fast but loses structure. |
## Priority Order
Sections are prioritized during truncation (highest to lowest):
1. **VAULT.md** - Never truncated (highest priority)
2. **context** files - High priority
3. **conventions** - High priority
4. **structure** - Medium priority
5. **Active note** - Medium priority
6. **examples, templates** - Low priority (truncated first)
## XML Format (Claude Optimized)
When using XML format, files are wrapped in tags:
```xml
<context>
<file name="VAULT.md">
Your vault conventions here...
</file>
<file name="structure.md">
Your folder structure here...
</file>
</context>
```
This format is especially effective with Claude models, as they handle structured XML well within their context window.
## One-Click Context Copy
Output is formatted with clear separators and optional filename headers:
```markdown
# === VAULT.md ===
Your vault conventions here...
---
# === structure.md ===
Your folder structure here...
```